action #77317
open
chat bot to conduct daily checks, alerts, reminders, etc.
Added by okurz over 3 years ago.
Updated almost 3 years ago.
Description
Motivation¶
To ensure the QE Tools has a central place for urgent issues and critical alerts we would like to have an RC chat bot informing us about alerts and such
Acceptance criteria¶
- AC1: RC bot is connected to team chat channel
- AC2: Administration is documented and understood by at least two persons
- AC3: Bot writes in team chat channel for any OSD alert
Suggestions¶
Since I looked into this previously I can share some info:
- Grafana can make use of the Slack Notification Channel to post alerts into RC (https://github.com/grafana/grafana/issues/9251#issuecomment-354804092)
- It seems like API-Keys to RC are once again bound to personal accounts. So we would need to request a new RC-account for such a bot to not depend on a single person again
- Description updated (diff)
- Target version changed from future to Ready
nicksinger wrote:
Since I looked into this previously I can share some info:
- Grafana can make use of the Slack Notification Channel to post alerts into RC (https://github.com/grafana/grafana/issues/9251#issuecomment-354804092)
oh wow, that should make it easier :)
- It seems like API-Keys to RC are once again bound to personal accounts. So we would need to request a new RC-account for such a bot to not depend on a single person again
Yes, I think there are different kind of accounts and I already checked in the past and the SUSE RC admins are happy to provide an account for us if we just tell them what kind of account it should be. I am sure we can ask them what they suggest. We can just ask in #rocket-help
Adding the ticket to our backlog with the updated description.
EDIT: found in my notes: long time ago received a response from dmueller in https://chat.suse.de/channel/collaboration-platform?msg=JbNzWZ9Ky6g83ENeK that he could create an account. We should just find out in before if ee need "user account, there are bot accounts, there are push accounts (used for CI integrations)". We could try any own account for testing of course
- Related to action #81106: test out chat service notifications, e.g. matrix, from github actions size:M added
- Priority changed from Normal to Low
- Status changed from Workable to New
moving all tickets without size confirmation by the team back to "New". The team should move the tickets back after estimating and agreeing on a consistent size
- Target version changed from Ready to future
Also available in: Atom
PDF