Skip to main content

Std-out logs

Structured logs that every Prequel service writes to std-out.

OTEL

Export OpenTelemetry traces and metrics to your observability stack.

Logging

The platform events Prequel records, reviewable through the logs API.

Webhooks

Subscribe to event types and push them to your systems as they happen.

​
Std-out logs

By default, all Prequel services surface structured logs to std-out. The structure of these logs should be somewhat intuitive, but please get in touch with the Prequel team if you have questions about the specific structure of certain logs. To facilitate debugging, we recommend ingesting these logs into AWS CloudWatch, GCP Logs Explorer, or your preferred logging solution.
Unsafe tracesOn occasion, an external dependency not controlled by Prequel (such as a database driver) will produce a trace that might have the potential to contain transfer data. These traces are tagged with the unsafe_trace key in any Prequel structured log.To ensure compliance with your own user-data retention policies, we suggest either not ingesting those keys to logs, or ensuring that your logs are in line with any retention policies you may be bound to. See the relevant GCP documentation and AWS documentation on how to avoid ingesting those logs.

​
Observability

Prequel code is instrumented with the Open Telemetry (OTEL) standard. Self-hosted deployments give the ability to export those telemetry events to the observability solution of your choice. We offer native support for solutions including Datadog, Elastic, Honeycomb, and more. Please get in touch with the team for information on how to set these up.