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.

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

Whats new 01 13 otelmetrics #19694

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
20 changes: 20 additions & 0 deletions src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
title: 'Enhanced APM golden metrics accuracy for services instrumented with OpenTelemetry'
summary: 'APM golden metrics are now calculated directly from OpenTelemetry metrics'
releaseDate: '2025-01-13'
learnMoreLink: 'https://docs.newrelic.com/docs/opentelemetry/get-started/apm-monitoring/opentelemetry-apm-ui/#golden-metrics'
getStartedLink: ''
---

Starting today, we're improving the accuracy of APM golden metrics for services instrumented with OpenTelemetry. "Golden metrics" or "golden signals" refer to high-value metrics such as latency, error rate, and throughput, which are visible in the entity explorer, workloads activity page, and change tracking details page. Previously, these metrics were derived from sampled span data. Now that OpenTelemetry metrics have matured, we are calculating them using unsampled metrics data, providing a more precise and comprehensive view of your service's performance. **To maintain visibility of golden metrics for your OpenTelemetry services, please ensure you are reporting both traces and metrics.**

Check warning on line 9 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [Microsoft.SentenceLength] Try to keep sentences short (< 30 words). Raw Output: {"message": "[Microsoft.SentenceLength] Try to keep sentences short (\u003c 30 words).", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 9, "column": 115}}}, "severity": "INFO"}

Check warning on line 9 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.ComplexWords] Consider using 'before' instead of 'Previously'. Raw Output: {"message": "[new-relic.ComplexWords] Consider using 'before' instead of 'Previously'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 9, "column": 325}}}, "severity": "INFO"}

Check warning on line 9 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [Microsoft.Passive] 'were derived' looks like passive voice. Raw Output: {"message": "[Microsoft.Passive] 'were derived' looks like passive voice.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 9, "column": 351}}}, "severity": "INFO"}

Check failure on line 9 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [Microsoft.Contractions] Use 'we're' instead of 'we are'. Raw Output: {"message": "[Microsoft.Contractions] Use 'we're' instead of 'we are'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 9, "column": 433}}}, "severity": "ERROR"}

Check warning on line 9 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.ComplexWords] Consider using 'keep' or 'support' instead of 'maintain'. Raw Output: {"message": "[new-relic.ComplexWords] Consider using 'keep' or 'support' instead of 'maintain'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 9, "column": 571}}}, "severity": "INFO"}

**Key Benefits:**
* **Improved accuracy:** If you're already reporting metrics for your OpenTelemetry-instrumented services, you will now receive more accurate and reliable data for latency, error rate, and throughput. This enhancement will be reflected in key areas such as the **Entity Explorer**, **Workloads Activity** page, and **Change Tracking Details** page.

Check warning on line 12 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.ComplexWords] Consider using 'right' or 'exact' instead of 'accurate'. Raw Output: {"message": "[new-relic.ComplexWords] Consider using 'right' or 'exact' instead of 'accurate'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 12, "column": 134}}}, "severity": "INFO"}

Check warning on line 12 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [Microsoft.Passive] 'be reflected' looks like passive voice. Raw Output: {"message": "[Microsoft.Passive] 'be reflected' looks like passive voice.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 12, "column": 224}}}, "severity": "INFO"}

* **Faster troubleshooting:** With more accurate metrics, you can gain a clearer understanding of your application's performance. This precision allows you to pinpoint issues faster, identify root causes more efficiently, and resolve them swiftly. Detailed and accurate metrics help you trace anomalies to their sources, enabling quicker fixes and reducing downtime.

Check warning on line 14 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.ComplexWords] Consider using 'right' or 'exact' instead of 'accurate'. Raw Output: {"message": "[new-relic.ComplexWords] Consider using 'right' or 'exact' instead of 'accurate'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 14, "column": 41}}}, "severity": "INFO"}

Check warning on line 14 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.Adverbs] Consider removing 'swiftly'. Raw Output: {"message": "[new-relic.Adverbs] Consider removing 'swiftly'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 14, "column": 240}}}, "severity": "INFO"}

Check warning on line 14 in src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md

View workflow job for this annotation

GitHub Actions / vale-linter

[vale] reported by reviewdog 🐶 [new-relic.ComplexWords] Consider using 'right' or 'exact' instead of 'accurate'. Raw Output: {"message": "[new-relic.ComplexWords] Consider using 'right' or 'exact' instead of 'accurate'.", "location": {"path": "src/content/whats-new/2025/01/whats-new-01-13-otelmetrics.md", "range": {"start": {"line": 14, "column": 262}}}, "severity": "INFO"}

**Next Steps:**

* **Review instrumentation:** If you're using OpenTelemetry, verify that you are reporting both traces and metrics for your services.

* ![OTelmetrics image](/images/otelmetrics.webp "OTel metrics screenshot")
Binary file added static/images/otelmetrics.webp
Binary file not shown.
Loading