Managing Metrics

This connector uses Spring Boot Metrics, which leverages Micrometer to manage its metrics.

Connector Meters

In addition to the meters provided by the Spring framework, this connector supplies the following custom meters:

Name Type Tags Description Notes

solace.connector.process

Timer

type: channel

name: <bindingName>

result: (success | failure)

exception: (none | exception simple class name)

Processing time

This meter is a rename of spring.integration.send, whose name tag matches a binding name.

solace.connector.error.process

Timer

type: channel

name: <bindingNames>

result: (success | failure)

exception: (none | exception simple class name)

Error processing time

This meter is a rename of spring.integration.send, whose name tag matches an input binding's error channel name (<destination>.<group>.errors).

Meters might be merged under the same name tag (delimited by |) if multiple bindings have the same error channel name (that is, bindings have matching destination, group, or both).

Setting a binding's group is not supported.

solace.connector.message.size.payload

DistributionSummary

Base Units: bytes

name: <bindingName>

Message payload size

 

solace.connector.message.size.total

DistributionSummary

Base Units: bytes

name: <bindingName>

Total message size

 

solace.connector.publish.ack

Counter

Base Units: acknowledgments

name: <bindingName>

result: (success | failure)

exception: (none | exception simple class name)

Publish acknowledgment count

 

The solace.connector.process meter with result=failure is not a reliable measure of tracking the number of failed messages. It only tells you how many times a step processed a message, how long it took to process that message, and if that step completed successfully.

Instead, we recommend that you use a combination of solace.connector.error.process and solace.connector.publish.ack to track failed messages.

Adding a Monitoring System

The following monitoring systems are supported:

To use a different monitoring system, add the system’s micrometer-registry-<system> JAR file and its dependency JAR files to the connector’s classpath (see Adding External Libraries). The included systems can then be individually enabled by setting management.<system>metrics.export.enabled=true in the application.yml file.