SadServers - Linux & DevOps Troubleshooting Interviews

Troubleshooting Scenarios

apache bash c caddy csv data processing disk volumes dns docker envoy etcd git golang gunicorn hack haproxy harbor hashicorp vault helm java jenkins json kubernetes linux-other mysql nginx php postgres prometheus python rabbitmq redis sql sqlite ssh ssl supervisord

realistic / interviews new pro

Prometheus

Prometheus Scenarios

#	Name	Level	Time	Type
1	"Warsaw": Prometheus can't scrape the webserver	Medium	30 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: 30 minutes.

Troubleshooting Scenarios

Prometheus

Prometheus Scenarios

"Warsaw": Prometheus can't scrape the webserver

Send Us Feedback or Get Notified