Create a Prometheus connection

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Establish a zero copy connection to a Prometheus system in Zero Copy Connector Hub.

    Before you begin

    Role required: df_connection_admin

    About this task

    Work with your data source admin to create a connection to Prometheus. For additional information about connecting, refer to the Prometheus connector documentation.

    Note:
    This connector was developed by the open-source community and made available through the ServiceNow AI Platform for general use. Functionality can vary and might not cover all use cases supported by primary connectors.

    Procedure

    1. Navigate to the available community connectors in Zero Copy Connector Hub in one of the following ways:
      • Navigate to All > Zero Copy Connector Hub > Available connectors > Community connectors.
      • Navigate to Admin > Zero Copy Connector Hub > Available connectors > Community connectors.
    2. Find the Prometheus connector and select Connect.
    3. On the form, fill in the fields.
      Table 1. New Prometheus Connection form
      Field Description
      Name and description
      Connection label Unique name for this connection. This helps in identifying the connection within your system.
      Connection name System-generated name based on the Connection label. This field cannot be modified once the connection is established.
      Short description Description of the connection explaining what it is about.
      Connection attributes
      Connection URL Endpoint for the Prometheus coordinator host. For example:

      https://<host>/<path>

      Authentication methods
      Authentication method Authentication method to use with Prometheus. Default is Basic Authentication.
      Username Username for basic authentication. This field appears only when Basic Authentication is selected from Authentication Method.
      Password Password associated with the username. This field appears only when Basic Authentication is selected from Authentication Method.
    4. Configure the connection security method.
      • If you want to use Java security CA certificates to establish a secure connection with the data source, select Default.

        This option uses public certificates already available in the Java security truststore.

      • If your data source requires one-way SSL and uses its own certificates, select TLS.

        Only one-way TLS (server validation) is supported. mTLS isn't supported.

    5. If you selected TLS, attach the Base64-encoded truststore PEM file.
      OptionDescription
      Attach TrustStore file Upload the PEM file by selecting Attach PEM file and selecting the file.
      Enter TrustStore file contents Copy and paste the contents of the truststore file, verifying the content begins with:
      -----BEGIN CERTIFICATE-----
      and ends with:
      -----END CERTIFICATE-----
    6. Select Connect.
    7. In the DataFabric Connector Properties [sn_df_connector_properties] table, set properties for queries that retrieve data from Prometheus.
      1. Enter sn_df_connector_properties.LIST in the navigation filter.
      2. Set the following properties.
        • prometheus.max.query.range.duration — Defines the maximum span of time series data that the Prometheus connector can retrieve in a single query.
        • prometheus.query.chunk.size.duration — Specifies the duration of each time chunk when splitting a query range into smaller intervals. Accepts standard duration notation (for example, 1y, 1w, 1d, 1h, 30m). The connector executes one query per chunk, reducing the risk of timeouts and improving performance on the Prometheus server. For more information, see Range Vector Selectors.

    Result

    A test connection is made to the external data source, verifying that the connection details are correct and the data source is accessible.

    What to do next

    If the connection succeeds, configure data steward access on the Access Control tab. See .

    If the connection fails, verify the connection details with your data source administrator and try again.