Prometheus Troubleshooting Scenarios

Packages advent2025 ai ansible apache aws cli bash c caddy clickhouse cron csv data processing disk volumes dns docker elk envoy etcd financial finops ftp git gitea golang gunicorn hack haproxy harbor hashicorp vault helm java jenkins json kubernetes linux-other mongodb mysql nginx node.js php podman postgres prometheus python rabbitmq redis sql sqlite ssh ssl supervisord systemd terraform traefik

realistic / interviews new pro business

Prometheus

Prometheus Scenarios

#	Name	Level	Time	Type
1	"Warsaw": Prometheus can't scrape the webserver	Medium	60 m	Fix Pro	"Warsaw": Prometheus can't scrape the webserver Scenario: "Warsaw": Prometheus can't scrape the webserver Level: Medium Type: Fix Access: Paid Description: A developer created a golang application that is exposing the /metrics endpoint. They have a problem with scraping the metrics from the application. They asked you to help find the problem. Full source code of the application is available at the /home/admin/app directory. Credit Kamil Błaż Test: The endpoint http://localhost:9000/metrics should return HTTP code 200. The "Check My Solution" button runs the script /home/admin/agent/check.sh, which you can see and execute. Time to Solve: 60 minutes.

Prometheus Troubleshooting Scenarios

Prometheus

Prometheus Scenarios

"Warsaw": Prometheus can't scrape the webserver

Send Us Feedback or Get Notified