You are browsing a read-only backup copy of Wikitech. The primary 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:
- cloudmetrics1002.eqiad.wmnet --- currently master
- cloudmetrics1001.eqiad.wmnet --- currently cold standby
Both servers get applied the puppet role role::wmcs::monitoring (modules/role/manifests/wmcs/monitoring.pp), which get them ready to collect metrics using a software stack composed of carbon, graphite, Prometheus 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/wmcs/monitoring.pp.
The DNS records grafana-labs.discovery.wmnet and graphite-labs.discovery.wmnet define the active web server servicing requests. This entry is managed in the DNS git repo at /dns/browse/master/templates/wmnet and configured on trafficserver in hieradata/common/profile/trafficserver/backend.yaml.
Accessing "labs" prometheus
Our monitoring for physical servers is a mix of production Prometheus/Thanos and the Prometheus setup on the cloudmetrics100x servers. These are mentioned in https://grafana.wikimedia.org as "eqiad prometheus/labs". To access the servers directly in order to troubleshoot what the scrapes are coming up with and more quickly construct queries, you can set up an ssh proxy like so:
ssh -L 8000:prometheus-labmon.eqiad.wmnet:80 cloudmetrics1001.eqiad.wmnet
And then point your web browser to http://localhost:8000/labs to bring up the Prometheus web interface. You can then construct and execute PromQL queries as needed per the upstream docs. Note, that sometimes a copied grafana query will not work because it has a grafana variable in it. Just watch out for things with a "$name" format, since that's not PromQL.
Our metrics retention policy is 90 days. There are two cronjobs for the
_graphite user that are running on
labmon1001 for this task:
archive-deleted-instances: Moves data from deleted instances to
delete-old-instance-archives: Deletes archived data that is older than 90 days
This prevents the
/srv partition from becoming full.
archive-instances script logs operations to
Monitoring for Cloud VPS
The Cloud VPS project "metricsinfra" provides the base infrastructure and services for multi-tenant instance monitoring on Cloud VPS.
Adding new projects
The monitoring configuration is mostly kept in a Trove database. There is no interface for more user-friendly management yet, but for now you can ssh to
metricsinfra-controller-1.metricsinfra.eqiad1.wikimedia.cloud and use
sudo -i mariadb to edit the database by hand.
Some hardcoded accounts (WMCS staff and some trusted volunteers) can use prometheus-alerts.wmcloud.org to create and edit silences. In the future the same interface will work for all project administrators for their own projects.
- Prometheus dashboard: https://prometheus.wmflabs.org/cloud
- Prometheus active alerts: https://prometheus.wmflabs.org/cloud/alerts
- Grafana alert overview: https://grafana-labs.wikimedia.org/d/woLx6H6Wz/metricsinfra-alerts
- Grafana project overview: https://grafana-labs.wikimedia.org/d/8Npp-46Zz/project-overview
- Grafana instance details: https://grafana-labs.wikimedia.org/d/000000590/instance-details
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||NFS Server Statistics||grafana||labstore and cloudstore NFS operations, connections and various details|||
|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||ToolsDB (Toolforge R/W MariaDB)||grafana||Database metrics for ToolsDB servers|||
|eqiad||Toolforge grid status||custom tool||jobs running on Toolforge's grid|||
|any||cloud servers||icinga||all physical servers with the cloudXXXX naming scheme|||
|eqiad||Cloud VPS eqiad1 capacity||grafana||capacity planning|||
|eqiad||labstore1004/labstore1005||grafana||load & general metrics|||
|eqiad||Cloud VPS eqiad1||grafana||load & general metrics|||
|eqiad||Cloud VPS eqiad1||grafana||internal openstack metrics|||
|eqiad||Cloud VPS eqiad1||grafana||hypervisor metrics from openstack|||
|eqiad||Cloud VPS memcache||grafana||cloudservices servers|||
|eqiad||openstack database backend (per host)||grafana||mariadb/galera on cloudcontrols|||
|eqiad||openstack database backend (aggregated)||grafana||mariadb/galera on cloudcontrols|||
|eqiad||Cloud HW eqiad||icinga||Icinga group for WMCS in eqiad|||
|eqiad||Toolforge, new kubernetes cluster||prometheus/grafana||Generic dashboard for the new Kubernetes cluster|||
|eqiad||Toolforge, new kubernetes cluster, namespaces||prometheus/grafana||Per-namspace dashboard for the new Kubernetes cluster|||
|eqiad||Toolforge, new kubernetes cluster, ingress||prometheus/grafana||dashboard about the ingress for the new kubernetes cluster|||
|eqiad||Toolforge||prometheus/grafana||dashboard showing a table with basic information about all VMs in the tools project|||
|eqiad||Toolforge email server||prometheus/grafana||dashboard showing data about Toolforge exim email server|||