Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy gitter bot to write annotations to Grafana #425

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

betatim
Copy link
Member

@betatim betatim commented Feb 18, 2018

Fixes #312

This is a (very) simple gitter bot that creates grafana annotations for messages that start with !log.

Can we run this on the k8s cluster as well? Or would it make sense to run it somewhere else so it doesn't go down when we have a problem? Or ...?

@minrk
Copy link
Member

minrk commented Feb 19, 2018

Running this on the cluster makes sense to me. Do you want to take a stab at that here?

@betatim
Copy link
Member Author

betatim commented Feb 19, 2018

I'll take a stab at making this run on the cluster. An opportunity to learn how to add new things to the helm chart. I guess if the cluster is so broken that the bot doesn't work any more chances are grafana&co are down too.

@minrk
Copy link
Member

minrk commented Feb 19, 2018

True. If you want an example, #398 is also adding a new pod to run in the cluster. I can't tell you if it's good example yet, though.

@yuvipanda
Copy link
Contributor

hmm, after today's incidents with Grafana, I'm wondering if we should run this in the same cluster at all. Perhaps a separate 'misc' cluster that runs our various bots and grafana? That would also allow us to put them in a separate repo.

@betatim
Copy link
Member Author

betatim commented Feb 21, 2018

We should definitely make this bot more robust towards grafana failures. I think our deployment got "stuck" once yesterday because it couldn't create the grafana annotation. It feels like that shouldn't happen and for this bot means it needs to have a buffer/queue of some kind.

@yuvipanda
Copy link
Contributor

Also wanted to say, let's not make the perfect enemy of the good, etc. So this should go ahead in whatever form makes it deployable :)

@minrk
Copy link
Member

minrk commented Apr 19, 2018

I think we should create a support cluster, and I will work on that after releasing jupyterhub 0.9 if nobody else does it first, but I think we can and should do this one in the existing cluster in the meantime, since I think it'll be handy.

@betatim would you like to take a stab at adding a chartpress config for building and using the image?

@choldgraf
Copy link
Member

@betatim if the grafana message posting automation is blocking on this PR, why don't we start with a small addition to the binder SRE tools that will just use the gitter API to grab all the lines with !log in them and collect them as a time-stamped dataframe, or something like this?

@yuvipanda yuvipanda changed the title Add basic gitter bot for ops log Deploy gitter bot to write annotations to Grafana Nov 2, 2018
@yuvipanda
Copy link
Contributor

yuvipanda commented Nov 2, 2018

@betatim @minrk I picked this back up, and made some progress.

  1. Builds image automatically
  2. Uses asyncio to listen to multiple rooms at the same time

Still to do:

  • Find a way to auth to Gitter without giving it my (irrevocable!) gitter personal access token
  • Build some network resiliency into the script

betatim and others added 4 commits November 2, 2018 15:28
- Gitter secret comes from a new github bot account I created.
  Username and Password for it are in secrets/bot-accounts.yaml
@yuvipanda
Copy link
Contributor

Setup gitter key for this. Comes from a github bot account I created. Account details for the bot account are in secrets/bot-accounts.yaml

@manics
Copy link
Member

manics commented Jul 13, 2021

What's the plan here?

@yuvipanda
Copy link
Contributor

I'd still love to get this deployed!

@betatim
Copy link
Member Author

betatim commented Jul 14, 2021

If someone wants to take over this PR and finish it that would be fine with me

@consideRatio consideRatio marked this pull request as draft April 28, 2023 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Shared operations log
5 participants