Documentation forSolarWinds Observability SaaS

Forward Auth0 tenant events (Papertrail)

You can forward Auth0 tenant events to Papertrail using an Auth0 event stream with a webhook destination.

How it works

An Auth0 event stream delivers tenant events to an HTTPS endpoint as CloudEvents JSON. Auth0 sends the events in batches, and the Papertrail bulk endpoint stores each line as a separate log entry.

The ingestion token is supplied in the endpoint URL rather than in an Authorization header. The event stream configuration allows only one custom header, which is used to set the System name.

Events are stored with their original CloudEvents JSON as the message text, so fields such as type, a0tenant, and a0stream are searchable as text.

Prerequisites

  • A Papertrail ingestion token from a token-based destination. To get a destination and token in Papertrail, add a new log destination. The ingestion token is generated along with the destination.

  • The data center the organization uses (na-01, na-02, eu-01, or ap-01). This appears in the URL used to sign in, for example, my.na-01.cloud.solarwinds.com.

  • An Auth0 tenant and permission to create event streams in the Auth0 Dashboard.

Setup

Step 1: Create the event stream

In the Auth0 Dashboard, create a new event stream with a webhook destination. Give it a name that identifies the destination, such as Papertrail.

Step 2: Configure the endpoint and the header

Complete the stream configuration as follows:

Field Value
Endpoint https://logs.collector.<REGION>.cloud.solarwinds.com/v1/logs/bulk/<TOKEN>
Authentication method Custom header
Header key X-Otel-Resource-Attr
Header value host.name=auth0

Replace <REGION> with the data center of the organization and <TOKEN> with the ingestion token.

The X-Otel-Resource-Attr header sets the System name for every event in the stream. Without it, the System column shows the IP address that sent the events.

Because the token is part of the URL, anyone who can read the stream configuration can send logs with it. To replace a token, create a new destination token and update the endpoint.

Step 3: Select the events and enable the stream

Select the event types to deliver, then save and enable the stream. Auth0 starts delivering events as they occur.

Verify ingestion

Trigger an event in the Auth0 tenant, then search the Logs Explorer for specversion or for the tenant name. Each Auth0 event appears as one entry, the System column shows auth0, and the message text contains the full CloudEvents JSON.

If events do not arrive, check the delivery status of the stream in the Auth0 Dashboard. A 401 response means the token or the region in the endpoint URL is wrong, and a 413 response means a batch exceeded the size limits of 1 MB per event and 5 MB per request.

Notes

  • Severity is always Info. Auth0 events carry no field that the collector maps to a syslog severity.

  • The System name applies to the whole stream rather than to individual events. The Program column stays empty unless service.name is added to the same header, as in host.name=auth0, service.name=auth0.

  • To forward several Auth0 tenants to one destination, create one event stream per tenant and set host.name to the tenant name so that the tenants can be told apart.

Remove or reset the configuration

To stop forwarding events, disable or delete the event stream in the Auth0 Dashboard. To change the destination, the token, or the region, update the Endpoint field. To change the System name, update the header value.