Configuring Integration runtime tracing for end-to-end monitoring

Integration runtime tracing integration enables monitoring of integration flows, including message processing times, transformation performance, and connector operations. This task focuses on configuring OpenTelemetry tracing on an already deployed integration runtime.

• Ensure you have an integration runtime and integration dashboard deployed

• Create a service account token for authentication. For more information, see Creating a service account for authentication

This method configures an integration runtime to send traces directly to the end-to-end monitoring collector using authentication through a vault.

1. From your terminal, create a vault for storing the authentication credentials:

   ibmint create vault e2em --prompt

2. Add the service account token to the vault.

3. Retrieve the service account token:

   oc get secret -n your-product-namespace e2em -o jsonpath="{.data.token}" | base64 -d

4. Export the vault as an archive:

   ibmint export credentials --archive-location e2em.zip --archive-key vaultkey --external-directory-vault e2em --external-directory-vault-key vaultkey

5. Get the end-to-end monitoring CA certificate:

   oc get configmap openshift-service-ca.crt -o jsonpath="{.data['service-ca\.crt']}" > e2em-ca.crt

6. Create a zip file containing the CA certificate:

   zip e2em-cacert ca.crt

7. Create an App Connect server.conf.yaml configuration that enables OpenTelemetry:

   serverConfVersion: 1
   ResourceManagers:
     OpenTelemetryManager:
       openTelemetryEnabled: true
       exporterOtlpGrpcEndpoint: <e2em_collector_endpoint>
       openTelemetryTruststoreType: PEM
       openTelemetryTruststoreFile: /home/aceuser/generic/e2em-ca.crt
       openTelemetryGrpcSecurityId: e2em

   For more information about how to get the OpenTelemetry endpoint, see Getting the OTel endpoint for end-to-end monitoring.

8. Add all configurations to the runtime: vault archive, vault archive key, generic files with CA certificate, and server configuration YAML.

9. When you invoke the runtime endpoint, traces display in end-to-end monitoring.

When you invoke the runtime endpoint, traces are generated and display in end-to-end monitoring. You can view integration flow execution, message processing times, and connector operations in the end-to-end monitoring UI.

• Validate that traces are displaying in the end-to-end monitoring UI.

• Configure additional integration runtimes to send traces.

• Set up alerts for integration runtime failures or performance issues.