Debug health synchronization
StackState Self-hosted v5.1.x
Last updated
StackState v5.1
StackState Self-hosted v5.1.x
Last updated
The can be used to troubleshoot a health synchronization and fix issues that might prevent health data from being correctly ingested and displayed in StackState. This page describes the general troubleshooting steps to take when debugging a health synchronization, as well as the CLI commands used, and a description of the error messages returned.
When debugging the health synchronization there are some common verification steps that can be made no matter what the specific issue is:
.
If you are using sub streams, . The response will also show the number of check states on the substream. This lets you know if the data is being ingested and processed.
Investigate further:
Stream present - , this will show the metrics latency of the stream and any .
Streams / sub streams present, but there are no check states - Confirm that the payload sent to the Receiver API adheres to the .
No streams / sub streams are present - Use the CLI command below to verify that health data sent to the Receiver API is arriving in StackState:
There can be two reasons for a check state not to show on a component in StackState:
Returns a list of all current synchronized health streams and the number of sub streams included in each.
Returns a list of all sub streams for a given stream URN, together with the number of check states in each.
The substream status provides useful information to verify that StackState could bind check states sent from an external system to existing topology elements. This information is helpful to debug why a specific check isn't visible on the expected topology element.
The substream status can be expanded to include details of matched and unmatched check states using the -t command line argument. This is helpful to identify any health states that aren't attached to a topology element. In the example below, checkStateId2 is listed under Check states with identifier which has no matching topology element. This means that it was not possible to match the check state to a topology element with the identifier server-2.
The delete stream functionality is helpful while setting up a health synchronization in StackState. You can use it to experiment, delete the data and start over again clean. You can also delete a stream and drop its data when you are sure that you don't want to keep using it.
The clear-errors option removes all errors from a health stream. This is helpful while setting up a health synchronization in StackState, or, for the case of the TRANSACTIONAL_INCREMENTS consistency model, when some errors can't be removed organically. For example, a request to delete a check state might raise an error if the check state isn't known to StackState. The only way to suppress such an error would be to use the clear-errors command.
StreamMissingSubStream
Raised when the health synchronization receives messages without a previous stream setup message as start_snapshot or expiry.
StreamConsistencyModelMismatch
Raised when a message is received that belongs to a different consistency model than that specified when the stream was created.
StreamMissingSubStream
Raised when the health synchronization receives messages with a previous start snapshot in place.
SubStreamRepeatIntervalTooHigh
Raised when the health synchronization receives a repeat_interval_s greater than the configured max of 30 minutes.
SubStreamStartWithoutStop
Raised when the health synchronization receives a second message to open a snapshot when a previous snapshot was still open.
SubStreamCheckStateOutsideSnapshot
Raised when the health synchronization receives external check states without previously opening a snapshot.
SubStreamStopWithoutStart
Raised when the health synchronization receives a stop snapshot message without having started a snapshot at all.
SubStreamMissingStop
Raised when the health synchronization doesn't receive a stop snapshot after time out period of two times the repeat_interval_s established in the start snapshot message. In this case an automatic stop snapshot will be applied.
SubStreamExpired
Raised when the health synchronization stops receiving data on a particular substream for longer than the configured expiry_interval_s. In this case, the substream will be deleted.
SubStreamLateData
Raised when the health synchronization doesn't receive a complete snapshot timely based on the established repeat_interval_s.
SubStreamTransformerError
Raised when the health synchronization is unable to interpret the payload sent to the receiver. For example, "Missing required field 'name'" with payload {"checkStateId":"checkStateId3","health":"deviating","message":"Unable to provision the device. ","topologyElementIdentifier":"server-3"} and transformation Default Transformation.
SubStreamMissingCheckpoint
Raised when a Transactional increments substream previously observed a checkpoint, but the received message is missing the previous_checkpoint
SubStreamInvalidCheckpoint
Raised when a Transactional increments substream previously observed a checkpoint, but the received message has a previous_checkpoint that isn't equivalent to the last observed one.
SubStreamOutdatedCheckpoint
Raised when a Transactional increments substream previously observed a checkpoint, but the received message has a checkpoint that precedes the last observed one, meaning that its data that StackState already received.
SubStreamUnknownCheckState
Raised when deleting a Transactional increments check_state and the check_state_id isn't present on the substream.
The health check state hasn't been created. Follow the to confirm that the stream / substream has been created and that data is arriving in StackState.
The health check state was created, but its topologyElementIdentifier doesn't match any identifiers from the StackState topology. Use the CLI command to verify if there are any Check states with identifier which has no matching topology element.
The main reason for this is that the latency of the health synchronization is higher than expected. Use the CLI command to confirm the latency of the stream as well as the throughput of messages and specific check operations. It may be necessary to tweak the data sent to the health synchronization, or the frequency with which data is sent.
➡️
➡️
The stream status command returns the aggregated stream latency and throughput metrics. This is helpful when debugging why a health check takes a long time to land on the expected topology elements. It will help diagnose if the frequency of data sent to StackState should be adjusted. The output includes a section Errors for non-existing sub streams: as some errors are only relevant when a substream couldn't be created, for example StreamMissingSubStream. Substream errors can be any of the documented .
➡️
➡️
➡️
➡️
➡️