Manage log streaming

Log streaming is in Early Access and is only available to select customers. If you are interested in trying this feature, contact your Tealium Support representative.

Enable log streaming

1. Go to Server-Side Settings > Log Streaming.
2. Turn on Enable Log Streaming.
3. Save and publish the profile.

Create a destination

Create one destination for each external system that receives logs.

For example:

• Create a Datadog destination for monitoring and alerting.
• Create an Amazon S3 destination for long-term storage and auditing.

To create a destination:

1. In the admin menu, click Manage Log Streaming.
2. Click + New Destination.
3. Select a connector and click Next.
4. Turn on Status to enable the destination.
5. Enter a Name for the destination.
6. (Optional) Enter any Notes to describe the destination.
7. Configure authentication and connection settings. The required fields vary based on the connector you select.
8. Click Test Connection to verify connectivity.
9. Click Done.

Each destination has its own configuration requirements. Refer to the connector documentation for required fields and supported parameters. For a list of available connectors, see Available destination connectors.

Create a log source

Log streaming counts toward your outbound event connector calls. Monitor only the connectors and actions necessary for your use case.

To create a log source:

1. Open the log source dialog using one of the following:

   • From the Manage Log Streaming table, click + New Source in the destination row.
   • Select a destination, then click + New Source.

2. In the New Log Source dialog:

   1. Enter a Log Source Name.

   2. Select a Log Streaming Scope:

      • Send Entire Log Event: Sends all log attributes in the payload.
      • Send Log Event: Sends only mapped attributes in the payload.

      If only one option is available, it is selected by default. For more information, see Available destination connectors.

   3. The Log Source Type is set to Connector Errors.

   4. Review the sample payload on the right to understand the available fields.

   5. Click Continue.

3. Select connectors to monitor:

   1. Choose one or more connectors from the list.
   2. To refine what is logged, click Select Action Logs for a connector.

4. Configure action-level logging (optional):

   1. In the Select Actions to Log dialog, choose a Log Streaming Mode:
      • Send All (connector-level logging)
        Sends error logs for all actions in the connector, including actions added later.
      • Send Selected Actions (action-level logging)
        Sends logs only for the selected actions.
   2. If using Send Selected Actions, select the actions to monitor.
   3. Click Done.

5. Click Done to save the connector selection.

Map event attributes to vendor parameters

After configuring a log source, map Tealium log attributes to the parameters required by your destination system in the log source Settings tab.

For information about available vendor parameters, see the documentation for your destination connector and action and the connector log parameters.

How mapping works

Log streaming runs in a separate pipeline from standard event processing. Regular event attributes from visitor or event data are not available in log streaming actions. Because of this separation, log parameter values must be explicitly promoted to event attributes before they can be mapped to destination fields.

Mapping involves two steps:

1. Create event attributes using enrichments

   Create a string event attribute for each log field you want to send to your destination. Then add a set string enrichment to that attribute with the log parameter as the value, using double curly braces.

   For example, to make the severity level available for mapping:

   • Create a string event attribute named dd_severity.
   • Add a set string enrichment with the value {{severityText}}.

   At delivery time, the enrichment extracts the value from the log record and writes it to the event attribute.

   For the full list of available log parameters, see Connector log parameters.

2. Map event attributes to destination parameters

   In the log source settings, map the event attribute to the appropriate vendor parameter. The available parameters depend on the destination connector you are using.

   For example, in the Datadog Send Log Event log source settings, map the event attribute dd_severity to the Datadog Severity parameter.

Example mapping (Datadog)

The following example shows how to structure attributes for a Datadog destination:

Event attribute	Set string enrichment
dd_tags	account:{{account}},profile:{{profile}},connector:{{connectorType}},action_id:{{customId}},status:{{result.status}},error_code:{{result.failure.code.name}},http_status:{{http.0.response.statusCode}},group_id:{{groupId}}
dd_subject	{{result.failure.code.name}}
dd_content	{{result.failure.error.0.message}}
dd_severity	{{severityText}}

Then map those event attributes to vendor parameters in the log source Settings tab:

Event attribute	Vendor parameter
tealium_connector_errors	DD Source
dd_tags	DD Tags
tealium_server_side	Hostname
tealium_connectors	Service
tealium_timestamp_epoch	Timestamp
dd_subject	Subject
dd_content	Content
dd_severity	Severity

Use the sample payload in the log source view to confirm that the fields you reference exist and contain expected values.

For full parameter definitions, see Connector log parameters.

Verify delivery

After configuring a destination and log source:

• Confirm that logs are arriving in the destination system.
• Validate that fields are mapped correctly.
• Adjust mappings if fields are missing or incorrectly formatted.

In Tealium, use the log streaming dashboard to confirm that logs are being sent successfully.

Monitor log streaming activity

Use the Manage Log Streaming page to monitor delivery performance and manage destinations.

Summary metrics

The summary section shows delivery metrics for the selected time range.

• Total Volume: Number of log events sent
• Retries: Number of retry attempts
• Total Success: Successfully delivered events
• Success after Retry: Events delivered after one or more retries
• Total Errors: Events that failed delivery

These metrics reflect the health of the log delivery pipeline, not connector execution.

A high error count typically indicates issues such as:

• authentication failures
• connectivity issues
• destination configuration errors

Destinations table

The Log Streaming Destinations table lists all configured destinations and their delivery performance.

Each row shows:

• Sources: Number of log sources attached to the destination
• Total Volume / Success / Errors: Delivery metrics for the destination
• Date Modified: When the destination was last updated
• Labels: Labels applied to the destination
• Status: Whether the destination is active

Use this table to identify unusual patterns in volume or errors, then select a destination to investigate further.

View destination details

Select a destination to open its details. Use the following tabs:

• Overview: Delivery trend chart, summary statistics, and basic information (name, notes, UID, labels). Select a time period to filter the statistics and trend chart.
• Log Sources: Log sources attached to this destination, with type, status, and statistics (total volume, successes, and errors) for each. Includes options to duplicate or delete individual sources.
• Settings: Connector configuration (authentication fields, IDs, and connection parameters)

View log source details

Select a log source to open its details. Use the following tabs:

• Overview: Delivery trend chart and summary statistics. Select a time period to filter the statistics.
• Connectors: Connectors and actions monitored by this log source.
• Settings: Attribute mappings and sample payload. To reuse mappings across log sources, see Copy mappings.

Use the sample payload to confirm that the fields you reference in mappings exist and contain expected values.

Copy mappings

Use Copy Mappings to reuse configurations across log sources.

1. Open a log source.
2. Go to the Settings tab.
3. Click Copy Mappings.
4. Select one of the following:
   • Insert Mappings From an Action: Copies mappings from the selected action to the current action.
   • Copy Mappings to an Action: Copies mappings from the current action to the selected action.
5. Choose how to handle conflicts:
   • Keep Original Mappings: Adds new mappings from the source without modifying existing mappings in the destination.
   • Overwrite All Mappings: Replaces all existing mappings in the destination with those from the source action.
6. Apply filters or search to narrow the list of actions, then select the action.
7. Click Done.

If you want to send the same log source to multiple destinations, create the additional destinations, add the log sources, and then use the copy mappings option to duplicate the mappings from one log source to the others.

Related resources

• Connector error logging
<<<<<<< Updated upstream
• Manage enrichments
=======
• About enrichments
>>>>>>> Stashed changes
• About log streaming