Run Prometheus locally and validate your metrics with the Autometrics CLI and Explorer 📈
Autometrics Logo
GitHubGitHub (opens in a new tab)DiscordDiscord (opens in a new tab)
  • Introduction
  • Why Autometrics?
  • Features
  • Local Development
    • CLI Reference
  • CI/CD
  • Service Level Objectives
  • Languages & Frameworks
    • Quickstart
    • Adding version information
    • Adding alerts and SLOs
    • API Reference ↗ (opens in a new tab)
    • Frameworks
    • Setting up SLOs with Axum
    • Quickstart
    • API Reference ↗ (opens in a new tab)
    • Using wrappers and decorators
    • Adding version information
    • Adding alerts and SLOs
    • Configuration
    • Frameworks
    • Setting up SLOs in Express
    • Setting up SLOs in Fastify
    • Quickstart
    • Adding version information
    • Adding alerts and SLOs
    • API Reference ↗
    • Quickstart
    • Adding version information
    • Adding alerts and SLOs
    • API Reference ↗ (opens in a new tab)
    • Frameworks
    • Setting up SLOs with FastAPI
  • C# (community) ↗ (opens in a new tab)
  • Deployment
  • Autometrics Stack
  • Prometheus
    • Docker
    • Kubernetes
    • Northflank
    • Railway
  • Explorer
    • Docker
    • Kubernetes
    • Northflank
    • Railway
    • Docker
    • Kubernetes
  • OTel Collector
    • Northflank
    • Railway

  • Get Involved
Question? Give us feedback → (opens in a new tab)Edit this page
Prometheus
Configuring Prometheus on Fly.io

Configuring Prometheus on Fly.io

Fly.io (opens in a new tab) provides a hosted Prometheus instance for every project.

To have Fly's Prometheus scrape your Autometrics-instrumented app, simply add this to your fly.toml configuration (opens in a new tab):

fly.toml
app = "your-app-name"
 
[metrics]
port = 9091 # default for most prometheus clients
path = "/metrics" # default for most prometheus clients
RailwayDocker

MIT/Apache-2.0 2025 © Autometrics