-
Notifications
You must be signed in to change notification settings - Fork 202
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
livemetrics does not pick instrumentation key in code. #969
Comments
we are also facing this issue, support case created, this is delaying our deployment to production as we wanted to send different instrumentation keys for on premise applications
Application Type: Dynamic Web with Servlet (java) |
@trask please update the doc (Please note that Live Metrics does not support reading instrumentation key from code.) that this is supported from newer version of sdk. |
Thanks @cijothomas, I have created docs PR MicrosoftDocs/azure-docs#35789. |
Expected behavior
Configured ikey in code as per below doc.
https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-get-started?toc=%2Fazure%2Fazure-monitor%2Ftoc.json#alternative-ways-to-set-the-instrumentation-key
LiveMetrics and every other telemetry should pick this instrumentationkey.
Actual behavior
Describe what actually happened that was unexpected.
All expect Livemetrics is picking the instrumentation key.
To Reproduce
Follow doc above to set ikey in code, NOT in ai.xml.
Sample Application
If applicable, provide a sample application which reproduces the issue.
System information
Please provide the following information:
Logs
Turn on SDK logs and attach/paste them to the issue. If using an application server, also attach any relevant server logs.
Be sure to remove any private information from the logs before posting!
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: