Project

General

Profile

Actions

action #132752

closed

coordination #132275: [epic] Better o3 monitoring

Use proper bot account for notifications in zabbix.suse.de size:M

Added by jbaier_cz 11 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
Start date:
2023-07-14
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Currently, notifications from zabbix.suse.de are send to @jbaier_cz (who has o3-admins mailing list as his email address) which is not ideal. Proper bot account owned by the team would be a nicer solution.

Acceptance criteria

AC1: Notifications from zabbix.suse.de will work if @jbaier_cz leaves the team

Suggestions

Create a notification bot account in zabbix (it may be a user account without access to frontend, only API access is also possible), add the user to the O3 Team and set the bot email address to the mailing list. After that reconfigure the notification action to notify the bot.


Related issues 1 (0 open1 closed)

Follows openQA Infrastructure - action #132278: Basic o3 http response alert on zabbix size:MResolvedjbaier_cz

Actions
Actions #1

Updated by jbaier_cz 11 months ago

  • Follows action #132278: Basic o3 http response alert on zabbix size:M added
Actions #2

Updated by jbaier_cz 11 months ago

  • Parent task set to #132275
Actions #3

Updated by livdywan 11 months ago

  • Subject changed from Use proper bot account for notifications in zabbix.suse.de to Use proper bot account for notifications in zabbix.suse.de size:M
  • Status changed from New to Workable
Actions #4

Updated by jbaier_cz 11 months ago

  • Description updated (diff)
Actions #5

Updated by jbaier_cz 11 months ago

  • Status changed from Workable to In Progress
  • Assignee set to jbaier_cz
Actions #6

Updated by jbaier_cz 11 months ago

  • Status changed from In Progress to Blocked

Request for bot account created, blocked by SD-128548.

Actions #7

Updated by okurz 11 months ago

jbaier_cz wrote:

Request for bot account created, blocked by SD-128548.

ok. Please keep the ticket template from https://progress.opensuse.org/projects/qa/wiki/Tools#SUSE-IT-ticket-handling in mind

Actions #8

Updated by jbaier_cz 11 months ago

okurz wrote:

ok. Please keep the ticket template from https://progress.opensuse.org/projects/qa/wiki/Tools#SUSE-IT-ticket-handling in mind

Ah, right. My bad, I keep forgetting we already have that. Btw. there is no longer generic Eng-Infra in the system selection list, I hope Infra is the correct replacement.

Actions #9

Updated by ghormoon 11 months ago

jbaier_cz wrote:

Request for bot account created, blocked by SD-128548.

as noted on the ticket, there is already such user sending mails to mailinglist o3-admins@suse.de. ping me there if it should be added or replaced

Actions #10

Updated by okurz 9 months ago

Last update in https://sd.suse.com/servicedesk/customer/portal/1/SD-128548 2 days ago, still blocked

Actions #11

Updated by jbaier_cz 9 months ago

  • Status changed from Blocked to Resolved

We clarified the remaining issues in Slack, now everything should be done. Notifications are in place and they are not tied to my personal account. For tweaking the trigger action we might need to ask Infra / create a ticket due to permission problems (the action setting is only accessible to the bot and admins). The default right now is the same as it was: send e-mail for average and higher after 15 minutes.

Actions #12

Updated by tinita 9 months ago

What are the account's credentials if we need to change something?

Actions #13

Updated by jbaier_cz 9 months ago

tinita wrote in #note-12:

What are the account's credentials if we need to change something?

Unknown to me. If we need to change something we can create a ticket or maybe even request the credentials (if that is even possible). I am even not sure, if the account has GUI access enabled or not.

Actions

Also available in: Atom PDF