Logging, debugging, testing

Logging

For a comprehensive guide to logging from all component types, see the Logging page.

In summary:

• obelisk:log interface (preferred): Structured string-based logging with log levels (trace, debug, info, warn, error). Available to activities, workflows, and webhook endpoints.
• stdout/stderr forwarding: Byte-stream output from println! and similar. Available to activities and webhook endpoints only. Controlled by forward_stdout and forward_stderr in the configuration.

Debugging and Testing

Unit and integration testing is possible with Cargo's test harness.

The stargazers demo repository contains unit and integration tests for activities.