Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] Create portable dashboard for OTel .NET runtime metrics (#184842)…
… (#198795) # Backport This will backport the following commits from `main` to `8.x`: - [Create portable dashboard for OTel .NET runtime metrics (#184842)](#184842) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Steve Gordon","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-04T14:16:02Z","message":"Create portable dashboard for OTel .NET runtime metrics (#184842)\n\n## Summary\r\n\r\nCreate a dedicated \"portable dashboard\" for OTel .NET.\r\n\r\nThis uses metrics available in the\r\n[contrib](https://github.com/open-telemetry/opentelemetry-dotnet-contrib)\r\nruntime metrics library. These metrics are opt-in and not enabled by\r\ndefault in the vanilla SDK. Our Elastic distro brings in the package and\r\nenables them by default. Therefore, the dashboard will only work if a)\r\nthe customer uses our distro or b) they enable the metrics themselves\r\nwhen using the vanilla SDK.\r\n\r\nFurther, work is ongoing to define [semantic conventions for .NET\r\nruntime\r\nmetrics](https://github.com/open-telemetry/semantic-conventions/pull/1035).\r\nOnce complete, the metrics will be implemented directly in the .NET\r\nruntime BCL and be available with no additional dependencies. The goal\r\nis to achieve that by .NET 9, which is not guaranteed. At that point,\r\nthe metric names will change to align with the semantic conventions.\r\nThis is not ideal, but it is our only option if we want to provide some\r\nform of runtime dashboard with the current metrics and OTel distro.\r\n\r\nAs with #182107, this dashboard uses a table for some of the data and\r\nthis table doesn't seem to reflect the correct date filtering. Until\r\nthere is a solution, this PR will remain in the draft, or we can\r\nconsider dropping the table for the initial dashboard.\r\n\r\n\r\n","sha":"0600309378bf124c193c2bb041f731ad9ee5090d","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services","apm:review"],"title":"Create portable dashboard for OTel .NET runtime metrics","number":184842,"url":"https://github.com/elastic/kibana/pull/184842","mergeCommit":{"message":"Create portable dashboard for OTel .NET runtime metrics (#184842)\n\n## Summary\r\n\r\nCreate a dedicated \"portable dashboard\" for OTel .NET.\r\n\r\nThis uses metrics available in the\r\n[contrib](https://github.com/open-telemetry/opentelemetry-dotnet-contrib)\r\nruntime metrics library. These metrics are opt-in and not enabled by\r\ndefault in the vanilla SDK. Our Elastic distro brings in the package and\r\nenables them by default. Therefore, the dashboard will only work if a)\r\nthe customer uses our distro or b) they enable the metrics themselves\r\nwhen using the vanilla SDK.\r\n\r\nFurther, work is ongoing to define [semantic conventions for .NET\r\nruntime\r\nmetrics](https://github.com/open-telemetry/semantic-conventions/pull/1035).\r\nOnce complete, the metrics will be implemented directly in the .NET\r\nruntime BCL and be available with no additional dependencies. The goal\r\nis to achieve that by .NET 9, which is not guaranteed. At that point,\r\nthe metric names will change to align with the semantic conventions.\r\nThis is not ideal, but it is our only option if we want to provide some\r\nform of runtime dashboard with the current metrics and OTel distro.\r\n\r\nAs with #182107, this dashboard uses a table for some of the data and\r\nthis table doesn't seem to reflect the correct date filtering. Until\r\nthere is a solution, this PR will remain in the draft, or we can\r\nconsider dropping the table for the initial dashboard.\r\n\r\n\r\n","sha":"0600309378bf124c193c2bb041f731ad9ee5090d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/184842","number":184842,"mergeCommit":{"message":"Create portable dashboard for OTel .NET runtime metrics (#184842)\n\n## Summary\r\n\r\nCreate a dedicated \"portable dashboard\" for OTel .NET.\r\n\r\nThis uses metrics available in the\r\n[contrib](https://github.com/open-telemetry/opentelemetry-dotnet-contrib)\r\nruntime metrics library. These metrics are opt-in and not enabled by\r\ndefault in the vanilla SDK. Our Elastic distro brings in the package and\r\nenables them by default. Therefore, the dashboard will only work if a)\r\nthe customer uses our distro or b) they enable the metrics themselves\r\nwhen using the vanilla SDK.\r\n\r\nFurther, work is ongoing to define [semantic conventions for .NET\r\nruntime\r\nmetrics](https://github.com/open-telemetry/semantic-conventions/pull/1035).\r\nOnce complete, the metrics will be implemented directly in the .NET\r\nruntime BCL and be available with no additional dependencies. The goal\r\nis to achieve that by .NET 9, which is not guaranteed. At that point,\r\nthe metric names will change to align with the semantic conventions.\r\nThis is not ideal, but it is our only option if we want to provide some\r\nform of runtime dashboard with the current metrics and OTel distro.\r\n\r\nAs with #182107, this dashboard uses a table for some of the data and\r\nthis table doesn't seem to reflect the correct date filtering. Until\r\nthere is a solution, this PR will remain in the draft, or we can\r\nconsider dropping the table for the initial dashboard.\r\n\r\n\r\n","sha":"0600309378bf124c193c2bb041f731ad9ee5090d"}}]}] BACKPORT--> Co-authored-by: Steve Gordon <[email protected]>
- Loading branch information
1 parent
88926f3
commit e7f9bb9