The Log Target feature in Contentstack Launch enables you to forward logs to third-party monitoring services.

Logs flow through the following path:

Your App → Launch Edge/Server → Log Target → Your Observability Provider

When you create a Log Target, you choose which type of logs to forward:

• Server Logs: Runtime output from your SSR Applications, Cloud Functions, and Edge Functions.
• Traffic Logs: Request/response metadata from the CDN edge.

You can forward one or both data types per Log Target. This lets you control what each monitoring destination receives.

1. Server Logs: Logs exactly as generated by your SSR Applications, Cloud Functions, and Edge Functions.
2. Traffic logs: Traffic Logs include request/response metadata processed at the CDN edge. Each log entry contains the following fields:

NoteServer Logs are forwarded exactly as generated by your application. Launch does not modify, filter, or mask log content. If your logs contain sensitive information, ensure it is masked or removed at the source before export.

• Track 1: Your provider already supports OTLP natively (Datadog, New Relic, Honeycomb, etc.) → No collector needed, just use your provider's endpoint and API key.
• Track 2: Your provider doesn't support OTLP (Splunk, custom setup, etc.) → You need to self-host an OTEL Collector.

Note The endpoint URLs and header details listed above are based on each provider's documentation at the time of writing. These may change over time — refer to your provider's official documentation for the most up-to-date configuration details.

Launch automatically sets a unique service.name OTLP resource attribute on every log entry to identify its source environment:

• Server Logs: launch-<environmentUid>
• Traffic Logs: launch-traffic-<environmentUid>

Use this field to filter and separate logs by environment inside your observability provider. For example, filtering by service name in Axiom, Datadog, New Relic, or Honeycomb. This is especially useful when sending logs from multiple environments to a single destination.

This step-by-step guide lets you create Log Targets in Contentstack Launch to forward your project logs to specific endpoints.

1. Contentstack account
2. Access to Launch for your organization
3. OTEL Collector service capable of receiving logs configured with TLS-secured gRPC/HTTP Endpoint

To create a Log Target, log in to Contentstack account and follow the steps:

1. Go to the “App Switcher” icon in the top-right corner and click Launch.
2. Click the Settings icon and navigate to the Log Targets page.
   Click to enlarge
3. Click the Create Log Target button to create a new Log Target.
   Click to enlarge
4. In the modal that appears, enter the following:
   • Log Target Name: A name for the Log Target.
   • Data Type: Select one or both log types that the Log Target should forward. At least one is required:
     • Server Logs: Runtime output from SSR Applications, Cloud Functions, and Edge Functions.
     • Traffic Logs: Request/response metadata from the CDN edge.
   • Send Logs For: Select the Launch projects and environments that should send logs to this Log Target. You have two options:
     • All Projects & Environments: Sends logs from all current and future Launch projects and environments in your organization.
       Click to enlarge

       Only one Log Target can forward each data type organization-wide. The valid setups are:

       • One Log Target forwarding both Server Logs and Traffic Logs.
       • Two Log Targets with one forwarding Server Logs and one forwarding Traffic Logs.
     • Custom: To configure a Log Target for specific projects and environments, select the Custom option. Select your Projects and Environments from the respective dropdowns, then click Apply to configure the settings. Also, click + Add another project to add another set of projects and environments.
       Click to enlarge

       Uniqueness rule

       Each environment and data type combination can be covered by only one Log Target. The same environment can send logs to multiple Log Targets, as long as each uses a different data type.

       Examples:

       • Target A covers env1 with Server Logs, and Target B covers env1 with Traffic Logs. This is allowed because both targets use the same environment but different data types.
       • Target A covers env1 with Server Logs, and Target B covers env1 with Server Logs. This is blocked because the same environment and data type are already covered by another Log Target.
       • Target A covers env1 with Server Logs, and Target B covers env2 with Server Logs. This is allowed because both targets use the same data type but different environments.
       • A Log Target scoped to All Projects & Environments with Server Logs covers Server Logs across every environment. This means no other Log Target can use Server Logs for any environment while this Log Target exists.

       Note If existing Log Targets cover environments for a selected data type, the system disables the All Projects & Environments option for that data type when creating or editing a Log Target.

   • Delivery Protocol: A protocol (gRPC or HTTP) used to forward logs to the required endpoint.
   • Endpoint URL: The OpenTelemetry OTLP/gRPC/HTTP endpoint where logs are transmitted.

     Note For gRPC, do not include http:// or https:// prefix. For HTTP, the URL must begin with https:// and end with /v1/logs.

   • Authentication & Headers: Headers required by your provider.

     Example: Header name x-honeycomb-team, value your-api-key.

   • Payload Format: The data format (JSON or Protobuf) used to send logs to your provider.

     Note The JSON option is only for HTTP. If you have selected gRPC as the protocol, the payload format is always Protobuf.

     Click to enlarge
5. Click the Continue Setup button.
6. In the modal that appears, perform one of the following:
   • Verify the details and click the Test Connection button.
     If the test is successful, the Log Target is created and configured to forward your project logs to the specified Endpoint URL. If the test fails, an error message appears. You can return to editing and update the Log Target configuration.
   • Click the Save Log Target button to save and verify later.
     If you save the Log Target without testing it first, the system saves it in a disabled state. To enable the Log Target, you must verify it by testing the connection.
     Click to enlarge
7. Once verification is successful, click the Enable Log Target button to enable the Log Target and start forwarding logs.
   Click to enlarge

Follow the steps below to edit a Log Target:

1. Click the Settings icon and navigate to the Log Targets page.
2. To edit a Log Target, click the vertical ellipses under Actions, and then select Edit.
   Click to enlarge
3. Edit the Log Target details as required and then click the Save Changes button to save the updated details.

   Note You can change the Data Type during editing. The change is subject to the same environment and data type uniqueness rule. If the selected data type is already covered by another Log Target, including All Projects & Environments Log Targets, the system blocks the change.

   Click to enlarge

The Log Target is updated while in a disabled state.

To enable the Log Target, follow these steps:

1. Click the toggle next to the Log Target you want to enable.
   Click to enlarge
2. After verifying all the details, click the Test Connection button on the Verify Log Target Connection modal.
   Click to enlarge
3. Once the connection is successfully verified, click the Enable Log Target button.

The Log Target is now enabled and ready to forward logs to your provider.

To verify the Log Target and test the connection, follow these steps:

1. Click the Settings icon and navigate to the Log Targets page.
2. Next to the Log Target you want to verify, click the vertical ellipses under Actions, then select Verify Connection.
   Click to enlarge
3. Verify the details, and click the Test Connection button in the Verify Log Target Connection modal.

This confirms whether your Log Target is ready to receive logs.

NoteTo verify the connection to your endpoint, Launch sends a test log that may be visible in your observability tool.

Follow the steps below to delete a Log Target:

1. Click the Settings icon and navigate to the Log Targets page.
2. To delete the Log Target, click the vertical ellipses under Actions, and then click Delete.
   Click to enlarge
3. In the modal that appears, click the Yes, Delete button to delete the Log Target.
   Click to enlarge

Additional ResourcesUse this GitHub repository as an example to set up a TLS-secured OTLP/gRPC endpoint that receives and exports logs to CloudWatch.

• You can create a specific number of Log targets. If you want to raise the limit, contact Contentstack support.
• Launch can forward only up to 1000 logs in a single request.
• Launch supports a log line size of up to 64 KB per line.
• Launch supports a total log size of up to 1 MB per request.