stac
CLI yet?sts
CLI. Use the stac
CLI.topologyElementIdentifier
does not match any identifiers
from the StackState topology. Use the CLI command show sub stream status to verify if there are any Check states with identifier which has no matching topology element
.stac
CLI yet?sts
CLI. Use the stac
CLI.stac
CLI yet?sts
CLI. Use the stac
CLI.Errors for non-existing sub streams:
as some errors are only relevant when a sub stream could not be created, for example StreamMissingSubStream
. Sub stream errors can be any of the documented error messages.stac
CLI yet?sts
CLI. Use the stac
CLI.stac
CLI yet?sts
CLI. Use the stac
CLI.-t
command line argument. This is helpful to identify any health states that are not 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
.stac
CLI yet?sts
CLI. Use the stac
CLI.delete
stream functionality is helpful while setting up a health synchronization in StackState. It allows you 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 do not want to keep using it.stac
CLI yet?sts
CLI. Use the stac
CLI.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 is not known to StackState. The only way to suppress such an error would be to use the clear-errors
command.stac
CLI yet?sts
CLI. Use the stac
CLI.SubStreamStopWithoutStart
will be closed once the health synchronization observes a start snapshot message followed by a stop snapshot message.start_snapshot
or expiry
.repeat_interval_s
greater than the configured max of 30 minutes.repeat_interval_s
established in the start snapshot message. In this case an automatic stop snapshot will be applied.expiry_interval_s
. In this case, the sub stream will be deleted.repeat_interval_s
.{"checkStateId":"checkStateId3","health":"deviating","message":"Unable to provision the device. ","topologyElementIdentifier":"server-3"}
and transformation Default Transformation
.previous_checkpoint
previous_checkpoint
that is not equivalent to the last observed one.checkpoint
that precedes the last observed one, meaning that its data that StackState already received.check_state_id
is not present on the sub stream.