Importing resilience data from Prometheus

Edit online

Using Concert Workflows, you can import a prebuilt workflow from the library designed to facilitate resilience data collection in Prometheus and send it to your Concert instance to assess against the defined requirements for a given application. The workflow collects metrics such as latency, throughput, and error rate from Prometheus and maps them to metrics in a Concert resilience profile.

Before you begin

You must ensure Prometheus server is active and exposes metric endpoints for your applications.
You must have an application that exists in Concert and is linked to a resilience profile containing metrics such as Availability, Latency, Throughput, Error rate, and Disk or Swap usage.
You must have permission to import workflows from the Automation library and can create Authentications.
You should ensure that Prometheus endpoint is reachable from your Concert instance.
Note: Metric freshness depends on Prometheus scrape intervals and retention settings.

Step 1: Download and import the prebuilt workflow

In Concert Workflows, in the Workflows page, click Create workflow > Select from library. choose the Prometheus workflow, and import it. For more information about importing Concert-specific workflows into Concert Workflows, see creating workflows.

Step 2: Create the required authentications

The Prometheus workflow requires two authentications to establish a valid connection with the external systems referenced in the workflow:

Create an authentication for the Prometheus service. When doing so, you must provide the connection parameters of your Prometheus server, including the protocol, host, and port number. You can also specify credentials username and password if your Prometheus instance requires authentication.
After entering these details, click Test authentication to verify the connection, and then click Create to save it.

Step 3: Edit the imported workflow

After importing the workflow, you must provide the parameter values and authentications that are required to run it.

Click the overflow menu (in the Actions column) next to the Prometheus workflow you imported, and select Open to open the workflow editor.
The User variables section displays the parameters that are referenced throughout the workflow.
Enter the following parameter values listed in the User variables section of the workflow editor:
- in_concert_key- Choose the authentication key for your Concert instance. The recommended value is ibmconcert/hub-self.
- in_profile_name- Enter the name of the resilience profile in Concert where the Prometheus data will be mapped.
- application_name_version - Provide the application identity and mapping. At minimum, include the Concert application name and version, also include the Prometheus job mapping as shown in the following example.
```
{
  "concert_app_name": "node_exporter",
  "concert_app_version": "1.8.1",
  "mapping": [
    {
      "tool": "prometheus",
      "job_name": "node_exporter",
      "job_version": ""
    }
  ]
}
   
```
  Make sure that the application name and version match your Concert inventory and that the job_name matches the Prometheus target label.
Click Save.
Attention: If the resilience profile name or target identifiers are missing or mismatched, the workflow run fails with an error such as Profile name or target missing — cannot create posture.

Step 4: Run the workflow or schedule a Concert Workflows job

To run the workflow manually:

Navigate to the Workflows page.
Click the overflow menu (in the Actions column) next to the Prometheus workflow you imported.
Click Run.

To schedule recurring workflow jobs:

To configure recurring data ingestion, create a Concert Workflows job to automatically initiate resilience data ingestion from Prometheus at a defined interval. Refer to creating jobs for instructions.

To trigger a workflow using automation rules:

You can create an automation rule to trigger a workflow based on a specific condition in your Concert instance. This requires you to establish a connection between Concert and your Concert Workflows instance. Refer to Automating Concert Workflows using automation rules.

Step 5: Review resilience assessment details

After running the workflow, you can review the data that is ingested from Prometheus in the resilience posture assessment details for the corresponding application.

In Concert, go to Dimensions > Resilience.
In the Postures tab, scroll down and click the name of the posture assessment plan from the list to view details.
In the Assessment summary tab, scroll down to view a list of metrics.
The list contains all the metrics collected related to this posture assessment, including those ingested from Prometheus. Refer to the Source column in the table to verify the origin of each ingested metric.