action #175210
closed[o3][zabbix] reconsider e-mail notification settings size:S
0%
Description
Observation¶
The current configuration is to receive an e-mail for a problem if:
- The problem is there for at least for 15 minutes
- The problem severity is at least Average (i.e. Average, High or Critical); we are not informed about Information and Warning via e-mail
Maybe we want to reevaluated those rules.
Acceptance criteria¶
- AC1: We receive an email on "WARNING" conditions from zabbix
Suggestion¶
Updated by jbaier_cz about 2 months ago
- Related to action #132752: Use proper bot account for notifications in zabbix.suse.de size:M added
Updated by jbaier_cz about 2 months ago
- Related to action #174316: [o3][zabbix][alert] no email about zabbix alerts including storage and cpu load size:S added
Updated by robert.richardson about 2 months ago
- Subject changed from [o3][zabbix] reconsider e-mail notification settings to [o3][zabbix] reconsider e-mail notification settings size: S
- Description updated (diff)
- Status changed from New to Workable
Updated by okurz about 1 month ago
- Subject changed from [o3][zabbix] reconsider e-mail notification settings size: S to [o3][zabbix] reconsider e-mail notification settings size:S
Updated by robert.richardson about 1 month ago
- Assignee set to robert.richardson
Updated by robert.richardson about 1 month ago
- Status changed from Workable to In Progress
Updated by robert.richardson about 1 month ago
- Status changed from In Progress to Feedback
I'm unsure on how to proceed, on https://progress.opensuse.org/projects/openqav3/wiki/Wiki#Monitoring it is stated that
Alert notification is configured via trigger action in a special Infra-owned RO bot account. E-mail notification is in place for average problems and higher.
which sounds to me like i need to open a SD ticket similar to this one to increase the notification verbosity?
however further below it says
Configuration of alerts is done in /etc/munin/munin.conf
i checked /etc/munin/munin.conf and it has this setting commented out
# Use this to always send an email, not oly when the status changes
#contact.o3admins.always_send warning critical
Would it be enough to uncomment this, (maybe it should be contact.o3admins.always_send warning average high critical instead), or do i need to open a sd ticket ?
Updated by jbaier_cz about 1 month ago
Munin and Zabbix are two different monitoring platforms. This ticket is about Zabbix where the alerting is done as described in #132752. As we do not have credentials for the bot user to change the setting, SD ticket is needed. Changing /etc/munin/munin.conf will not (should not) affect Zabbix in any way.
Updated by robert.richardson about 1 month ago ยท Edited
- Status changed from Feedback to Blocked
jbaier_cz wrote in #note-8:
Munin and Zabbix are two different monitoring platforms. This ticket is about Zabbix where the alerting is done as described in #132752. As we do not have credentials for the bot user to change the setting, SD ticket is needed. Changing /etc/munin/munin.conf will not (should not) affect Zabbix in any way.
ok i see, thanks
created a sd ticket to change the setting and will block the current ticket on that
Updated by robert.richardson about 1 month ago
- Status changed from Blocked to Feedback
The SD ticket mentioned above is resolved, waiting for the first mail with "WARNING" Severity to close this issue.
Updated by okurz about 1 month ago
I got an email with subject "Problem: Test trigger for #175210", looks good I guess?
Updated by jbaier_cz about 1 month ago
I created that trigger to test the settings and forgot it already in the mean time. Glad that the alerting worked :)