Search Result
Collapse
6 results in 0.0026 seconds.
Keywords
Members
Tags
-
Any solutions for Zabbix high level alerting
We are looking for ways to define high level trigger(s) when any usual trigger gets triggered for a number of times in a certain time period, e.g., any trigger gets triggered 3 times within a week. I was wondering if there are any approaches to achieve this goal? Your ideas and inputs would be much... -
TiddleMiddle started a topic Creating Log Check Triggers with a General Error Trigger + Triggers for Known Errorsin Zabbix HelpCreating Log Check Triggers with a General Error Trigger + Triggers for Known Errors
I am attempting to write a series of triggers for a single log check item.
I want to have a starting trigger that catches any unknown string of "ERROR", this is easy enough to do. I want to be able to incrementally add known errors that can trigger in its place, such as "ERROR:...Last edited by TiddleMiddle; 21-10-2020, 20:37. -
Eventlog trigger (Windows)
Hello, i'm kinda new to zabbix and I have problems to create trigger for eventlog item. I would like to monitor Error and Critical events but with sending me notification let's say only once per hour of same event if it creates multiple times. Hope this make sense
This is my trigger... -
Monitoring Apt-get with zabbix
Hi Team
I am trying to monitor the activities/ commands with apt-get ( install/remove/upgrade/update) with zabbix on my ubuntu machine . But I am getting error not supported by zabbix agent.
The item key is like this
log["/var/log/apt/history.log","Install|Upgrade|Error|Remove","UTF-8",4]... -
trigger по evetid (windows)
Добрый день, как правило создать триггер по evetid?
у меня сейчас срабатывает при каждом получении события с evetid 1102
а надо чтобы срабатывал триггер когда событие с evetid 1102 генерируется 5 раз в течении 6ти минут
помогите пожалуйста -
consistant alert emails, no log entries
I have a very odd issue that I haven't had any luck tracking down.
There is a service check net.tcp.service[https] that fires every 90 seconds on 40 hosts. Every day at 2:30 AM and 2:30 PM, this check fires a trigger that the service is down for approximately 10 of these hosts. It's...