Showcase Your Prometheus Skills with a GitHub README Badge

Use this markdown in your README:

![Prometheus](https://img.shields.io/badge/Prometheus-E6522C?style=for-the-badge&logo=prometheus&logoColor=white)

The #E6522C is Prometheus's official orange from their brand guidelines. The prometheus logo identifier renders Prometheus's logo from Simple Icons. This orange badge pairs naturally with Grafana (the companion visualization layer) and Kubernetes in an observability-focused profile.

Prometheus expertise spans metrics collection, querying, and alerting:

• Metrics instrumentation: Adding Prometheus client libraries to applications (Python, Go, Java, Node.js)
• PromQL: Writing efficient metric queries, range queries, and aggregation functions
• Exporters: Node Exporter, cAdvisor, Blackbox Exporter, custom exporters
• Alerting: Alertmanager configuration, alert rules with for duration, notification routing to PagerDuty/Slack
• Service discovery: Kubernetes service discovery, file-based discovery
• Federation: Hierarchical Prometheus deployments for multi-cluster environments
• Recording rules: Pre-computing expensive queries for dashboard performance

Writing PromQL beyond basic queries — using rate(), histogram_quantile(), or complex label matching — signals genuine observability engineering rather than basic dashboard viewing.

Prometheus is the center of the cloud-native observability stack:

• LGTM stack: Prometheus + Grafana + Loki + Tempo (metrics, logs, traces)
• Kubernetes observability: Prometheus + Grafana + Alertmanager + kube-state-metrics
• Full monitoring stack: Prometheus + Grafana + Elasticsearch + Jaeger
• SRE toolbox: Prometheus + Grafana + PagerDuty + Runbooks

Prometheus and Grafana are so commonly paired that listing one usually implies the other. If you maintain complete observability pipelines — metrics (Prometheus), logs (Loki or Elasticsearch), and traces (Jaeger or Tempo) — mention all three observability signals since the combination demonstrates production-grade monitoring maturity.

Prometheus configuration is YAML and PromQL rules — not counted in GitHub language statistics. Instrumentation code that adds Prometheus metrics to applications is in your primary language (Python, Go, etc.). The presence of prometheus.yml, alert rules files, and recording rules in your repositories signals infrastructure observability work.

For pinned repositories, a complete monitoring stack in Docker Compose — Prometheus scraping real application metrics, Grafana with pre-built dashboards, and Alertmanager configured with routing rules — is an outstanding DevOps portfolio piece. Include screenshots of Grafana dashboards in the README to make the observability capabilities immediately visible without requiring the viewer to run the stack.