Skip to content

Commit

Permalink
Update the other languages with general changes
Browse files Browse the repository at this point in the history
  • Loading branch information
watson committed Jan 17, 2025
1 parent 1e5f577 commit 5267746
Show file tree
Hide file tree
Showing 5 changed files with 61 additions and 21 deletions.
6 changes: 3 additions & 3 deletions content/en/dynamic_instrumentation/enabling/dotnet.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ further_reading:
text: 'Getting Started with Datadog Agent'
---

Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version, and go directly to enabling Dynamic Instrumentation in step 4.
Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version. Then, go directly to enabling Dynamic Instrumentation in step 4.

## Prerequisites

Expand All @@ -26,7 +26,7 @@ For a better experience, Datadog recommends enabling [autocomplete and search (i

**Note**: Dynamic Instrumentation is available in the `dd-trace-dotnet` library in versions 2.54.0 and later.

4. Run your service with Dynamic Instrumentation enabled by setting the `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `DD_SERVICE`, `DD_ENV`, and `DD_VERSION` Unified Service Tags so you can filter and group your probes and target active clients across these dimensions.
4. Run your service with Dynamic Instrumentation enabled by setting the `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `DD_SERVICE`, `DD_ENV`, and `DD_VERSION` Unified Service Tags so you can filter and group your instrumentations and target active clients across these dimensions.
5. After starting your service with Dynamic Instrumentation enabled, you can start using Dynamic Instrumentation on the [APM > Dynamic Instrumentation page][4].

## Configuration
Expand All @@ -43,7 +43,7 @@ Configure Dynamic Instrumentation using the following environment variables:

## What to do next

See [Dynamic Instrumentation][6] for information about setting snapshot and metric probes and browsing and indexing the data.
See [Dynamic Instrumentation][6] for information about adding instrumentations and browsing and indexing the data.

## Further reading

Expand Down
6 changes: 3 additions & 3 deletions content/en/dynamic_instrumentation/enabling/java.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ further_reading:
text: 'Getting Started with Datadog Agent'
---

Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version, and go directly to enabling Dynamic Instrumentation in step 4.
Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version. Then, go directly to enabling Dynamic Instrumentation in step 4.

## Requirements

Expand Down Expand Up @@ -45,7 +45,7 @@ Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If

**Note**: Dynamic Instrumentation is available in the `dd-java-agent.jar` library in versions 1.34.0 and later.

3. Run your service with Dynamic Instrumentation enabled by setting `-Ddd.dynamic.instrumentation.enabled` flag or `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `dd.service`, `dd.env`, and `dd.version` Unified Service Tags so you can filter and group your probes and target active clients across these dimensions.
3. Run your service with Dynamic Instrumentation enabled by setting `-Ddd.dynamic.instrumentation.enabled` flag or `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `dd.service`, `dd.env`, and `dd.version` Unified Service Tags so you can filter and group your instrumentations and target active clients across these dimensions.
{{< tabs >}}
{{% tab "Command arguments" %}}

Expand Down Expand Up @@ -99,7 +99,7 @@ Configure Dynamic Instrumentation using the following environment variables:

## What to do next

See [Dynamic Instrumentation][6] for information about setting snapshot and metric probes and browsing and indexing the data.
See [Dynamic Instrumentation][6] for information about adding instrumentations and browsing and indexing the data.

## Further reading

Expand Down
32 changes: 26 additions & 6 deletions content/en/dynamic_instrumentation/enabling/php.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,17 +12,20 @@ further_reading:
text: 'Getting Started with Datadog Agent'
---

Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version, and go directly to enabling Dynamic Instrumentation in step 4.
{{< beta-callout-private url="https://forms.gle/TODO" >}}
<p><strong>Dynamic Instrumentation for PHP is in limited preview</strong></p>
<p>It is not available to all customers. Request access to join the waiting list.</p>
<p>Certain limitations apply to the limited preview. See <a href="#limitations">Limitations</a> for more information.</p>
{{< /beta-callout-private >}}

Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version. Then, go directly to enabling Dynamic Instrumentation in step 4.

## Installation

1. Install or upgrade your Agent to version [7.45.0][7] or higher.
2. If you don't already have APM enabled, in your Agent configuration, set the `DD_APM_ENABLED` environment variable to `true` and listening to the port `8126/TCP`.
3. Install or upgrade the PHP tracing libraries to version 1.4.0, by following the [relevant instructions][2].

**Note**: Dynamic Instrumentation is available in the `dd-trace-php` library in versions 1.4.0 and later. Only function and method probes are supported.

4. Run your service with Dynamic Instrumentation enabled by setting the `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `DD_SERVICE`, `DD_ENV`, and `DD_VERSION` Unified Service Tags so you can filter and group your probes and target active clients across these dimensions.
4. Run your service with Dynamic Instrumentation enabled by setting the `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `DD_SERVICE`, `DD_ENV`, and `DD_VERSION` Unified Service Tags so you can filter and group your instrumentations and target active clients across these dimensions.
5. After starting your service with Dynamic Instrumentation enabled, you can start using Dynamic Instrumentation on the [APM > Dynamic Instrumentation page][3].

## Configuration
Expand All @@ -39,7 +42,22 @@ Configure Dynamic Instrumentation using the following environment variables:

## What to do next

See [Dynamic Instrumentation][5] for information about setting snapshot and metric probes and browsing and indexing the data.
See [Dynamic Instrumentation][5] for information about adding instrumentations and browsing and indexing the data.

## Limitations

Dynamic Instrumentation for PHP is currently in limited preview, which means it is not available to all customers. To join the waiting list, [fill out this form][6].

The following limitations apply to the limited preview:

### Supported features

- [Dynamic Logs][8] attached to a function/method

### Unsupported features

- Dynamic Logs attached to a specific file/line
- Dynamic Metrics, Spans, and Span Tags

## Further reading

Expand All @@ -50,4 +68,6 @@ See [Dynamic Instrumentation][5] for information about setting snapshot and metr
[3]: https://app.datadoghq.com/dynamic-instrumentation
[4]: /getting_started/tagging/unified_service_tagging
[5]: /dynamic_instrumentation/
[6]: https://forms.gle/TODO
[7]: https://app.datadoghq.com/account/settings/agent/latest?platform=overview
[8]: /dynamic_instrumentation/#creating-log-probes
6 changes: 3 additions & 3 deletions content/en/dynamic_instrumentation/enabling/python.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ further_reading:
text: 'Getting Started with Datadog Agent'
---

Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version, and go directly to enabling Dynamic Instrumentation in step 4.
Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version. Then, go directly to enabling Dynamic Instrumentation in step 4.

## Prerequisites

Expand All @@ -31,7 +31,7 @@ Recommended, [autocomplete and search (in Preview)][6] is enabled.

**Note**: Dynamic Instrumentation is available in the `ddtrace` library version 2.2.0 and higher.

4. Run your service with Dynamic Instrumentation enabled by setting the `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `DD_SERVICE`, `DD_ENV`, and `DD_VERSION` Unified Service Tags so you can filter and group your probes and target active clients across these dimensions.
4. Run your service with Dynamic Instrumentation enabled by setting the `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `DD_SERVICE`, `DD_ENV`, and `DD_VERSION` Unified Service Tags so you can filter and group your instrumentations and target active clients across these dimensions.
{{< tabs >}}
{{% tab "Environment variables" %}}

Expand Down Expand Up @@ -70,7 +70,7 @@ Configure Dynamic Instrumentation using the following environment variables:

## What to do next

See [Dynamic Instrumentation][5] for information about setting snapshot and metric probes and browsing and indexing the data.
See [Dynamic Instrumentation][5] for information about adding instrumentations and browsing and indexing the data.

## Further reading

Expand Down
32 changes: 26 additions & 6 deletions content/en/dynamic_instrumentation/enabling/ruby.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,17 +12,20 @@ further_reading:
text: 'Getting Started with Datadog Agent'
---

Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version, and go directly to enabling Dynamic Instrumentation in step 4.
{{< beta-callout-private url="https://forms.gle/TODO" >}}
<p><strong>Dynamic Instrumentation for Ruby is in limited preview</strong></p>
<p>It is not available to all customers. Request access to join the waiting list.</p>
<p>Certain limitations apply to the limited preview. See <a href="#limitations">Limitations</a> for more information.</p>
{{< /beta-callout-private >}}

Dynamic Instrumentation is a feature of supporting Datadog tracing libraries. If you are already using [APM to collect traces][1] for your application, ensure your Agent and tracing library are on the required version. Then, go directly to enabling Dynamic Instrumentation in step 4.

## Installation

1. Install or upgrade your Agent to version [7.45.0][7] or higher.
2. If you don't already have APM enabled, in your Agent configuration, set the `DD_APM_ENABLED` environment variable to `true` and listening to the port `8126/TCP`.
3. Install or upgrade the Ruby tracing library to version 2.8.0 or higher, by following the [relevant instructions][2].

**Note**: Dynamic Instrumentation is available in the `dd-trace-ruby` library in versions 2.8.0 and later. Only log probes are currently supported.

4. Run your service with Dynamic Instrumentation enabled by setting the `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `DD_SERVICE`, `DD_ENV`, and `DD_VERSION` Unified Service Tags so you can filter and group your probes and target active clients across these dimensions.
4. Run your service with Dynamic Instrumentation enabled by setting the `DD_DYNAMIC_INSTRUMENTATION_ENABLED` environment variable to `true`. Specify `DD_SERVICE`, `DD_ENV`, and `DD_VERSION` Unified Service Tags so you can filter and group your instrumentations and target active clients across these dimensions.
5. After starting your service with Dynamic Instrumentation enabled, you can start using Dynamic Instrumentation on the [APM > Dynamic Instrumentation page][3].

## Configuration
Expand All @@ -39,7 +42,22 @@ Configure Dynamic Instrumentation using the following environment variables:

## What to do next

See [Dynamic Instrumentation][5] for information about setting snapshot and metric probes and browsing and indexing the data.
See [Dynamic Instrumentation][5] for information about adding instrumentations and browsing and indexing the data.

## Limitations

Dynamic Instrumentation for Ruby is currently in limited preview, which means it is not available to all customers. To join the waiting list, [fill out this form][6].

The following limitations apply to the limited preview:

### Supported features

- [Dynamic Logs][8] attached to a function/method

### Unsupported features

- Dynamic Logs attached to a specific file/line
- Dynamic Metrics, Spans, and Span Tags

## Further reading

Expand All @@ -50,4 +68,6 @@ See [Dynamic Instrumentation][5] for information about setting snapshot and metr
[3]: https://app.datadoghq.com/dynamic-instrumentation
[4]: /getting_started/tagging/unified_service_tagging
[5]: /dynamic_instrumentation/
[6]: https://forms.gle/TODO
[7]: https://app.datadoghq.com/account/settings/agent/latest?platform=overview
[8]: /dynamic_instrumentation/#creating-log-probes

0 comments on commit 5267746

Please sign in to comment.