How does Hantera trace work across the platform?
The Monitoring area can trace one unit of work across ingresses, jobs, egresses, actors, and Sendings in a shared operational view.
Read the full answerQuestions about safe changes, monitoring, authority, and keeping complex operations understandable.
The Monitoring area can trace one unit of work across ingresses, jobs, egresses, actors, and Sendings in a shared operational view.
Read the full answerHantera Monitoring keeps operational statistics per external host as well as per egress, helping teams distinguish a slow integration implementation from a slow partner system.
Read the full answerHantera audit logs record system-level platform actions with the affected resource path, action, timestamp, field-level changes, and the initiating identity when one is available.
Read the full answerYes. Hantera can query audit logs by resource-path prefix, time range, or changed field, with cursor-based pagination for moving through the results.
Read the full answerWhen commands change an actor, Hantera persists a checkpoint with an identifier, timestamp, and optional change metadata. Teams can use those checkpoints to inspect the actor's historical state.
Read the full answerYes. Hantera can combine a checkpoint rewind with preview mode to show an earlier actor state in an isolated transaction; the changes are rolled back and no data is persisted.
Read the full answerHantera requires a dedicated rewind permission to persist a rewind. A separate preview-only permission can allow historical-state investigation without allowing a stored change.
Read the full answerYes. A Hantera rewind preserves the original mutation history, appends a new checkpoint for the rewind, and adds an activity-log entry for the operation.
Read the full answer