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

Add Microsoft Application Insights as a supported trace datastore #2590

Closed
kdhamric opened this issue May 25, 2023 · 0 comments · Fixed by #2691
Closed

Add Microsoft Application Insights as a supported trace datastore #2590

kdhamric opened this issue May 25, 2023 · 0 comments · Fixed by #2691
Assignees
Labels

Comments

@kdhamric
Copy link
Collaborator

We want to add Microsoft Application Insights as a supported trace datastore so Azure customers using tracing can utilize Tracetest and trace-based testing techniques against their distributed apps. We have confirmed with the team at Microsoft that the trace data can be queried via the Azure Monitor Log Analytics API (https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/overview).

AC1: Microsoft Application Insights is added to the Settings screen under Configure Data Store

AC2: Once configured, Tracetest is able to use the API to successfully pull back a trace from Azure Monitor and build tests based on it.

AC3: Microsoft Application Insights is added as a supported trace data store in the docs under https://docs.tracetest.io/configuration/overview.

AC4: There is a recipe showing how to use Microsoft Application Insights with an Azure based project and test the project via Tracetest.

AC5: This integration is added to the Tracetest.io integration page.

@kdhamric kdhamric added feature request triage requires triage labels May 25, 2023
@xoscar xoscar self-assigned this May 31, 2023
@xoscar xoscar linked a pull request Jun 8, 2023 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants