-
Notifications
You must be signed in to change notification settings - Fork 6
Setting up monitoring/alerts #2
Comments
Remember what this means?
Can view the monitoring dashboard? Or: can run the dashboard locally, in an automated way? |
@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? |
Yeah let that running-locally be separate: ipfs/infra#52 |
Ok, in that case, this task would depend on us running jenkins deployed somewhere before you can start working on this task. Correct? |
Nah I can get started with the local jenkins |
#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 |
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. |
Splitting off tuning and alerting to #31. |
Moved infrastructure for jenkins and monitoring is not setup yet. Reopening this in the meantime. |
Acceptance Criteria
Tasks
Dependencies
Depends on #1
The text was updated successfully, but these errors were encountered: