Managing Metrics

This Micro-Integration uses Spring Boot Metrics, which leverages Micrometer to manage its metrics.

Connector Meters

In addition to the meters provided by the Spring framework, this Micro-Integration 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)`	The 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)`	The 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>`	The message payload size.
`solace.connector.message.size.total`	`DistributionSummary` Base Units: `bytes`	`name: <bindingName>`	The total message size.
`solace.connector.publish.ack`	`Counter` Base Units: `acknowledgments`	`name: <bindingName>` `result: (success \| failure)` `exception: (none \| exception simple class name)`	The publish acknowledgment count.
`solace.connector.transform.expressions.count`	`Gauge` Base Units: `expressions`	`workflow.id: <workflowId>`	Transformation expressions count
`solace.connector.transform.time`	`Timer`	`workflow.id: <workflowId>` `result: (success \| failure)`	Transformation execution time	This is the aggregate time for all expressions used to transform a single message.

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.

Provide feedback