> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/resilience-testing/chaos-engineering/use-chaos-engineering/probes/prometheus-probes/configure-prom-probe.md).

# Configure Prometheus Probe

* [What is a Resilience Probe?](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/index.md#what-is-a-resilience-probe)
* [Prometheus Probe](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/prometheus-probes/index.md)

## Configuration <a href="#configuration" id="configuration"></a>

1. Go to **Chaos Engineering** module and select **Resilience Probes**. Select **New Probe**.

   ![navigate to module](/files/VAskr9LQaM6MMV6LRdEb)
2. Select infrastructure type as **Kubernetes** and chaos probe as **Prometheus**.

   ![prometheus probe](/files/DT7a2l3UROTPYkEDosWA)
3. Provide the name, and click **Configure Details**.

   ![configure details](/files/8NiJcYQ5i6c6yp4zNwjJ)
4. Based on your application's requirements, provide values for the following parameters.

* **Prometheus Endpoint**: It is the target HTTP/HTTPS endpoint that the probe will send requests to.

  ![](/files/ZZ8BnJ4sMwxNNVS76LUE)

5. **Authorization** section has the following fields:

   * **Type**: Type of HTTP request to be performed. Supports `GET` and `POST`.
   * **Credentials**: Authentication credentials (username and password) required to access the target URL/endpoint. This field is mutually exclusive with **Credentials file** field.
   * **Credentials file**: Path of the file that contains authentication credentials to access the HTTP endpoint. This field is mutually exclusive with **Credentials** field.

   Go to [Authorization](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/prometheus-probes/index.md#authentication) for more information.

   ```
    **TLS Config** has the following fields:

        - **CA file**: Path of the file to validate the custom certificates for TLS of the target URL.
        - **Cert file**: Path of the file to the client certificate required for mTLS.
        - **Key file**: Path of the file to the client key required for mTLS.
        - **Insecure Skip Verify**: If enabled, the probe bypasses the SSL/TLS certificate verification, allowing requests to proceed even if the certificate is invalid or self-signed.
    
   ```

   Go to [TLS](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/prometheus-probes/index.md#tls) for more information.

   ![](/files/sqO4M6XrpkDFVPhNMRRn) ![](/files/4mPQuXB0CFAmfnh6hhGG)
6. Provide the **Prometheus Query** (**Query** or **Query Path** depending on your usage).

   * **Query**: The PromQL query used with the probe to fetch the desired Prometheus metrics. Ensure that the strings inside the query are enclosed within backslash ("/"). This field is mutually exclusive with **Query Path** field.
   * **Query Path**: Path of the file where PromQL query is present. This field is mutually exclusive with **Query** field.

   Go to [Schema](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/prometheus-probes/index.md#schema) for more information.

   ![](/files/Ws80VI9ck6vBgbDHqami)
7. Specify the data comparison fields, and click **Configure Properties**.

   The data returned using the PromQL **Query** or **Query Path** is compared to the following fields:

   * **Type**: Type of data compared with result of Prometheus query. Accepts only `float` data type.
   * **Comparison Criteria**: The criteria (`>=`, `<=`, `==`, `<`, `>`, `!=`, and so on) based on which the **value** and the result of Prometheus query are compared.
   * **Value**: The value with which the result of Prometheus query is compared

   Go to [Comparator](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/prometheus-probes/index.md#comparator) for more information.

   ![](/files/Iy7DcAZirQhcEV8PxlV5)
8. Specify general probe properties such as timeout, interval, and so on. Click **Create Probe**.

* **Timeout**: Time limit for the probe to execute the check and return the expected output.
* **Interval**: Duration for which the probe waits between subsequent attempts.
* **Attempt**: Number of times a check is executed upon failure in the previous attempts before declaring the probe status as `FAILED`.
* **Polling Interval**: Time interval for which `continuous` and `onchaos` probe modes should wait after each iteration.
* **Initial Delay**: Duration to wait before the probe begins execution.
* **Verbosity**: Level of detail to include in the logs generated during the execution of the probe. Choose between `info` (essential logs, probe status are printed) and `debug` (in-depth logs, timestamps, and execution logs are printed) mode.
* **Stop on Failure (Optional)**: Enable it to continue or disable it to stop the experiment execution after the probe fails. Disabled by default.

Go to [Run Properties](/resilience-testing/chaos-engineering/use-chaos-engineering/probes/prometheus-probes/index.md#run-properties) for more information.

![](/files/czQmDuqqXswwqejguoNX)