Skip to content

Connections

The Connections page shows all the tool integrations configured for your organization. Each connection links NeuBird to an external service — such as AWS, Datadog, Grafana, PagerDuty, or Kubernetes — so the agent can pull telemetry data, query logs, and investigate incidents across your stack.

Connections page showing integration cards in a grid layout

Connections are displayed as cards in a grid. Each card shows the connection name, the service type (e.g. AWS, GRAFANA, SPLUNK), a status indicator, and a colored accent bar at the bottom. A green Active dot means the connection is healthy; a red Error dot means credentials may need attention.

To add a new integration:

  1. Click the Add Connection tile (the dashed-border card with the + icon).
  2. A dialog titled New Connection appears with a grid of available services. You can browse the full list or use the Search connections… field at the top to filter by name.
  3. Click the service you want to connect (e.g. AWS, Datadog, Grafana, Kubernetes).

New Connection dialog showing a searchable grid of available service types

  1. The dialog advances to the credentials form. Fill in the required fields:
    • Connection Name — a friendly label (auto-populated with the service name, e.g. “Datadog Connection”).
    • Description — an optional note about what this connection is for.
    • Service-specific credential fields (marked with a red asterisk when required). Sensitive fields like tokens and secrets are masked by default; click the eye icon to reveal them.
  2. Some services offer multiple authentication modes (e.g. token-based vs. role-based). If available, tabs appear above the credential fields — select the mode that matches your setup.
  3. For fields that support auto-discovery (such as selecting a repository or account), click the Load button to fetch available options from the service after entering your credentials.
  4. Click View setup guide below the dialog title to open a step-by-step help panel for the selected service.
  5. Click Create Connection to save. On success, a confirmation screen appears with the connection name and a green checkmark.
  6. Click Done to close, or Add Another to create additional connections.
  • Edit a connection — Click any connection card to reopen the dialog in edit mode. You can update the name, description, or credentials, then click Save Changes.
  • Delete a connection — Click the three-dot menu (vertical dots) on a connection card and select Delete. A confirmation prompt appears; this action cannot be undone.
  • Check status — The status indicator on each card (green Active or red Error) tells you whether the connection is working. If you see an error, click the card to review and update credentials.
  • Refresh — Click the three-dot menu and select Refresh to re-check the connection state.

On the Connections page, select Edit from the connection’s dropdown menu to open the edit view, which has two tabs:

  • Details — view and update the connection name, description, and credentials. An edit will fail if the updated credentials can’t reach the customer environment.
  • Telemetry — change which telemetry types (logs, metrics, alerts, traces) are enabled or blocked for the connection. Changes apply to all projects using this connection.

After making changes, click Save in the top-right corner.

ConnectionTelemetry Supported
AWS (Amazon Web Services)Logs, Alerts, Metrics, Config
Microsoft AzureAlerts, Metrics, Config, Logs
ServiceNowAlerts
ElasticAlerts, Logs
PrometheusMetrics
OpenSearchLogs
IBM Cloud LogsLogs
DSLLogs
Snowflake Data CloudLogs
GrafanaLogs, Metrics
KloudFuseLogs, Metrics
Google CloudLogs, Metrics, Config
Slack
FireHydrantAlerts
Incident.ioAlerts
InfluxDBMetrics
DynatraceAlerts, Metrics, Traces, Logs
PagerDutyAlerts
GitHubConfig
DatadogAlerts, Metrics, Traces, Logs
Azure DevOpsConfig
SplunkLogs, Alerts
SignalFXMetrics, Alerts

For customers with private telemetry sources, you must allowlist the following IP address so that NeuBird can communicate with your endpoints:

Note: Please ensure that your firewall and network policies allow inbound and outbound traffic to the IP address 54.236.215.157.