You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
This page is currently a draft.
More information and discussion about changes to this draft on the talk page.
There are 2 physical servers:
- labmon1001.eqiad.wmnet --- currently master
- labmon1002.eqiad.wmnet --- currently cold standby
Both servers get applied the puppet role labs::monitoring (modules/role/manifests/labs/monitoring.pp), which get them ready to collect metrics using a software stack composed of carbon, graphite and friends.
Although the ideal would be for both servers to collect and serve metrics at the same time using a cluster approach, right now only the master actually works. The cold standby fetch metrics using rsync from the master (/srv/carbon/whisper/), so in case of a failover we could rebuild the service without much metrics loss.
These bits are located at modules/profile/manifests/labs/monitoring.pp.
There is a cron job with a custom script (archive-instances) that rotates (archives) old metrics from CloudVPS projects. Then, archived metrics get deleted if they are older than 90 days by means of a cronjob.
Both the /srv/ partition and the archive directory /srv/carbon/whisper/archived_metrics/ could grow out of control if these mechanisms are not properly adjusted.
These bits are located at:
The script logs operations to /var/log/graphite/instance-archiver.log.
Monitoring for Cloud VPS
There are metrics per project.
Monitoring for Toolforge
There are metrics for every node in the Toolforge cluster.
If you want to get an overview of what's going on the Cloud VPS infra, open these links:
|eqiad||NFS servers||icinga||labstore1xxx servers|||
|eqiad||Cloud VPS main services||icinga||service servers, non virts|||
|codfw||Cloud VPS labtest servers||icinga||all physical servers|||
|eqiad||Toolforge basic alerts||grafana||some interesting metrics from Toolforge|||
|eqiad||Toolforge grid status||custom tool||jobs running on Toolforge's grid|||
|any||cloud servers||icinga||all physical servers with the cloudXXXX naming scheme|||