home / platform / monitoring

Know what happened, and where to look

Every flow run, every log line, and every credential use — captured, searchable, and shippable to the observability stack you already run.

run → log → view

Search first, ask questions later.

Flow execution logsEvery run, every record's path, searchable by flow, status, or date.
Scheduled & on-demand job historySee what ran, when, and whether it succeeded.
Structured application logsNot just flow runs — system events, auth attempts, and errors too.
Retention you controlKeep logs as long as your plan and compliance needs require.
Filter & searchFind the one failed record in a run of ten thousand.
No separate tool requiredThe log viewer ships inside Diselma; nothing extra to stand up.

log → your stack

Diselma's logs, in the observability tool your team already watches.

AWS CloudWatch LogsShip structured log events to a log group/stream.
Azure Monitor LogsSend records to a custom table via the Logs Ingestion API.
Google Cloud LoggingFormerly Stackdriver, via the Cloud Logging REST API.
Generic webhookForward log events to any endpoint you control.
File / syslogWrite to a local file or forward via syslog for legacy setups.
Multiple destinations at onceKeep the built-in viewer and ship to an external tool in parallel.

alert → escalate

Failures should page someone, not wait to be noticed.

Retry & failure alertingGet notified when a flow exhausts its retries.
Credential health alertsExpired tokens and failed auth surface before they cause a bigger outage.
Action & audit logsWho changed a flow, a credential, or a role, and when.
Role-based visibilityGive support staff log access without giving them credential access.
Exportable historyPull logs into a report or hand them to a client during a QBR.
Same infrastructure as productionThe monitoring your flows run on is the same system, not a bolted-on add-on.

See a failure before your customer does

Log viewing, alerting, and external log shipping ship standard on every plan.