Skip to content
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

[dev.icinga.com #12243] Database StatsLogger too noisy #4408

Closed
icinga-migration opened this issue Jul 27, 2016 · 2 comments
Closed

[dev.icinga.com #12243] Database StatsLogger too noisy #4408

icinga-migration opened this issue Jul 27, 2016 · 2 comments
Labels
area/db-ido Database output area/log Logging related bug Something isn't working

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12243

Created by iustin on 2016-07-27 21:31:00 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-07-27 21:31:00 +00:00 (in Redmine)

Icinga Version: 2.4.10
Backport?: Not yet backported
Include in Changelog: 1

I've recently enable a database module and since then I see in the logs every 15 seconds:

Jul 27 22:03:28 debian icinga2[6926]: [2016-07-27 21:56:13 +0200] information/IdoPgsqlConnection: Query queue items: 0, query rate: 3.65/s (219/min 1141/5min 3393/15min);

Looking at the sources, it seems that this log message is generated unconditionally at info severity, with no method to disable. Note that in my syslog features I have:

object SyslogLogger "syslog" {
    severity = "warning"
}

But this still doesn't stop the logging from the db module. Is it really needed to log that often an informational message? It would make sense to only log when the database can't keep up, but just for the query rate it seems somewhat pointless (compared to actually sending this to a stats system).


Relations:

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-12-08 00:52:44 +00:00

  • Duplicated set to 12513

@icinga-migration icinga-migration added bug Something isn't working area/db-ido Database output labels Jan 17, 2017
@dnsmichi dnsmichi added the area/log Logging related label Feb 8, 2017
@dnsmichi
Copy link
Contributor

It helps debugging. Since the log itself is an application log, it doesn't hurt to keep these log entries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/db-ido Database output area/log Logging related bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants