Verbose logging on every CloudWatch API call
See original GitHub issueHey, we’re grateful for cloudwatch_exporter and would like to have better visibility of what requests are fired to the AWS API, especially to monitor cost.
Would you be interested in a pull request that adds log output for every request made? I think this should go to log level FINE
. Assuming that it would be too verbose for the standard case.
It would make sense to have the log level be configurable, e. g. via a command line flag. Is that already the case? If not, that could be part of the PR too.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Setting up CloudWatch logging for a REST API in API Gateway
Set up CloudWatch API logging using the API Gateway console · Choose Enable Access Logging under Custom Access Logging. · Enter the ARN...
Read more >Logging Amazon CloudWatch API calls with Amazon CloudTrail
CloudTrail captures API calls made by or on behalf of your Amazon account. The captured calls include calls from the console and code...
Read more >How to Enable Logging on Every AWS Service in Existence ...
What Gets Logged? Request-level and field-level logs for the GraphQL API. Where Do They Go? CloudWatch Logs. Are They Enabled by Default ...
Read more >Python CloudWatch Logging — watchtower documentation
It aggregates logs into batches to avoid sending an API request per each log message, while guaranteeing a delivery deadline (60 seconds by...
Read more >Eleven Tips on How to Get the Most of AWS Logging - Papertrail
Running applications on AWS can often involve using many services, each of which ... CloudWatch Logs encrypts log data in transit and at...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The PR wasn’t needed. Logging each request worked for me with the explanation given in https://www.robustperception.io/viewing-logs-for-the-jmx-exporter
I’m okay with that, I’d expect the logging levels to come to the logging library from wherever it usually gets it (system properties or xml).