Choose the best description of what Prometheus does when integrated with a Spring Boot app.
Think about which tool is responsible for gathering data versus showing it.
Prometheus is designed to collect and store metrics data. Grafana is used for visualization.
Given this Prometheus scrape configuration snippet, what is the target URL Prometheus will scrape?
scrape_configs: - job_name: 'springboot-app' static_configs: - targets: ['localhost:8080']
Prometheus defaults to scraping the /metrics path unless overridden.
Since no metrics_path is specified in the scrape config, Prometheus defaults to /metrics and scrapes http://localhost:8080/metrics.
Select the correct property to enable Prometheus metrics endpoint in application.properties.
Look for the property that exposes endpoints over web.
To expose the Prometheus endpoint, you must include it in the management endpoints web exposure list.
Arrange these steps in the right order to set up monitoring with Prometheus and Grafana for a Spring Boot app.
Think about enabling metrics first, then scraping, then visualization.
You first expose metrics in Spring Boot, then configure Prometheus to scrape them, then connect Grafana to Prometheus, and finally build dashboards.
Prometheus scrapes Spring Boot metrics without errors, but Grafana dashboards show 'No data'. What is the most likely cause?
Check the connection between Grafana and Prometheus.
If Prometheus scrapes metrics correctly but Grafana shows no data, the Grafana data source is likely misconfigured or pointing to the wrong Prometheus URL.