Quickstart

This guide covers your first connection to Cordant. When you finish, at least one observability source will be connected, an alerting integration will be configured, and a Slack channel will receive incident updates.

Estimated time: under 10 minutes for a basic setup. A full stack takes 30 to 60 minutes.

Step 1: Create your workspace

Sign up at trycordant.com/register

Sign up with your work email. Cordant names the workspace after your email domain by default. Rename it later from the workspace settings.

Create an API key

In the dashboard, open Settings > API Keys and create a key with read-write access. Use it for the ingest webhook and integrations managed programmatically. Copy it now because it cannot be viewed again.

Step 2: Connect an observability source

Cordant needs at least one observability source for diagnostic queries during incidents. Begin with the source your team uses most.

Go to Settings > Integrations > Add integration

Choose a source from the catalog. The setup wizard requests its credentials and permission scopes. Follow the instructions for your selected source.

Test the connection

After entering credentials, click Test connection. Cordant performs a read operation to verify permissions. If it fails, the error identifies the missing permission.

Step 3: Connect alerting

Connect PagerDuty or OpsGenie

For PagerDuty, add an inbound integration to your service with Cordant as the event source, then copy its integration key into Cordant. For OpsGenie, create an API integration and copy its API key.

Or use the webhook ingest endpoint

For a custom alerting source, POST alert payloads to the ingest endpoint. See the webhook ingest documentation for its payload schema.

curl -X POST https://api.trycordant.com/v1/ingest/webhook \
  -H "Authorization: Bearer <your_api_key>" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "test",
    "service": "my-service",
    "severity": "low",
    "title": "Test alert from quickstart"
  }'

Successful ingestion returns HTTP 201 and the new incident ID. The incident appears in the dashboard within seconds.

Step 4: Connect Slack

Install the Cordant Slack app

Open Settings > Integrations, choose Slack, click Install to Slack, and authorize the app. Choose an existing channel or create one for incident notifications.

Send a test alert

Open Settings > Integrations > Slack > Send test message. A test incident card should appear in the configured channel within seconds. If not, check the channel configuration and confirm the Cordant app was added to that channel.

Step 5: Configure your first runbook

Open the Runbooks section in the dashboard

Click Create runbook, then enter a name and trigger condition. The simplest trigger matches the service name in incoming alerts. For example, trigger when service == "my-service".

Add a diagnostic step and a notification step

Add a query step for your observability source to retrieve the service's recent error rate. Add a notify step to post the result to Slack. Save and activate the runbook.

You are set up

After you configure an observability source, alerting integration, and runbook, Cordant responds to incoming alerts. The dashboard records every incident it handles, including each diagnostic step and action.

For runbook authoring, action types, and authorization levels, see the Runbooks section in the documentation.