hello everyone. We have a few log growths alerts, and notified the DBA's. they checked and reduced the logs, so the nagios check should back to normal. however the counter still in critical.
I would need to know what parameters are being considered in order to get the result. the alert says "CRITICAL: Log Growths is 38.0" where this 38 comes from?.
i checked the .py file as well but the query result acording to the DBA team is empty.
Can i have some clarification about what and how this growth is being monitored?
thanks in advance.
Log Growth check_mssql_database.py
Re: Log Growth check_mssql_database.py
Hello,
Log Growths is a counter in SQL Server. It counts the number of times a transaction log has grown since the database has been online. To my knowledge, that counter does not reset unless you restart SQL Server.
Log Growths is a counter in SQL Server. It counts the number of times a transaction log has grown since the database has been online. To my knowledge, that counter does not reset unless you restart SQL Server.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Log Growth check_mssql_database.py
so, the only way to get rid of the critical is increasing the thresholds?
Re: Log Growth check_mssql_database.py
The plugin does store temporary files in the /tmp folder.
Try removing the files starting with mssql-* from that folder and see if the plugin returns the changed value.
Try removing the files starting with mssql-* from that folder and see if the plugin returns the changed value.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Log Growth check_mssql_database.py
Unfurtunatelly it does not do the trick. i have figured out the correct DB query, and it actually returns 38 which is bigger than the ones we have configured.tgriep wrote:The plugin does store temporary files in the /tmp folder.
Try removing the files starting with mssql-* from that folder and see if the plugin returns the changed value.
i think that the only way to get rid of the critical is modifiyng the thresholds or restarting the sql services.
Re: Log Growth check_mssql_database.py
Either method should work fine - increasing the thresholds in your command or restarting the server. Let us know if you have any further questions or it is OK to close this topic. Thank you!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Log Growth check_mssql_database.py
thanks you can close the tkt.