promitor
promitor copied to clipboard
tomkerkhove
Bringing Azure Monitor metrics where you need them.
Trigger CI to verify CI bug (https://github.com/tomkerkhove/promitor/issues/2053)
CI fails to report the unit tests results, example: https://github.com/tomkerkhove/promitor/runs/6955136168?check_suite_focus=true
### Proposal Provide unit tests for AzureResourceGroupsDiscoveryBackgroundJob to ensure we handle paging correctly. ### Component Scraper ### Contact Details _No response_
### Proposal Provide guidance on running Promitor on Azure Container Apps to simplify deployment ### Component Resource Discovery, Scraper ### Contact Details _No response_
### Proposal I implemented the MySQL resource type a while ago, and while not a huge issue it is a bit annoying to see: `The metric 'cpu_credits_remaining' was not found`....
### Discussed in https://github.com/tomkerkhove/promitor/discussions/1886 Originally posted by **ahurtaud** December 14, 2021 Hello, On some big subscriptions we are seeing in promitor scrapers a lot of: ``` [15:57:55 FTL] ResourceRequestsThrottled: Number...
Introduce new validation step for verifying configured Azure Monitor metrics at startup. For every single configured metric it should: - [ ] Verify that it has access to query it...
Provide validation rule to see if aggregation interval is configured correctly which is not the case as of today, see #789 At startup, the metrics declaration should enforce valid configs.
Provide aggregation type validation for every individual metric. Azure Monitor provides a list of supported aggregation types per metric via `Microsoft.Azure.Management.Monitor.Fluent.IMetricDefinition.SupportedAggregationTypes`. We should make sure that the configured aggregation type...
Aggregation intervals should be an exact match instead of determining the closest aggregation interval that is available. We are changing this give it can result in odd metrics. Imagine you've...
Metadata
Owner
Metadata
Bringing Azure Monitor metrics where you need them.