Open
Description
- Package Name: @azure/monitor-opentelemetry
- Package Version: 1.7.0
- Operating system: Azure Function App
- Is the bug related to documentation in
Describe the bug
We have a setup to install and instrument our application running on function app, telemetry was send to our application insight with Azure Monitor Private Link Scope (AMPLS)
As we saw from https://learn.microsoft.com/en-us/azure/azure-monitor/app/statsbeat?tabs=eu-java%2Cnode, there are feature that send data to Microsoft own app insight. We found it seem to be this one
Even after we open firewall, the error still remains in the traces
{"stack":"Error: PeriodicExportingMetricReader: metrics export failed (error RestError: getaddrinfo ENOTFOUND westeurope-5.in.applicationinsights.azure.com)\n at doExport (/home/site/wwwroot/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:76:23)\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async PeriodicExportingMetricReader._doRun (/home/site/wwwroot/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:84:13)\n at async PeriodicExportingMetricReader._runOnce (/home/site/wwwroot/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:55:13)","message":"PeriodicExportingMetricReader: metrics export failed (error RestError: getaddrinfo ENOTFOUND westeurope-5.in.applicationinsights.azure.com)","name":"Error"} []
and another one
Export took longer than [ 30000 ] milliseconds and timed out.
To Reproduce
Steps to reproduce the behavior:
- Azure setup with nodejs function app, application insight, hub and spoke network, azure monitor private link scope, firewall deny by default
- Open firewall for westeurope-5.in.applicationinsights.azure.com
- Instrument application with @azure/monitor-opentelemetry
- Check the traces in application insight
Expected behavior
A way to disable statbeats or fix the error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
This issue points to a problem in the data-plane of the library.Monitor, Monitor Ingestion, Monitor QueryWorkflow: This issue is responsible by Azure service team.Issues that are reported by GitHub users external to the Azure organization.Workflow: This issue needs attention from Azure service team or SDK teamThe issue doesn't require a change to the product in order to be resolved. Most issues start as that