TEAM WORKSPACE
DEMO REPLAY

Restart the workspace demo?

This clears teams, service maps, alerts, incidents, conversations, and terminal history for everyone in this workspace. Sign-in, early-access approvals, saved source connections, and usage accounting stay in place. A server backup is made first.
TEAM WORKSPACE

Create a team workspace

Name the team first. Source access and scope come next.
RELATIONSHIP REVIEW

Add relationship

Owner-reviewed links are starting context, not observed runtime traffic.
NEW INVESTIGATION

What is happening?

Service notebooks

START WITH YOUR SERVICE

You choose the sources.
Meld puts the context together.

Connect the code and telemetry that matter. Build a draft with Meld, refine it together, and publish when it’s ready.

  1. 01
    Name your service

    Give the notebook a name and environment.

  2. 02
    Choose its sources

    Datadog and GitHub first. AWS is optional.

  3. 03
    Build, review, publish

    A useful starting point that you control.

Your notebooks

DIRECT THE SHARED INVESTIGATION

Send a direction to the Room

Review this text before sending. The team and Meld will see only the direction below; your private conversation stays here.
REVIEW BEFORE SHARING

Share a finding with the Room

Your conversation stays private. Only this claim, uncertainty, and selected terminal excerpts become visible to the team and Meld.

NEW INVESTIGATION

What’s happening?

Choose a discovered service. Meld freezes its current source context when the investigation starts.
FULL HISTORY

Investigation record

Every observation, direction, review and decision.

Recovery criteria

Applies to this incident and future incidents for the same team, service and environment. Checks use bounded samples, not all traffic.

Record an external change

Meld does not apply changes. Record what your team did and when, so recovery checks use evidence after the change.
STEP 1 OF 4

Create a service notebook

Start with the service. You’ll choose its sources next.
ATTACH A SOURCE
WORKSPACE CONNECTION

Connect Datadog

Connect your organization here. You’ll select the service and environment in each notebook.

Create the keys in Datadog Organization Settings. Use an application key with only the read permissions Meld needs for logs, APM and metrics, preferably owned by a service account. Meld checks actual access when you attach a service.

This local prototype stores credentials in a private server-side file. Replacing this workspace connection affects every attached notebook. It does not change your deployed telemetry agents.
READY FOR INVESTIGATIONS

Publish this notebook?

New investigations can start from this version. Review known gaps so responders understand its limits. Gaps do not all need to be closed before publishing. Published text stays fixed; later changes use a new revision.
PROPOSED BY MELD

Review changes

Before

Proposed
SERVICE MAP · OWNER REVIEW

What should Meld know before the first check?

Connected source pointers are shown automatically. Add only durable service meaning; Meld verifies live state during each incident. Leave unknowns blank and record important gaps.
INVESTIGATE TOGETHER

Share with Meld

The command, output and connected reads will become cited evidence in the conversation. Your note directs Meld’s next step.



TERMINAL REFERENCE
Select output


Connect Datadog alerts
Create an authenticated endpoint for your Datadog organization.