Skip to content
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.

Setting up monitoring/alerts #2

Closed
7 tasks done
victorb opened this issue Jan 29, 2017 · 10 comments
Closed
7 tasks done

Setting up monitoring/alerts #2

victorb opened this issue Jan 29, 2017 · 10 comments

Comments

@victorb
Copy link
Collaborator

victorb commented Jan 29, 2017

Acceptance Criteria

  • Can view jenkins monitoring dashboards
  • Can deploy changes to monitoring by reading the documentation
  • Will get alerts if certain metrics goes under the threshold

Tasks

  • checkout Prometheus integration for jenkins and apply if possible
  • Connect to existing Prometheus deployment
  • Setup dashboard
  • Setup alerts

Dependencies

Depends on #1

@ghost
Copy link

ghost commented Jan 30, 2017

Remember what this means?

  • Can check out the monitoring dashboards

Can view the monitoring dashboard? Or: can run the dashboard locally, in an automated way?

@victorb
Copy link
Collaborator Author

victorb commented Jan 30, 2017

@lgierth my intention was "can view the monitoring dashboard".

Thinking about it now, we should probably have two tasks, one for being able to run monitoring locally and one for having it working in production. What you think?

@ghost ghost added in progress and removed ready labels Jan 30, 2017
@ghost
Copy link

ghost commented Jan 30, 2017

Yeah let that running-locally be separate: ipfs/infra#52

@victorb
Copy link
Collaborator Author

victorb commented Jan 30, 2017

Ok, in that case, this task would depend on us running jenkins deployed somewhere before you can start working on this task. Correct?

@victorb victorb closed this as completed Jan 30, 2017
@victorb victorb reopened this Jan 30, 2017
@ghost
Copy link

ghost commented Jan 30, 2017

Nah I can get started with the local jenkins

@ghost ghost added ready in progress and removed ready labels Jan 30, 2017
@ghost
Copy link

ghost commented Jan 31, 2017

#11 enables the scraping endpoint for prometheus, and the dashboard is here: http://metrics.ipfs.team/dashboard/db/jenkins?from=now-1h&to=now -- I simply imported the one from grafana.net and I'm not very convinced by it.

The dashboard will need tuning when there's actual jobs to monitor :) And that's also when we can start setting alert conditions.

Prometheus is currently set to scrape [fce3:5702:8051:3e65:3a36:1299:c458:1470]:8090/prometheus and we can change that to what comes out of #8.

@ghost ghost added ready and removed in progress labels Jan 31, 2017
@ghost ghost added in progress and removed ready in progress labels Jan 31, 2017
@ghost ghost added ready in progress and removed ready labels Jan 31, 2017
@ghost
Copy link

ghost commented Feb 2, 2017

I'm wrapping this up with ipfs/infra#235 which makes all provsn units systemd-compatible, so that we now also get host metrics (cpu, ram, io).

The dashboard should start showing numbers tomorrow when @victorbjelkholm brings jenkins back up (I broke it). Over the rest of the sprint we'll tune the dashboard and add alerts as we see fit.

@ghost
Copy link

ghost commented Feb 4, 2017

Splitting off tuning and alerting to #31.

@ghost ghost closed this as completed Feb 4, 2017
@ghost ghost removed the ready label Feb 4, 2017
@victorb
Copy link
Collaborator Author

victorb commented Jan 24, 2018

Moved infrastructure for jenkins and monitoring is not setup yet. Reopening this in the meantime.

@victorb victorb reopened this Jan 24, 2018
@victorb
Copy link
Collaborator Author

victorb commented Jan 25, 2018

Yay, jenkins monitoring dashboard is back online!

image

@victorb victorb closed this as completed Jan 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant