📘

Service Maps is an Enterprise-only feature

If you are using Datadog, installing CodeSee Service Maps involves:

• Deploying the CodeSee Datadog Bridge docker image between your Datadog Agent(s) and datadoghq.com
• Installing and configuring the @codesee/trace-datadog-rum package in your browser-based frontend

Complete details for both the backend and frontend installations follows:

Backend:

Deploy the CodeSee Datadog Bridge docker image (dd-bridge) in each of your network environments. It is a very simple bridge process which receives Datadog-bound APM traffic (traces + metrics) and forks that traffic to both Datadog and CodeSee.

The dd-bridge docker image is available at https://hub.docker.com/r/codeseeio/dd-bridge. We encourage you to use the latest tag in order to more easily get updates.

docker pull codeseeio/dd-bridge:latest

The dd-bridge image:

• is an x86 image
• listens on port 8080
• needs to have outgoing https network access so it can send data to Datadog (datadoghq.com) and CodeSee (in-datadog.codesee.io)

Deployment architecture

The dd-bridge can be deployed as a daemon along with each Datadog Agent, or on its own instance(s) with all Datadog APM traffic being routed through it.

Or, if you use AWS Lambda with the Datadog Lambda Layer, there is a DD-Bridge Lambda Layer you can use as well.

You may decide to deploy dd-bridge with a load balancer and redundancy if you are concerned about throughput / uptime.

Here are a couple of possible deployments:

Configuration

Datadog Agent / Layer configuration

Note: this is exactly the same for Datadog Agent and AWS Lambda Datadog Layer.

// Ensure tracing and metrics are enabled
DD_APM_ENABLED: true             // turns on tracing and metrics
DD_APM_NON_LOCAL_TRAFFIC: true   // necessary in most environments

// send trace and metric data to CodeSee dd-bridge+
DD_APM_DD_URL: <location of dd-bridge>

// For example, if running dd-bridge locally
DD_APM_DD_URL: http://localhost:8080

CodeSee dd-bridge configuration

CODESEE_BRIDGE_TOKEN: <CodeSee Ingestion Client Key>
CODESEE_BRIDGE_FORWARD_HOST: https://in-datadog.codesee.io

// If you have a private datadog endpoint
CODESEE_BRIDGE_DD_HOST: https://your-private.datadoghq.com

Examples:

ECS task definition examples

Lambda configuration examples

Datadog with Vector

Frontend

Install and configure the @codesee/trace-datadog-rum package in each of your frontend browser codebases. Full details are in the project README.

Example

Update CSPs

If you use Content Security Policies (CSPs) you may need to update them to allow the browser to send trace data to CodeSee at https://in-datadog.codesee.io

connect-src https://in-datadog.codesee.io

Configure allowedTracingUrls

Datadog tracing will only be initiated from the frontend when making requests to allowed tracing urls. These urls must be configured, or no traces will be recorded. Follow the Datadog Rum instructions to configure the allowedTracingUrls initialization parameter.