Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[DOCS-6352] Remove runtime metrics from list of unsupported features. #20165

Closed
wants to merge 2 commits into from
Closed

[DOCS-6352] Remove runtime metrics from list of unsupported features. #20165

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4570b8e
Remove runtime metrics from list of unsupported features.
brett0000FF Oct 12, 2023
086bd5f
Fix spacing.
brett0000FF Oct 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/en/opentelemetry/otlp_ingest_in_the_agent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@

OTLP Ingest in the Agent is a way to send telemetry data directly from applications instrumented with [OpenTelemetry SDKs][1] to Datadog Agent. Since versions 6.32.0 and 7.32.0, the Datadog Agent can ingest OTLP traces and [OTLP metrics][2] through gRPC or HTTP. Since versions 6.48.0 and 7.48.0, the Datadog Agent can ingest OTLP logs through gRPC or HTTP.

OTLP Ingest in the Agent allows you to use observability features in the Datadog Agent. Because the application is instrumented with OpenTelemetry SDK, some Datadog library specific features aren't available for the ingested data including Application Security Management, Continuous Profiler, Runtime Metrics, and Ingestion Rules.
OTLP Ingest in the Agent allows you to use observability features in the Datadog Agent. Because the application is instrumented with OpenTelemetry SDK, some Datadog library specific features aren't available for the ingested data including Application Security Management, Continuous Profiler, and Ingestion Rules.

Check notice on line 20 in content/en/opentelemetry/otlp_ingest_in_the_agent.md

View workflow job for this annotation

GitHub Actions / vale

[vale] content/en/opentelemetry/otlp_ingest_in_the_agent.md#L20 

[Datadog.sentencelength] Try to keep your sentence length to 25 words or fewer.
Raw output 
{"message": "[Datadog.sentencelength] Try to keep your sentence length to 25 words or fewer.", "location": {"path": "content/en/opentelemetry/otlp_ingest_in_the_agent.md", "range": {"start": {"line": 20, "column": 89}}}, "severity": "INFO"}

To get started, you first [instrument your application][3] with OpenTelemetry SDKs. Then, export the telemetry data in OTLP format to the Datadog Agent. Configuring this varies depending on the kind of infrastructure your service is deployed on, as described on the page below. Although the aim is to be compatible with the latest OTLP version, the OTLP Ingest in the Agent is not compatible with all OTLP versions. Verify OTLP version compatibility through the [Agent changelog][4].

Expand Down
Loading