MSSQL Percent of log using is high generating inconsistent Triggers
Version 6.2.2 with 6.2.2 Agent2. Our Percent of log using is high Problems are generating inconsistent triggers. As in sometimes they execute the Trigger Action and sometimes they don't. Same server, same conditions. Is this a known bug or something? See the screenshot below. Out of 7 Problems only 2 of them executed a Trigger Action. All 7 should have generated the same Trigger Action. What could possibly cause this if not a bug?
-
-
I would say, user permissions... that user, who is running actions does not see all hosts... -
The users are in the DBA group which has access to read all templates and DBA hosts. They receive every other trigger from these hosts. The percent of log using is high is the only trigger that behaves this way. Also, in the screenshot 5 of those triggers are the exact same DB and host. Yet only 1 instance sent an email.Comment
-
No ideas from my side right now..
Comment
-
Do you know if there is a log file for the Trigger Actions? Something where I might be able to figure out what the issue is.... I'm planning on upgrading our Zabbix instance soon but I'm doubtful that will fix this as its such a random issue yet specific to only a single trigger...Comment
-
How does your action conditions look like?
Action is executed, if conditions match. Is there any tag based condition, which maybe do not match? My experience with actions not being executed have always been either permission issues or something with not matching conditions...
There is no logfile for what you ask.Comment
-
Any trigger that contains "Percentage of log using is high" in the name.
The user in the operation is configured with a distribution group email and sends to all the DBAs. It has read/write access to all the DB hosts, OS Templates and SQL Templates. I'm going to add a Super Admin user to the operation though to see if that makes any difference. If the Super Admin user gets the alerts and the DBAs do not then I guess it would have to be a permissions thing... however it still wouldn't make sense given its the exact same conditions and randomly it tries to send 1 time but not others.
Operations:Send message to users: <user removed for privacy> via Email (HTML) for Business Hours Immediately Default
Comment
Comment