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

What package and client is recommended for querying batch and single metrics? #24132

Open
PCaponetti opened this issue Feb 14, 2025 · 4 comments
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. Monitor Monitor, Monitor Ingestion, Monitor Query question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@PCaponetti
Copy link

I see there is /monitor/azquery, and /monitor/query/azmetrics. There are differences between them but they seem to have the same intent: get metrics. It seems only the azquery package has a function referencing single metric API but both have functions to query metrics by the batch (here and here).

Is the overlap intentional? Are there different intents for the different packages? Is one supported and the other deprecated?

@PCaponetti
Copy link
Author

Guessing @gracewilcox knows the answer, so pinging directly :)

@github-actions github-actions bot added 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. Monitor Monitor, Monitor Ingestion, Monitor Query needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. labels Feb 14, 2025
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AzmonActionG @azmonALERTS @AzMonEssential @AzmonLogA @dadunl @sameergMS.

@jhendrixMSFT jhendrixMSFT removed Service Attention Workflow: This issue is responsible by Azure service team. Client This issue points to a problem in the data-plane of the library. labels Feb 14, 2025
@github-actions github-actions bot added the needs-team-triage Workflow: This issue needs the team to triage. label Feb 14, 2025
@chlowell chlowell removed the needs-team-triage Workflow: This issue needs the team to triage. label Feb 14, 2025
@gracewilcox
Copy link
Member

Hi @PCaponetti! Thank you for your question!

The azquery module queries logs and metrics using multiple service endpoints.

This is not a long-term, sustainable design, so we decided to break up the logs and metrics into different modules. To query metrics using the data plane endpoint, use monitor/query/azmetrics . To query logs, use monitor/query/azlogs .

When the service team adds new features, they'll be added to those modules.

We are planning to deprecate the azquery module.

The transition is being tracked in this issue: #22377

@gracewilcox gracewilcox added the issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. label Feb 19, 2025
Copy link

Hi @PCaponetti. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

@github-actions github-actions bot removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. Monitor Monitor, Monitor Ingestion, Monitor Query 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

4 participants