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
Duplicate/Invalid metric errors when starting useAzureMonitor #1218
Comments
We are aware of this warnings, but these should not cause any change of behavior in the SDK, we fixed that in Azure Monitor OpenTelemetry Exporter recently and should be published soon. Related to Other issue related to Azure Instrumentation is also not causing problems but we are working on trying to avoid the unnecessary noise. |
Thanks, I have another issue I have set a startActiveSpan but it is not showing in the appinsights metrics. |
@pedro37 can you elaborate on your issue? what kind of metrics are you expecting to see? |
Yes, I have essentially the following code snippet and I am expecting span-name to appear in the application insights metric dropdown, using the config above
|
These are not simply warnings. These output to the terminal when run, so it is not currently possible to use the Azure Monitor OpenTelemetry solution in a CLI, since every execution displays this (incredibly odd) "warning" to the users and the CLI developers do not have the ability to control this behavior: #1107 (comment) |
@hectorhdzg any update on this? We use
yarn.lock entry
|
I am also getting similar errors on startup....I am following the "upgrade" path...for example....
...additionally, I am not sure why I am getting this error...
I am initializing it this way...
The value of Also one other question (I can create a separate item for this if needed)....am I still allowed to track custom metrics and events thusly?
|
I add config as per README and get duplicate errors in the config am I missing something?
The text was updated successfully, but these errors were encountered: