Log and metric streams
Forward future application logs and container measurements to your own HTTPS collector.
Openstead can send JSON batches of logs or runtime metrics to a workspace's HTTPS destination. Open Observability in the dashboard as an owner or admin.
Configure a destination
- Choose Log Streams or Metrics Stream.
- Add the destination's public HTTPS URL on port 443.
- Supply an access token if your collector expects Bearer authentication.
- Save the enabled connection and send a delivery test.
Metrics streaming requires an authorized, deployed paid service in the workspace. Openstead forwards its JSON format; use a collector or adapter when your monitoring provider expects a different ingestion protocol.
Batch format
Both stream types use the webhook envelope with id, type, version, createdAt, workspaceId, and data.records.
logs.batch records contain:
| Field | Meaning |
|---|---|
id | Numeric source log identifier. |
serviceId, serviceName | Originating service. |
timestamp | Log timestamp. |
source | Build, runtime, or system source. |
level | Reported log level. |
message | Application output. |
metrics.batch records contain the same service identity and timestamp, plus cpuPercent, memoryBytes, memoryLimitBytes, networkReceivedBytes, networkSentBytes, and replicas.
Network values are container counters that include private traffic. Do not treat them as a public bandwidth invoice. Handle counter resets when containers restart.
Delivery behavior
Streams begin at activation and send future data. New or re-enabled destinations do not backfill older records. Preview-log forwarding follows workspace preferences.
Delivery uses a durable queue and retries failures up to eight attempts. Deduplicate by the delivery ID because an accepted batch may be delivered again. Return 2xx responses only after safely accepting the batch.
Collection pauses when a destination reaches 100 outstanding batches. Fix receiver failures promptly and use the delivery history to retry failed batches. Source retention is finite; a prolonged outage can outlast it.
Editing or disabling a destination cancels pending deliveries. Review the endpoint before saving changes because an in-flight request can still reach its earlier destination.
Protect application data
Log messages can contain sensitive values emitted by your application. Restrict collector access, avoid logging secrets in the application, and apply your own retention policy downstream. For an interactive retained-log reader, use the Logs API or CLI instead.