# AWS Lambda with OpenTelemetry/dotnet - No data in the “Metrics” section **URL:** \ **Category:** APM\ **Tags:** aws-lambda\ **Created:** [April 28, 2023, 11:55am UTC](https://discuss.elastic.co/t/aws-lambda-with-opentelemetry-dotnet-no-data-in-the-metrics-section/331058 "2023-04-28T11:55:28Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![javaripa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javaripa/32/109882_2.png) [@javaripa](https://discuss.elastic.co/u/javaripa)\ **Post date:** [April 28, 2023, 11:55am UTC](https://discuss.elastic.co/t/aws-lambda-with-opentelemetry-dotnet-no-data-in-the-metrics-section/331058/1 "2023-04-28T11:55:28Z")
**Kibana version** : 8.6.1 **Elasticsearch version** : 8.6.1 **APM Server version** : 8.6.1 **Fresh install or upgraded from other version?** Fresh installation **Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**: In my AWS Lambda functions, I'm utilising the following OTEL agent for sending APM data to my self-managed elastic server. `opentelemetry/dotnet 1.3.2.732` However, I can see NO data in the Metrics section of the apropriate service, as you can easily see in the following screenshot! ![elastic-APM-Metrics](https://us1.discourse-cdn.com/elastic/original/3X/f/c/fce11b1597ce609643ee9fc7b4863c38713fea4d.png) I've checked Github for a related issue and I found this: > > > Similar to what we did for JVM metrics (https://github.com/elastic/apm-server/is…sues/4919), we should translate \[OpenTelemetry system metrics\](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic\_conventions/system-metrics.md) to the equivalent metrics produced by Elastic APM agents, if possible, so they appear under the service overview metrics in Kibana. In my point of view I think that is absolutely related with my issue. Any comments are apreciated! ---
**Author:** ![alexander.wert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexander.wert/32/95085_2.png) [@alexander.wert](https://discuss.elastic.co/u/alexander.wert)\ **Post date:** [April 28, 2023, 12:35pm UTC](https://discuss.elastic.co/t/aws-lambda-with-opentelemetry-dotnet-no-data-in-the-metrics-section/331058/2 "2023-04-28T12:35:34Z")
Hi @javaripa , I don't know which metrics OpenTelemetry/dotnet collects out of the box. But if it's `system.cpu.utilization` and `system.memory.utilization` (as described in this specification: [Semantic Conventions for System Metrics | OpenTelemetry](https://opentelemetry.io/docs/reference/specification/metrics/semantic_conventions/system-metrics/)) then there is already a fix for it in this PR: [Added support for OpenTelemetry process and system metrics by AlexanderWert · Pull Request #151826 · elastic/kibana · GitHub](https://github.com/elastic/kibana/pull/151826) So, it will be available with the next release of the Elastic stack. ---
**Author:** ![javaripa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javaripa/32/109882_2.png) [@javaripa](https://discuss.elastic.co/u/javaripa)\ **Post date:** [May 15, 2023, 2:00pm UTC](https://discuss.elastic.co/t/aws-lambda-with-opentelemetry-dotnet-no-data-in-the-metrics-section/331058/3 "2023-05-15T14:00:04Z")
Looking forward to testing it with the upcoming Kibana 8.8.0 version. ---
**Author:** ![javaripa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javaripa/32/109882_2.png) [@javaripa](https://discuss.elastic.co/u/javaripa)\ **Post date:** [May 30, 2023, 10:03am UTC](https://discuss.elastic.co/t/aws-lambda-with-opentelemetry-dotnet-no-data-in-the-metrics-section/331058/4 "2023-05-30T10:03:14Z")
Hi @alexander.wert , I have just finished with the upgrade of Kibana (8.8.0) ! Unfortunately my issue has not been resolved. I can still see NO data in the Metrics section. ---
**Author:** ![alexander.wert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexander.wert/32/95085_2.png) [@alexander.wert](https://discuss.elastic.co/u/alexander.wert)\ **Post date:** [May 30, 2023, 10:26am UTC](https://discuss.elastic.co/t/aws-lambda-with-opentelemetry-dotnet-no-data-in-the-metrics-section/331058/5 "2023-05-30T10:26:13Z")
Hi @javaripa , can you check if the metrics are being collected at all by the OTel .NET agent? For example by querying in Discover for something like the following and check if there are any documents matching this: ```auto service.name : "YOUR_SERVICE_NAME" and system.cpu.utilization : * ``` ---
**Author:** ![javaripa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javaripa/32/109882_2.png) [@javaripa](https://discuss.elastic.co/u/javaripa)\ **Post date:** [May 30, 2023, 11:31am UTC](https://discuss.elastic.co/t/aws-lambda-with-opentelemetry-dotnet-no-data-in-the-metrics-section/331058/6 "2023-05-30T11:31:18Z")
Hi @alexander.wert , It seems that the aforementioned metrics are NOT collected at all by the OTEL agent. The fields `system.cpu.utilization` and `system.memory.utilization` do not exist in the "Available fields" or the "Empty fields" section. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 20, 2023, 7:32am UTC](https://discuss.elastic.co/t/aws-lambda-with-opentelemetry-dotnet-no-data-in-the-metrics-section/331058/7 "2023-06-20T07:32:17Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.