Skip to content
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

azure-spring-boot traces don't show up in application insights #15773

Closed
Vibhuti0910 opened this issue Sep 28, 2020 · 4 comments
Closed

azure-spring-boot traces don't show up in application insights #15773

Vibhuti0910 opened this issue Sep 28, 2020 · 4 comments
Assignees
Labels
azure-spring All azure-spring related issues Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@Vibhuti0910
Copy link

Describe the bug
Upon updating azure-spring-boot version from 2.1.7 to 2.1.10 in pom.xml file, integration with azure monitor fails. The logs stop getting populated in application insights.
The bean AzureMonitorMetricsExportAutoConfiguration is conditional on resource "metrics.enable.config" (link to resource). This resource does not get added to classpath, and upon adding manually also the issue remains the same.

Exception or Stack Trace
No exception is thrown

To Reproduce

  1. Update azure-spring-boot version to 2.1.10 in pom.xml of module
  2. Add log message and check in Traces table in application insights. The log message does not get added there.

Code Snippet
N/A

Expected behavior
Log messages should get reflected in Traces table in application insights, like with azure-spring-boot version 2.1.7

Screenshots
N/A

Setup (please complete the following information):

  • OS: Windows 10
  • IDE : IntelliJ
  • Version of the Library used: 2.1.10

Additional context
Add any other context about the problem here.

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • [Yes] Bug Description Added
  • [Yes] Repro Steps Added
  • [Yes] Setup information Added
@msftbot msftbot bot added needs-triage This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 28, 2020
@joshfree joshfree changed the title [BUG] azure-spring-boot traces don't show up in application insights Sep 28, 2020
@joshfree joshfree added this to the [2020] December milestone Sep 28, 2020
@joshfree joshfree added azure-spring All azure-spring related issues and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Sep 28, 2020
@joshfree
Copy link
Member

Thanks for reporting this issue @vibhuti99. @srnagar will follow up as he's currently working on a closely related area for Azure SDKs.

@chenrujun
Copy link
Member

Hi, @joshfree ,

Did you want to @ @saragluna , not @srnagar ?

@saragluna
Copy link
Member

Hi @vibhuti99, sorry for the late reply. We've deprecated the azure-spring-boot-starter-metrics, check it here.

Please check https://github.com/Microsoft/ApplicationInsights-Java to see how to use Application Insights in Java.

@jialindai jialindai added the Client This issue points to a problem in the data-plane of the library. label Feb 20, 2021
@yiliuTo
Copy link
Member

yiliuTo commented Mar 19, 2021

Closing this issure because no response from the customer.

@yiliuTo yiliuTo closed this as completed Mar 19, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
azure-spring All azure-spring related issues Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

7 participants