Skip to content

Integrate Lightrun metric data into New Relic using Prometheus remote_write

In this guide, you will learn how to ingest Lightrun metrics data into New Relic from a Prometheus time series database with the Prometheus remote_write capabilities.

New Relic is a cloud-based all-in-one observability platform that monitors performance and availability. By storing Lightrun metrics with Prometheus and ingesting the stored data into New Relic with Prometheus remote_write, you can analyze real-time metrics (counter, tic toc, custom metrics) collected from your live code using Lightrun with New Relic's advanced monitoring capabilities.


This tutorial assumes that you have:

  1. A Lightrun account.
  2. A New Relic account. Register for a free New Relic account here.
  3. Prometheus installed and running. Refer to the Prometheus FAQ as well for additional help.
  4. Basic understanding of Prometheus concepts and terminologies.

Configure the Lightrun Prometheus integration

The first step in the tutorial will be to activate the Lightrun Prometheus integration.

To do that:

  1. Open a browser and log in to your Lightrun account.

  2. In the menu on the left, click Integrations.

    The page loads with all available integrations:

    Integrations Page -third

  3. From the Integrations page, click Connect from the Prometheus card.

    The Prometheus Integration window pops up:

    Prometheus Configuration -third

  4. From the Round Up dropdown list, select the rounding rule to be applied by Prometheus for your Lightrun data.

  5. Click Copy from under the scrape configuration.
  6. Paste the scrape_configs data to the existing scrape_configs section in your Prometheus YAML configuration file. Paste script -third

  7. Start your Prometheus server.

  8. Click Connect and wait for the approval toast message.

Configure New Relic and Prometheus

After configuring the Lightrun Prometheus integration, the next step is to configure our Prometheus server to send the collected metrics data to New Relic using the Prometheus remote_write capabilities.

To configure Prometheus New Relic remote_write connection,

  1. Log in to your New Relic account.
  2. Click Add Data in the New Relic sidebar.
  3. Search for Prometheus and select the Prometheus Remote Write Integration.

    Prometheus Configuration

  4. Enter a name to identify the data source and click Generate URL to generate the Prometheus remote_write configuration.

  5. Add the configuration to your prometheus.yml file.
  6. Restart your Prometheus server.


After adding the New Relic configuration to your prometheus.yml file, your prometheus.yml file should appear similar to the following.

# my global config
    scrape_interval: 15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
    evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
    # scrape_timeout is set to the global default (10s).

    # Alertmanager configuration
        - static_configs:
        - targets:
            # - alertmanager:9093

    # Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
    # - "first_rules.yml"
    # - "second_rules.yml"

    # A scrape configuration containing exactly one endpoint to scrape:
    # Here it's Prometheus itself.
        # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
        - job_name: "prometheus"

            # metrics_path defaults to '/metrics'
            # scheme defaults to 'http'.

            - targets: ["localhost:9090"]
        - job_name: "lightrun"
            scrape_interval: 5s
            scheme: https
            metrics_path: /athena/company/<lightrun_company_id>/integrations/prometheus/metrics
            - targets: []
        insecure_skip_verify: false
    - url:

Confirm your integration

To confirm your integration, insert a Lightrun metric into your application and select Prometheus as your target. The metrics data will appear in your metrics dashboard.

Query the collected data to gain more insights on your Lightrun metrics.

Query New Relic


  • If the connection state is down, confirm that:

    1. Your firewall rules are not blocking Prometheus queries to the Lightrun server.
    2. There are no communication issues with your Prometheus server.
  • If the connection state is down and there is a server returned HTTP status 403 forbidden error message. This error indicates that Prometheus integration is not currently enabled in your Management Portal.

    Prometheus Fail

Last update: June 6, 2024