Run Prometheus via Docker:docker run -d –name prometheus \\<\/p>\n\n\n\n
-p 9090:9090 \\<\/p>\n\n\n\n
-v $(pwd)\/prometheus.yml:\/etc\/prometheus\/prometheus.yml \\<\/p>\n\n\n\n
prom\/prometheus<\/p>\n\n\n\n
4. Visit http:\/\/localhost:9090 in your browser. You should see the Prometheus UI.
\u26a0\ufe0f Warning:<\/strong> If port 9090 is already in use on your machine, change the -p flag (e.g., -p 9091:9090) and adjust accordingly throughout this guide.<\/p>\n\n\n\nOption 2: Manual Binary Install<\/strong><\/h3>\n\n\n\nDownload the latest release from the official Prometheus downloads page, extract it, and run:<\/p>\n\n\n\n
.\/prometheus –config.file=prometheus.yml<\/p>\n\n\n\n
This route gives you more control but requires you to manually manage the binary during upgrades.<\/p>\n\n\n\n
Installing Grafana: Step-by-Step Process<\/strong><\/h2>\n\n\n\nDocker Install<\/strong><\/h3>\n\n\n\ndocker run -d –name grafana -p 3000:3000 grafana\/grafana<\/p>\n\n\n\n
Visit http:\/\/localhost:3000. Default login credentials are admin \/ admin \u2014 you’ll be prompted to change the password on first login.<\/p>\n\n\n\n
\u26a0\ufe0f Warning:<\/strong> Never leave default credentials active on a production or internet-facing Grafana instance. This is one of the most common security misconfigurations we see in real deployments.<\/p>\n\n\n\nManual Install (Linux example)<\/strong><\/h3>\n\n\n\nsudo apt-get install -y software-properties-common<\/p>\n\n\n\n
sudo add-apt-repository “deb https:\/\/packages.grafana.com\/oss\/deb stable main”<\/p>\n\n\n\n
sudo apt-get update<\/p>\n\n\n\n
sudo apt-get install grafana<\/p>\n\n\n\n
sudo systemctl start grafana-server<\/p>\n\n\n\n
Connecting Grafana to Prometheus<\/strong><\/h2>\n\n\n\nTo connect Grafana to Prometheus, log into Grafana, go to Connections \u2192 Data Sources \u2192 Add data source, select Prometheus, and enter your Prometheus server URL (typically http:\/\/localhost:9090 for local Docker setups, or http:\/\/prometheus:9090 if both containers share a Docker network). Click “Save & Test” to confirm the connection.<\/p>\n\n\n\n
Steps:<\/strong><\/p>\n\n\n\n\nOpen Grafana at http:\/\/localhost:3000<\/li>\n\n\n\n Navigate to Connections \u2192 Data Sources<\/strong><\/li>\n\n\n\nClick Add data source<\/strong>, select Prometheus<\/strong><\/li>\n\n\n\nEnter the URL: http:\/\/localhost:9090 (or your container’s internal hostname)<\/li>\n\n\n\n Click Save & Test<\/strong><\/li>\n<\/ol>\n\n\n\nIf successful, you’ll see a green confirmation message. If not, see the troubleshooting section below.<\/p>\n\n\n\n
\ud83d\udca1 Pro Tip:<\/strong> If you’re running both containers via docker-compose, use the service name (e.g., http:\/\/prometheus:9090) instead of localhost \u2014 this is the single most common connection error beginners hit.<\/p>\n\n\n\nBuilding Your First Dashboard <\/strong><\/h2>\n\n\n\n\nIn Grafana, go to Dashboards \u2192 New \u2192 New Dashboard<\/strong><\/li>\n\n\n\nClick Add visualization<\/strong><\/li>\n\n\n\nSelect your Prometheus data source<\/li>\n\n\n\n In the query field, enter a PromQL query like:<\/li>\n<\/ol>\n\n\n\nrate(prometheus_http_requests_total[5m])<\/p>\n\n\n\n
\nChoose a visualization type (time series, gauge, bar chart, etc.)<\/li>\n\n\n\n Click Apply<\/strong>, then Save dashboard<\/strong><\/li>\n<\/ol>\n\n\n\nSetting Up Basic Alerts<\/strong><\/h2>\n\n\n\nGrafana’s alerting engine lets you define conditions (e.g., “CPU usage > 85% for 5 minutes”) and trigger notifications via email, Slack, or webhook.<\/p>\n\n\n\n
\nGo to Alerting \u2192 Alert rules \u2192 New alert rule<\/strong><\/li>\n\n\n\nDefine your query and condition threshold<\/li>\n\n\n\n Set evaluation interval (e.g., every 1 minute)<\/li>\n\n\n\n Configure a contact point (Slack, email, PagerDuty, etc.)<\/li>\n\n\n\n Save and test the alert<\/li>\n<\/ol>\n\n\n\n\u2705 Best Practice:<\/strong> Start with conservative thresholds and tighten them over time. Overly sensitive alerts lead to “alert fatigue,” where teams start ignoring notifications altogether \u2014 a well-documented failure mode in SRE practice.<\/p>\n\n\n\nCommon Setup Errors and Fixes<\/strong><\/h2>\n\n\n\nError<\/strong><\/td>Likely Cause<\/strong><\/td>Fix<\/strong><\/td><\/tr>“No data” in Grafana panel<\/td> Wrong data source URL or scrape target down<\/td> Verify the Prometheus URL and check the\/targets page in the Prometheus UI<\/td><\/tr> Prometheus shows the target as “DOWN”<\/td> Wrong port or app not exposing \/metrics<\/td> Confirm the app has a metrics endpoint and the port is correct<\/td><\/tr> Grafana login loop<\/td> Browser cookie\/session issue<\/td> Clear cookies or use incognito mode<\/td><\/tr> Docker containers can’t reach each other<\/td> Containers not on the same network<\/td> Use docker-compose or docker network create to link them<\/td><\/tr> PromQL query returns empty<\/td> Metric name typo or no data yet<\/td> Use Prometheus’s built-in autocomplete in the query bar<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nPrometheus vs. Other Monitoring Tools <\/strong><\/h2>\n\n\n\nTool<\/strong><\/td>Best For<\/strong><\/td>Metrics Storage<\/strong><\/td>Learning Curve<\/strong><\/td>Pricing<\/strong><\/td><\/tr>Prometheus + Grafana<\/td> Cloud-native, Kubernetes, self-hosted<\/td> Built-in (Prometheus)<\/td> Moderate<\/td> Free, open-source<\/td><\/tr> Datadog<\/td> Enterprise, all-in-one observability<\/td> Managed\/cloud<\/td> Low<\/td> Paid, usage-based<\/td><\/tr> New Relic<\/td> APM-heavy environments<\/td> Managed\/cloud<\/td> Low\u2013Moderate<\/td> Paid, usage-based<\/td><\/tr> Zabbix<\/td> Traditional IT\/network monitoring<\/td> Built-in<\/td> Moderate\u2013High<\/td> Free, open-source<\/td><\/tr> Nagios<\/td> Legacy infrastructure monitoring<\/td> Built-in<\/td> High<\/td> Free\/paid tiers<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nKey Takeaways <\/strong><\/h2>\n\n\n\n\nPrometheus collects and stores metrics; Grafana visualizes them \u2014 they serve different jobs in the same stack.<\/li>\n\n\n\n Docker is the fastest, most reliable way to get both tools running for testing or learning.<\/li>\n\n\n\n Most connection errors trace back to networking (wrong hostname\/port), not the tools themselves.<\/li>\n\n\n\n Default Grafana credentials must be changed immediately, especially outside local testing.<\/li>\n\n\n\n This stack is free and open-source, but it requires more hands-on configuration than managed alternatives like Datadog.<\/li>\n<\/ul>\n\n\n\nFAQs <\/strong><\/h2>\n\n\n\n
\n
\n
1. What is the difference between Prometheus and Grafana?<\/strong><\/h3>\n\n\n
Prometheus collects, stores, and queries metrics data. Grafana visualizes that data in dashboards. Prometheus is the data layer; Grafana is the presentation layer.<\/p>\n\n<\/div>\n<\/div>\n
\n
2. Can Grafana work without Prometheus?<\/strong><\/h3>\n\n\n
Yes. Grafana supports over 100 data sources, including MySQL, Elasticsearch, and InfluxDB, so it doesn’t require Prometheus specifically.<\/p>\n\n<\/div>\n<\/div>\n
\n
3. Is Prometheus free to use?<\/strong><\/h3>\n\n\n
Yes, Prometheus is fully open-source under the Apache 2.0 license, with no licensing cost for self-hosted use.<\/p>\n\n<\/div>\n<\/div>\n
\n
4. How long does it take to set up Prometheus and Grafana?<\/strong><\/h3>\n\n\n
A basic local setup using Docker typically takes 15\u201330 minutes, including installation, configuration, and connecting the two tools.<\/p>\n\n<\/div>\n<\/div>\n
\n
5. Why does my Grafana dashboard show “No data”?<\/strong><\/h3>\n\n\n
This usually means Grafana can’t reach Prometheus, or Prometheus isn’t successfully scraping the target. Check the data source URL and the Prometheus \/targets page first.<\/p>\n\n<\/div>\n<\/div>\n
\n
6. Do I need Kubernetes to use Prometheus and Grafana?<\/strong><\/h3>\n\n\n
No. While they’re extremely popular in Kubernetes environments, both tools run fine on standalone servers, VMs, or local machines.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"
If you’ve ever stared at a server outage wondering what happened three hours before it crashed, you already understand why monitoring matters. Roughly 60% of production incidents could be caught earlier with proper observability tooling. Yet a surprising number of teams still run servers blind, with no visibility into CPU, memory, or request latency until […]<\/p>\n","protected":false},"author":64,"featured_media":120472,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[621],"tags":[],"views":"108","authorinfo":{"name":"Abhishek Pati","url":"https:\/\/www.guvi.in\/blog\/author\/abhishek-pati\/"},"thumbnailURL":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/Prometheus-and-Grafana-300x116.webp","_links":{"self":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/120121"}],"collection":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/users\/64"}],"replies":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/comments?post=120121"}],"version-history":[{"count":4,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/120121\/revisions"}],"predecessor-version":[{"id":120476,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/120121\/revisions\/120476"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media\/120472"}],"wp:attachment":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media?parent=120121"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/categories?post=120121"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/tags?post=120121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}