[01:15:10] FIRING: SystemdUnitFailed: arclamp_generate_svgs.service on arclamp1001:9100 - https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state - https://grafana.wikimedia.org/d/g-AaZRFWk/systemd-status - https://alerts.wikimedia.org/?q=alertname%3DSystemdUnitFailed [01:20:10] RESOLVED: SystemdUnitFailed: arclamp_generate_svgs.service on arclamp1001:9100 - https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state - https://grafana.wikimedia.org/d/g-AaZRFWk/systemd-status - https://alerts.wikimedia.org/?q=alertname%3DSystemdUnitFailed [09:44:34] tappof: I have a new one for you: https://gerrit.wikimedia.org/r/c/operations/puppet/+/1369626 DPE is okay and already gave their blessings [10:48:00] I spoke too soon [11:31:25] Following up on the conversation we had with tappof at the SRE Summit: as part of the migration from PyBal to Liberica, I’m rethinking our metrics and their cardinality. Currently count({__name__="pybal_monitor_status"}) returns ~49k series. [11:31:25] My main constraint is that I need to alert when an individual realserver is misbehaving, which seems to require exposing metrics per realserver. That’s a lot of series: lvs1020 alone has around 12k realservers configured. [11:31:25] Is it possible to alert on a per-realserver basis without exposing per-realserver metrics? [11:48:46] vgutierrez: Have you already mapped {__name__="pybal_monitor_status"} to a Liberica-related metric for the DCs that have already been migrated? This is just to take a look at a couple of them and get a better understanding of what they'll eventually look like. [11:50:09] right now that would be `liberica_healthcheck_result` [11:50:17] ack [12:27:37] hello! would love your thoughts on T445205 [12:27:37] T445205: Dynamically generate Icinga host groups - https://phabricator.wikimedia.org/T445205 [16:49:40] FIRING: LogstashKafkaConsumerLag: Too many messages in logging-eqiad for group logstash7-codfw - https://wikitech.wikimedia.org/wiki/Logstash#Kafka_consumer_lag - https://grafana.wikimedia.org/d/000000484/kafka-consumer-lag?var-cluster=logging-eqiad&var-datasource=codfw%20prometheus/ops - https://alerts.wikimedia.org/?q=alertname%3DLogstashKafkaConsumerLag [16:54:40] FIRING: [2x] LogstashKafkaConsumerLag: Too many messages in logging-eqiad for group logstash7-codfw - https://wikitech.wikimedia.org/wiki/Logstash#Kafka_consumer_lag - https://alerts.wikimedia.org/?q=alertname%3DLogstashKafkaConsumerLag [17:04:40] RESOLVED: [2x] LogstashKafkaConsumerLag: Too many messages in logging-eqiad for group logstash7-codfw - https://wikitech.wikimedia.org/wiki/Logstash#Kafka_consumer_lag - https://alerts.wikimedia.org/?q=alertname%3DLogstashKafkaConsumerLag [17:34:40] FIRING: LogstashKafkaConsumerLag: Too many messages in logging-eqiad for group logstash7-codfw - https://wikitech.wikimedia.org/wiki/Logstash#Kafka_consumer_lag - https://grafana.wikimedia.org/d/000000484/kafka-consumer-lag?var-cluster=logging-eqiad&var-datasource=codfw%20prometheus/ops - https://alerts.wikimedia.org/?q=alertname%3DLogstashKafkaConsumerLag [17:39:40] FIRING: [2x] LogstashKafkaConsumerLag: Too many messages in logging-eqiad for group logstash7-codfw - https://wikitech.wikimedia.org/wiki/Logstash#Kafka_consumer_lag - https://alerts.wikimedia.org/?q=alertname%3DLogstashKafkaConsumerLag [20:23:53] FIRING: ProbeDown: Service webperf1003:443 has failed probes (http_performance_wikimedia_org_ip4) - https://wikitech.wikimedia.org/wiki/Runbook#webperf1003:443 - https://grafana.wikimedia.org/d/O0nHhdhnz/network-probes-overview?var-job=probes/custom&var-module=All - https://alerts.wikimedia.org/?q=alertname%3DProbeDown [20:28:53] RESOLVED: ProbeDown: Service webperf1003:443 has failed probes (http_performance_wikimedia_org_ip4) - https://wikitech.wikimedia.org/wiki/Runbook#webperf1003:443 - https://grafana.wikimedia.org/d/O0nHhdhnz/network-probes-overview?var-job=probes/custom&var-module=All - https://alerts.wikimedia.org/?q=alertname%3DProbeDown [21:39:40] FIRING: [2x] LogstashKafkaConsumerLag: Too many messages in logging-eqiad for group logstash7-codfw - https://wikitech.wikimedia.org/wiki/Logstash#Kafka_consumer_lag - https://alerts.wikimedia.org/?q=alertname%3DLogstashKafkaConsumerLag [22:07:53] FIRING: ProbeDown: Service webperf1003:443 has failed probes (http_performance_wikimedia_org_ip4) - https://wikitech.wikimedia.org/wiki/Runbook#webperf1003:443 - https://grafana.wikimedia.org/d/O0nHhdhnz/network-probes-overview?var-job=probes/custom&var-module=All - https://alerts.wikimedia.org/?q=alertname%3DProbeDown [22:12:53] RESOLVED: ProbeDown: Service webperf1003:443 has failed probes (http_performance_wikimedia_org_ip4) - https://wikitech.wikimedia.org/wiki/Runbook#webperf1003:443 - https://grafana.wikimedia.org/d/O0nHhdhnz/network-probes-overview?var-job=probes/custom&var-module=All - https://alerts.wikimedia.org/?q=alertname%3DProbeDown [23:34:48] FIRING: PuppetFailure: Puppet has failed on logging-hd2005:9100 - https://puppetboard.wikimedia.org/nodes?status=failed - https://grafana.wikimedia.org/d/yOxVDGvWk/puppet - https://alerts.wikimedia.org/?q=alertname%3DPuppetFailure