Closed esttenorio closed 3 years ago
Thanks for the feedback, we’ll investigate asap.
Hi @esttenorio , an interval of less than 1 minute is not supported by the service team currently.
Unfortunately, the backend data store only stores data at 1 minute resolutions and the only way to accomplish this would be to use Kusto queries over log data.
Even if metric data is being sent every second, the backend will be aggregating and rolling it up into 1 minute buckets so that data is lost there is no way to query MDM for less than 1 minute intervals.
we are planning to improve the error message for this situation and tracking it here https://msazure.visualstudio.com/One/_workitems/edit/10693931
Hi @esttenorio. 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.
Hi @esttenorio, since you haven’t asked that we “/unresolve
” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve
” to reopen the issue.
We are using the Azure Monitor Query client library to fetch both Logs and Metrics to create a custom monitoring Dashboard.
For logs, we have no issues since the interval can be defined with
by bin(TimeGenerated, 10s)
in the Kusto query. But for metrics, our team has developed some custom Telegraf plugins that are sending metrics to specific resources. When using the Monitor Query lib, the lowest interval that can be defined is 1m even when the plugin can emit data up to every 10s. We can confirm this by using the Chronograf InfluxDB local ui:Since Azure Monitoring does not provide a way to visualize Azure Metrics, using this lib is the only way we've found to do extract metrics and show them next to some other data from Azure Monitor Logs. We are using the lib to get live monitoring of remote machines and we do require smaller intervals to detect "jitter", abnormal fluctuations, and spikes. With the 1m interval, all the spikes and fluctuations are averaged over a minute and are not shown on the output data.
For our application, 5s or 10s would be ideal. Is it possible to remove the 1m limitation and support smaller intervals?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.