If you run a self-hosted Prometheus instance, NOFire AI can connect through an AWS VPC PrivateLink. This keeps all traffic within your network boundary and follows AWS security best practices.
Prerequisites
- A Prometheus instance that NOFire AI can reach.
- The query endpoint URL of that instance.
- The name of the cluster this connection covers.
- The instance must expose metrics for the services you want mapped. Without them, NOFire AI can read the instance but cannot map how your services depend on each other.
Step 1: Setup Prometheus instance integration
Grafana Cloud (skip for on-prem)
- Sign-in to portal https://grafana.com/auth/sign-in
-
Select your Grafana stack, for example nofire.\
-
Select Prometheus details.\
-
Copy the Query Endpoint to your clipboard and keep it in a note.\
-
Copy the User to your clipboard and keep it in a note.
-
Create a Cloud Access Policy for your stack. Use the
metrics:readscope only.
-
Add a token to this newly created access policy.\
-
Set a name and an expiration date, then generate the token.
Step 2: Add Prometheus connection to NOFire AI
-
In the NOFire AI dashboard, go to Connections and click Connect on Prometheus.
-
Enter credentials:
- Name (for example, production)
- Cluster Name (for example,
production-k8s) - URL (for example,
https://prometheus.grafana.net/api/prom) - Username: the Grafana Cloud access policy user from Step 1. Grafana Cloud requires this field. A self-hosted Prometheus without authentication can leave it blank.
- Password: the Grafana Cloud access policy token from Step 1. Grafana Cloud requires this field. A self-hosted Prometheus without authentication can leave it blank.
Test the connection
- Open the Connections dashboard and make sure that the Prometheus connection status is READY. A connection that stays in an error state did not authenticate.
- Ask NOFire a question that needs metrics, for example “what is the error rate for the checkout service right now?”. An answer that cites your metrics confirms the connection works end to end.
Troubleshooting
The connection saves but returns no data
The connection saves but returns no data
The URL points at a different instance, or the instance requires authentication that the connection does not supply. Open the URL yourself and compare.
NOFire cannot map service relationships
NOFire cannot map service relationships
The instance exposes no metrics for those services. Check your scrape configuration covers them.