Log streaming
Send bounded audit and sign-in event projections to an external destination.
Log streams send audit and sign-in event projections to Datadog, Splunk HEC, HTTPS or S3. Create with POST /v1/log_streams, list with GET /v1/log_streams, and delete with DELETE /. Use environment credentials with the corresponding log_streams:read or log_streams:write scope.
Allowance and usage
Section titled “Allowance and usage”Streams are an add-on on every plan, including Free. Business includes two destinations and Enterprise includes ten; a larger allowance is available on request. Creation beyond the current allowance returns plan_limit_reached. A downgrade retains existing streams and does not stop their delivery.
The pricing policy is $10 per destination per month, with the first 5 GB per month free and $0.50 per additional GB, all excl. taxes.
List responses expose public destination configuration, the current UTC usage_month and delivered_bytes as a decimal string. Bytes are counted once per immutable acknowledged delivery result, using uncompressed transport bytes. These totals are not proof that a receiver indexed the event.
Configure a destination safely
Section titled “Configure a destination safely”Choose datadog, splunk_hec, http or s3 and supply the matching fields in the API reference. Credentials are write-only and encrypted to the environment and destination. They are never returned by list operations. Do not put tokens in endpoint URLs.
HTTP destinations require checked public HTTPS endpoints without user information, query or fragment; redirects are refused. S3 uses supplied credentials and supported regional endpoints. This is not an arbitrary network forwarding service.
Environment and organization destinations
Section titled “Environment and organization destinations”A stream you create with /v1/log_streams belongs to the environment and receives audit and sign-in records for every organization.
An organization’s IT admin can also add destinations from the hosted portal, through a setup link with the log_streams intent. These destinations:
- use the same body and validation as the management API;
- receive only that organization’s sign-in records, never audit records;
- are listed only to that organization, and the environment-wide streams are never shown to it;
- count against the environment’s destination allowance.
The portal needs a plan with log stream destinations (Business and above, or the add-on); otherwise it answers plan_limit_reached. Creating and deleting are audited with the IT admin as the actor.
Delivery and deletion
Section titled “Delivery and deletion”Retries remain within the original 72-hour source/delivery deadline. Delayed fanout does not extend it. Provider acceptance followed by a crash can cause a retry to duplicate remote delivery; there is no exactly-once guarantee. A failed or unconfirmed operation can also remain unmetered until local completion.
Deletion scrubs stored credentials and cancels pending payloads. An already in-flight operation can still reach the receiver. Keep receiver-side deduplication and your own retention policy where required; service cleanup requires the worker to run.
Failover customers receive edge.failover.* events and status-page information.