Web service logs constantly print out DB session metrics
See original GitHub issueLooking at the webservice logs for the staging and production sites, a set of lines of the form
INFO [2019-08-23 17:43:34,611] org.hibernate.engine.internal.StatisticalLoggingSessionEventListener: Session Metrics { ... }
are constantly being printed out, making it hard to find actual logs. Would be nice to either reduce the frequency of these logs or make them appear as one line so they can be filtered out by regex.
┆Issue is synchronized with this Jira Story ┆Fix Versions: Dockstore 1.7.x ┆Issue Number: DOCK-926 ┆Sprint: Seabright Sprint 21 Viking ┆Issue Type: Story
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Logging Best Practices: The 13 You Should Know - DataSet
When you search for things on the internet, sometimes you find treasures like this post on logging, e.g. creating meaningful logs.
Read more >Logging - Appian 22.1
This article provides guidance on how System administrators can use the different types of log files that Appian produces to assess performance, analyze...
Read more >Collecting Pivotal Platform Logs and Metrics - Datadog
In this post, we will cover ways to collect these types of data. We'll go over using: Tools for accessing the Firehose; PAS's...
Read more >10+ Java Logging Best Practices: Get the Most Out of Your Logs
Use these Java logging best practices to get better insights into your app and environment, save time troubleshooting & deliver the best ...
Read more >A Step By Step Guide to Tomcat Performance Monitoring
Tomcat Performance Metrics · Memory Usage · Garbage Collection · Thread Usage · Request Throughput · Number of Sessions · Response Time ·...
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 FreeTop 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
Top GitHub Comments
In general, unless I haven’t discovered it or am using it incorrectly, the UI for searching in CloudWatch seems lacking. You can find things, but then you can’t zoom out. E.g., if I look for an error in the logs, I want to see if there are any clues in the logs right before the error.
I think the idea is more that our logs should have all the info available, but it should be easy to control the log level via regex like in this tutorial https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/FilterAndPatternSyntax.html#matching-terms-events
The problem is that these particular logs spread out across multiple lines and thus aren’t easily filterable by regex