Lab catalog
found 6 of 846 of 84loading…
Loading…
-
A machine dropped out of monitoring Since last night Prometheus has had no data on this server's CPU, memory and disks, although Prometheus itself is running. Bring the machine back into monitoring so that it stays there.~20 min not started
-
The app's metrics are not in Prometheus The web team needs the shop app's metrics in Prometheus with the label team="web". Yesterday a colleague added a job and said it was done — yet there is no data. Finish the job without exposing the metrics to the outside.~20 min not started
-
The full-volume alert stays silent The volume with exports on the reports server has run out twice at night, and nobody found out. A colleague added an alert rule for an almost full volume to Prometheus, yet yesterday the volume filled up again with no alert. Make the alert fire in time and clear when the space is freed.~30 min not started
-
Alerts do not reach the receiver Two instances of the online shop were down for twenty minutes last night. Prometheus saw it and the alert fired, yet the team in charge of the shop received not a single notification. Find where the alerts get lost and make the team learn about the instances that went down in one message.~30 min not started
-
The second machine's logs are not on the collector The team collects the logs of all machines on node1, each machine in its own directory. node2 was set up to forward its journal there, yet the collector has not a single line from it. Get the forwarding working end to end so that it survives a reboot of both machines.~30 min not started
-
The site returns 500 From some moment on the hotel booking site answers its guests with error 500, and the nginx error.log is empty. Work out from the logs when the outage began and what caused it, write that down and bring the site back.~25 min not started
No lab on the topic you need? Suggest a lab