--- title: "[Contentstack Launch] - Log Targets" description: Create and manage Log Targets in Contentstack Launch to forward server and edge logs to third-party monitoring services via OpenTelemetry. url: https://www.contentstack.com/docs/developers/launch/log-targets product: Contentstack Launch doc_type: how-to-guide audience: - developers - devops - platform-engineers version: current last_updated: 2026-03-25 --- # [Contentstack Launch] - Log Targets This page explains how to use the Log Target feature in Contentstack Launch to forward server and edge logs from Launch-hosted SSR websites, Cloud Functions, or Edge Functions to third-party monitoring services via OpenTelemetry. It is intended for developers and operators setting up observability integrations and should be used when configuring, verifying, enabling, editing, or deleting log forwarding endpoints. ## Log Targets The Log Target feature in Contentstack Launch enables you to forward server and edge logs generated by Launch-hosted SSR websites, Cloud Functions, or Edge Functions to third-party monitoring services. You can set up an OpenTelemetry Collector service to receive logs through a TLS-secured OTLP (OpenTelemetry Protocol) over gRPC/HTTP endpoint and forward them to your preferred log provider. OpenTelemetry is an industry-standard framework that simplifies integration with major log provider platforms, ensuring seamless implementation. **Additional Resources:** - Learn more about hosting an OpenTelemetry(OTEL) Collector service in the [OpenTelemetry Documentation](https://opentelemetry.io/). - Refer to [Host a Launch OTEL Collector Service exporting logs to AWS Cloudwatch](https://github.com/contentstack-launch-examples/launch-cloudwatch-otel-collector) to configure OTEL Collector service. **Tip**: You do not need to host your own OpenTelemetry Collector service if your log aggregator platform already supports ingesting logs in OpenTelemetry format over a gRPC/HTTP endpoint. With this feature, the generated server and edge logs can be integrated with external monitoring tools, providing insights, alerts, and persistent data storage for better management and analysis of log data. **Note**: Logs are forwarded exactly as generated by your application. We do not modify, filter, or mask log content. If your logs contain sensitive information, ensure it is masked or removed at the source before export. This step-by-step guide lets you create Log Targets in Contentstack Launch to forward your project logs to specific endpoints. ## Prerequisites - [Contentstack account](https://www.contentstack.com/login/) - Access to Launch for your organization - OTEL Collector service capable of receiving logs configured with TLS-secured gRPC/HTTP Endpoint ## Steps for Execution ### Create a Log Target Follow the steps below to create a Log Target: - [Log in to Contentstack](https://www.contentstack.com/login/) and click the **Launch** app. - Click the **Settings** icon to enter the **Log Targets** page. - Click the **+ Set up Log Target** button to create a new Log Target. - In the modal that appears, enter the following:**Log Target Name**: A name for the 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. - **Authentication Headers**: Headers required by your provider. - **Payload Format**: The data format (JSON or Protobuf) used to send logs to your provider.**Note**: This option is only for HTTP. If you have selected gRPC as the protocol, the payload format is always Protobuf. - Click the **Continue Setup** button. - 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, it is created in a disabled state. To enable the Log Target, you must verify it by testing the connection. - Once verification is successful, click the **Enable Log Target** button to enable the Log Target and start forwarding logs. ### Edit a Log Target Follow the steps below to edit a Log Target: - Click the **Settings** icon to enter the **Log Targets** page. - Against the Log Target that you want to edit, click the **ellipses** under **Actions**, and then click **Edit**. - Edit the Log Target details as required and then click the **Save Changes** button to save the updated details. The Log Target is updated while in a disabled state. ### Enable Log Target To enable the Log Target, follow these steps: - Click the **toggle** next to the Log Target you want to enable. - After verifying all the details, click the **Test Connection** button on the **Verify Log Target Connection** modal. - 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. ### Verify the Connection To verify the Log Target and test the connection, follow these steps: - Click the **Settings** icon to open the **Log Targets** page. - Next to the Log Target you want to verify, click the **vertical ellipses** under **Actions**, then select **Verify Connection**. - 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. **Note**: To verify the connection to your endpoint, Launch sends a test log that may be visible in your observability tool. ### Delete a Log Target Follow the steps below to delete a Log Target: - Click the **Settings** icon to enter the **Log Targets** page. - Against the Log Target that you want to delete, click the **ellipses** under **Actions**, and then click **Delete**. - In the modal that appears, click the **Yes, Delete** button to delete the Log Target. **Additional Resources**: Use this [GitHub repository](https://github.com/contentstack-launch-examples/launch-cloudwatch-otel-collector) as an example to set up a TLS-secured OTLP/gRPC endpoint that receives and exports logs to CloudWatch. ## Limitation - Launch can forward only up to **1000 logs** in a single request. ## Common questions ### Do I need to host my own OpenTelemetry Collector service? No. **Tip**: You do not need to host your own OpenTelemetry Collector service if your log aggregator platform already supports ingesting logs in OpenTelemetry format over a gRPC/HTTP endpoint. ### What happens if I save a Log Target without testing it? If you save the Log Target without testing it first, it is created in a disabled state. To enable the Log Target, you must verify it by testing the connection. ### Does Launch modify, filter, or mask logs before forwarding? No. **Note**: Logs are forwarded exactly as generated by your application. We do not modify, filter, or mask log content. ### How many logs can Launch forward in a single request? Launch can forward only up to **1000 logs** in a single request.