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
Custom metrics aren't published for storage accounts #20150
Comments
Further to this, I have checked multiple other resource types (see below for a list) and all were able to receive and display custom metrics. The resource types I tried (which all work) are:
|
@johndowns Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience. |
@anirudhcavale - FYI |
@johndowns can you do a quick sanity check for me. Can you validate if you are able to query the metrics out via the REST Metrics API for the custom metrics on the storage account? You can use the armclient (https://github.com/projectkudu/ARMClient). Once you install it run the following commands: (replace these with your resource and metric names)
|
@anirudhcavale I just checked, and yes, the metrics do appear when I query them through the ARM API. |
@anirudhcavale Another thing I noticed - when I have a metric with dimensions, other resource types show the 'split' and 'filter' buttons in the portal UI and let me select the dimension to split or filter on. When I have metrics against a storage account, though, these buttons aren't enabled. |
@anirudhcavale, any update to the above? |
@johndowns I'm able to reproduce this issue with a storage account. It appears to be a UX rendering issue. I will follow up on my side, but I can also have you file a support ticket to track this please? |
Update! @johndowns we found the issue in the UX rendering of custom metrics for storage accounts. We are working on a fix, it will likely be rolled out worldwide during the first week of Jan. Thank you for reporting this and helping us find it! |
Fantastic! That's great news @anirudhcavale. Thanks for the update. Re a support ticket - unfortunately I don't have access to create one currently. But it sounds like this won't be necessary anyway? |
Correct, no need for support ticket :), we found the issue and are fixing it. |
Thanks for the update @anirudhcavale and thanks again for bringing this to our attention @johndowns. |
Just confirming that this has now been fixed. Thanks for looking into this! |
Actually I spoke too soon. The metrics are published and are now visible on the UI, but dimensions aren't shown. Again the issue seems to be limited to storage accounts. Should I reopen this issue or create a new issue @anirudhcavale? |
@johndowns nope, lets just use this one. Its a known bug, we already have a fix ready. Just waiting on a deployment. |
@johndowns the issue should have been fixed late last week. |
@anirudhcavale Thanks - I just re-tested though and dimensions still aren't being shown for storage accounts. I tested using the southcentralus region. |
The bug we found had to do with the the azure portal caching older versions. Can I ask you to try an in private browsing session? If the issue still persists is there an email I can reach you at to further debug? |
I just tried using a private browsing session, and using a different browser with a completely cleared cache. I still can't see the dimensions. Sure, you can contact me at john@johndowns.co.nz. |
I've been testing publishing custom metrics with various resource types. In many cases they work well. However, it appears that Azure Storage accounts (i.e. resources of type Microsoft.Storage/storageAccounts) don't process custom metrics properly.
If I publish a metric to a storage account then the metric is accepted by the API, and the metric appears in the portal UI list of metric namespaces and names. But no data appears, even several hours after I published it.
If I use the exact same code to publish to a different resource type (say, Microsoft.Web/sites), the metric appears almost instantly.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: