Insights Metrics: Micro-Integrations

Solace Insights Metrics and Checks provides information about using, filtering, and understanding the metrics collected by Insights.

This page contains metrics collected from Micro-Integrations deployed in your estate. These metrics are used by the Micro-Integration Details dashboard and Micro-Integration Monitors.

Metric Families

Micro-Integrations emit two families of metrics:

  • solace.connector.* (original metrics): Available on all Micro-Integrations. These metrics include pre-computed statistics such as averages, maximums, and percentiles.
  • solace.connector.v2.* (v2 metrics): Available on Micro-Integrations running connector Helm chart v1.5.0 or later. Micro-Integrations on this chart emit both metric families.

The v2 metrics will become the standard. The original metrics remain available for backward compatibility.

Key Differences Between Metric Families

When using v2 metrics, be aware of these differences:

  • Count and sum only: v2 metrics publish .count and .sum rather than pre-computed statistics. To calculate an average, divide sum by count. Datadog's aggregation handles peaks and rollups from there. However, per-message percentiles (such as 95th percentile latency) are not recoverable from count and sum—use the original metrics for those statistics.
  • Timing units: v2 timing metrics (v2.process.sum, v2.error.process.sum, v2.transform.time.sum) are in seconds. The original timing metrics are in milliseconds.
  • Tag spelling: Workflow tags use underscores in v2 metrics (workflow_id, workflow_name) but dots in original metrics (workflow.id).
  • Collection interval: v2 metrics are collected every 60 seconds; original metrics are collected every 10 seconds. A newly started Micro-Integration may appear to have missing v2 data for the first couple of minutes.

This page contains metrics for:

Micro-Integration Metric Tags

The following tags are available for filtering and aggregating Micro-Integration metrics. Most tags use the same spelling in both metric families, but workflow tags differ—see the notes below.

  • micro_integration_name: The human-readable name of the Micro-Integration. This tag is present on all metrics and is the most useful filter for identifying specific Micro-Integrations in alerts and dashboards.

  • connector_flow_id: The unique identifier for the Micro-Integration instance.

  • name: The binding name (for example, input-0, output-0, or dmq-output-* for dead message queue bindings).

  • workflow.id / workflow_id: The identifier for the transformation workflow. Original metrics use workflow.id (with a dot); v2 metrics use workflow_id (with an underscore). Both tags require connector Helm chart v1.4.0 or later and are not available from Micro-Integrations running on older Helm charts.

  • workflow.name / workflow_name: The name of the transformation workflow. Original metrics use workflow.name (with a dot); v2 metrics use workflow_name (with an underscore). Both tags require connector Helm chart v1.4.0 or later and are not available from Micro-Integrations running on older Helm charts.

  • component: The component being measured (for example, root for health metrics).

  • result: The outcome of an operation (for example, success or failure). Used by processing metrics and transformation time metrics.

  • status: The outcome of a publish operation (for example, success or failure). Used by publish acknowledgment metrics.

  • exception: The exception type for failed operations. Used by processing and publish acknowledgment metrics.

  • endpoint: The scrape endpoint. Available on v2 metrics only.

Health Metrics

These metrics report the health status of Micro-Integrations. The Micro-Integration Monitors monitor uses these metrics to detect when a Micro-Integration is down or not processing messages.

Metric
Name		 Unit (If Applicable) Polling
Frequency
in Seconds		 Tags Description

solace.connector.health

 HTTP status code 10

connector_flow_id

component

micro_integration_name

The health status of the Micro-Integration. Cloud-managed Micro-Integrations emit a value of 200 when healthy and 503 when down. The Micro-Integration Monitors monitor alerts when this value exceeds 200.

Use the component:root tag to filter for overall Micro-Integration health.

Self-managed Micro-Integration deployments can customize the health status mapping through application properties.

solace.connector.v2.health

 HTTP status code 60

connector_flow_id

component

micro_integration_name

endpoint

v2 metric. The health status of the Micro-Integration. Equivalent to solace.connector.health.

Message Volume and Size Metrics

These metrics track the volume and size of messages processed by Micro-Integrations. You can use these metrics to monitor throughput and identify unusual message patterns.

Metric
Name		 Unit (If Applicable) Polling
Frequency
in Seconds		 Tags Description

solace.connector.message.size.payload.avg

 bytes 10

connector_flow_id

micro_integration_name

name

workflow.name

The average payload size of messages processed by the Micro-Integration. Filter by name to see payload sizes per binding.

solace.connector.message.size.payload.max

 bytes 10

connector_flow_id

micro_integration_name

name

workflow.name

The maximum payload size of messages processed by the Micro-Integration.

solace.connector.message.size.total.avg

 bytes 10

connector_flow_id

micro_integration_name

name

workflow.name

The average total message size (including headers and metadata) processed by the Micro-Integration.

solace.connector.message.size.total.max

 bytes 10

connector_flow_id

micro_integration_name

name

workflow.name

The maximum total message size (including headers and metadata) processed by the Micro-Integration.

solace.connector.message.size.total.count

 count 10

connector_flow_id

micro_integration_name

name

workflow.name

The count of messages processed. This metric powers the Message throughput per flow widget on the Micro-Integration dashboards.

solace.connector.v2.message.size.total.count

 count 60

connector_flow_id

micro_integration_name

name

workflow_name

endpoint

v2 metric. The count of messages processed. Use with v2.message.size.total.sum to calculate average total message size.

solace.connector.v2.message.size.total.sum

 bytes 60

connector_flow_id

micro_integration_name

name

workflow_name

endpoint

v2 metric. The sum of total message sizes (including headers and metadata). Divide by v2.message.size.total.count to calculate average.

solace.connector.v2.message.size.payload.count

 count 60

connector_flow_id

micro_integration_name

name

workflow_name

endpoint

v2 metric. The count of messages processed. Use with v2.message.size.payload.sum to calculate average payload size.

solace.connector.v2.message.size.payload.sum

 bytes 60

connector_flow_id

micro_integration_name

name

workflow_name

endpoint

v2 metric. The sum of message payload sizes. Divide by v2.message.size.payload.count to calculate average.

Processing Performance Metrics

These metrics track how messages are processed by Micro-Integrations, including processing time and error rates. The Micro-Integration Monitors monitor uses these metrics.

Metric
Name		 Unit (If Applicable) Polling
Frequency
in Seconds		 Tags Description

solace.connector.process.count

 count 10

connector_flow_id

micro_integration_name

name

workflow.name

result

exception

The count of messages processed by the Micro-Integration. Use the result tag to filter by success or failure.

This metric does not capture transformation failures. Messages that fail transformation are acknowledged after being sent to the dead message queue (DMQ), so they appear as successful processing. Use the Publish Acknowledgment Metrics with name:dmq-output-* to detect transformation failures.

solace.connector.process.avg

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

name

workflow.name

The average time to process a message, measured from receipt to acknowledgment.

solace.connector.process.max

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

name

workflow.name

The maximum time to process a message.

solace.connector.process.median

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

name

workflow.name

The median time to process a message. Half of messages are processed faster than this time, half slower.

solace.connector.process.95percentile

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

name

workflow.name

The 95th percentile processing time. 95% of messages are processed within this time.

Percentile statistics are not available in v2 metrics. Use this original metric for percentile analysis.

solace.connector.error.process.count

 count 10

connector_flow_id

micro_integration_name

name

workflow.name

result

exception

The count of messages processed by the error handler. Use the exception tag to filter by error type.

The result tag on error.process.* metrics only ever takes the value success. This indicates the error handler itself ran successfully—it does not reflect the outcome of the original message processing. To find messages that failed processing, use solace.connector.process.count with result:failure.

solace.connector.error.process.avg

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

name

workflow.name

The average time to process messages that resulted in errors.

solace.connector.error.process.max

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

name

workflow.name

The maximum time to process messages that resulted in errors.

solace.connector.error.process.median

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

name

workflow.name

The median time to process messages that resulted in errors.

solace.connector.error.process.95percentile

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

name

workflow.name

The 95th percentile time to process messages that resulted in errors.

solace.connector.v2.process.count

 count 60

connector_flow_id

micro_integration_name

name

workflow_name

result

exception

endpoint

v2 metric. The count of messages processed. Use the result tag to filter by success or failure. Use with v2.process.sum to calculate average processing time.

solace.connector.v2.process.sum

 seconds (s) 60

connector_flow_id

micro_integration_name

name

workflow_name

result

exception

endpoint

v2 metric. The sum of processing time in seconds. Divide by v2.process.count to calculate average processing time.

solace.connector.v2.error.process.count

 count 60

connector_flow_id

micro_integration_name

name

workflow_name

result

exception

endpoint

v2 metric. The count of processing errors. Use with v2.error.process.sum to calculate average error processing time.

solace.connector.v2.error.process.sum

 seconds (s) 60

connector_flow_id

micro_integration_name

name

workflow_name

result

exception

endpoint

v2 metric. The sum of error processing time in seconds. Divide by v2.error.process.count to calculate average.

Publish Acknowledgment Metrics

These metrics track the success and failure of message publishing to output bindings. The Micro-Integration Monitors monitor uses these metrics to detect transformation failures by monitoring publishes to dead message queue (DMQ) bindings.

Metric
Name		 Unit (If Applicable) Polling
Frequency
in Seconds		 Tags Description

solace.connector.publish.ack

 count 10

connector_flow_id

micro_integration_name

name

workflow.name

status

exception

The count of publish acknowledgments received for messages sent to output bindings. Use the status tag to filter by success or failure.

To detect transformation failures, filter by name:dmq-output-*. Messages that fail transformation are published to the DMQ output binding. Any non-zero rate to DMQ bindings indicates transformation errors that require investigation.

solace.connector.v2.publish.ack.count

 count 60

connector_flow_id

micro_integration_name

name

workflow_name

status

exception

endpoint

v2 metric. The count of publish acknowledgments. Equivalent to solace.connector.publish.ack.

Transformation Metrics

These metrics track the performance of message transformations within Micro-Integrations. You can use these metrics to identify slow or failing transformation workflows.

Metric
Name		 Unit (If Applicable) Polling
Frequency
in Seconds		 Tags Description

solace.connector.transform.time.avg

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

workflow.id

workflow.name

result

The average time to execute message transformations. Filter by workflow.id to see transformation time per workflow, or by result to see times for successful or failed transformations.

solace.connector.transform.time.max

 milliseconds (ms) 10

connector_flow_id

micro_integration_name

workflow.id

workflow.name

result

The maximum time to execute message transformations. Filter by result to see times for successful or failed transformations.

solace.connector.transform.expressions.count

 count 10

connector_flow_id

micro_integration_name

workflow.id

workflow.name

The count of transformation expressions evaluated by the Micro-Integration. Filter by workflow.id to see expression counts per workflow.

solace.connector.v2.transform.time.count

 count 60

connector_flow_id

micro_integration_name

workflow_id

workflow_name

result

endpoint

v2 metric. The count of transformations. Use with v2.transform.time.sum to calculate average transformation time.

solace.connector.v2.transform.time.sum

 seconds (s) 60

connector_flow_id

micro_integration_name

workflow_id

workflow_name

result

endpoint

v2 metric. The sum of transformation time in seconds. Divide by v2.transform.time.count to calculate average.

solace.connector.v2.transform.expressions.count

 count 60

connector_flow_id

micro_integration_name

workflow_id

workflow_name

endpoint

v2 metric. The count of transformation expressions evaluated. Filter by workflow_id to see expression counts per workflow.