Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Logging does not show root cause
See original GitHub issueI am having problems finding the cause of printed errors. They provide information about what the results were, but not what caused it, or what paths were attempted.
In the case of AzureMonitor, when I had invalid role permissions, I was getting
fail: Promitor.Integrations.AzureMonitor.Logging.AzureMonitorIntegrationLogger[0]
Exception in 5: Microsoft.Azure.Management.Monitor.Fluent.Models.ErrorResponseException: Operation returned an invalid status code 'Forbidden'
This tells me that some url probably received an HTTP 403, but that’s all I know. I think the URL, status code and the actual error message from the API would of interest here.
When I had configured the proper roles, I was getting the following error
fail: Promitor.Integrations.AzureMonitor.Logging.AzureMonitorIntegrationLogger[0]
Exception in 5: Microsoft.Azure.Management.Monitor.Fluent.Models.ErrorResponseException: Operation returned an invalid status code 'NotFound'
I don’t know what isn’t found. More verbosity in the logs would be nice. Or am I missing a flag?
Configuration
Config
server:
httpPort: 8080
prometheus:
# metricUnavailableValue: NaN
# enableMetricTimestamps: true
scrapeEndpoint:
baseUriPath: /metrics
metricsConfiguration:
absolutePath: /config/metrics-declaration.yaml
telemetry:
containerLogs:
isEnabled: false
defaultVerbosity: debug
azureMonitor:
logging:
informationLevel: BodyAndHeaders
isEnabled: true
Metrics
version: v1
azureMetadata:
tenantId: xxx
subscriptionId: xxx
resourceGroupName: promitor
metricDefaults:
aggregation:
interval: 00:05:00
scraping:
# Every minute
schedule: "0 * * ? * *"
metrics:
- name: promitor_demo_azuresqlmanagedinstance_nodes
description: "The amount of nodes for an Azure SQL Managed Instance."
resourceType: SqlManagedInstance
azureMetricConfiguration:
metricName: virtual_core_count
aggregation:
type: Average
resources:
- instanceName: my-special-postgres-instance
Specifications
- Version: 1.4.0
- Platform: Docker on Linux
- Subsystem:
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for the response. Yeah, it appeared to be an error caused by myself. Sorry about that. Feel free to close this issue now. I don’t expect you to do anything about this feedback, but I’ll just post my thoughts as I’m working with it.
Azure Monitor logging
I’m still not sure what the
azureMonitor.logging.informationLevel: BodyAndHeadersdoes. Is this for the requests towards the Azure Monitor API?API requests logging
For requests that are being made to the Azure Monitor API, like here, where I’m getting null values, if I could enable verbose logging on the HTTP requests, e.g. see the URL being queried, I could go straight into the API and look around for myself.
In this particular instance, it appeared to be that intervals < 5 minutes only occationally returned data.
After setting aggregation interval to 5 minutes, both values returned data for all requests. I suspect this isn’t an isse with Promitor, but rather the upstream API restrictions/limitations (?).
Happy to help and thanks for trying/using Promitor.
Feel free to let me know if you want to be listed on https://promitor.io/#Customers