Technology
GitHub Copilot
Enhance your AI coding assistant by connecting Copilot to your data on Dash0.
Overview
GitHub Copilot
GitHub Copilot is an autonomous coding agent for VS Code, capable of creating/editing files, running tests and commands, using the browser, and more. With support to MCP server, Copilot can access your telemetry data on Dash0 to enhance its coding capabilities.
Use Cases
- Telemetry-aware coding: Copilot can identify issues and performance bottlenecks in your cloud infrastructure and address them directly in the codebase.
- Incident-to-code correlation: Copilot can analyze your application code and latest commits and correlate them with logs, traces and metrics to provide deeper root-cause analysis.
Setup
Overview
GitHub Copilot can be connected to Dash0 using our remote MCP server, allowing it to get context about your telemetry data, navigate and analyze it, while leveraging the same capabilities that human users have access to in the UI.
Authentication
The Dash0 MCP server supports two authentication methods:
- OAuth 2.0 (recommended) — browser-based consent on first connection, no static token to manage. Access tokens refresh automatically every 15 minutes.
- Auth token (Bearer) — best for CI/CD pipelines, scripts, and headless environments where browser-based consent is impractical.
For more details on token lifecycle, audit logs, and revocation, see the Dash0 MCP Server integration.
Configure
-
On VS Code, click on
File>Preferences>Settingsand search forMCP. Make sure that the settingChat > MCPis enabled:
Depending on your type of Copilot subscription, this setting may need to be enabled by the organization administrator on GitHub.
Option 1: OAuth 2.0 (Recommended)
-
Add the following configuration to the file
~/.config/code/User/settings.jsonand save it:json{ "mcp": { "servers": { "dash0": { "command": "npx", "args": ["-y", "mcp-remote", "{{endpoint_mcp}}"] } } } } -
On first use,
mcp-remoteopens a browser window where you log in to Dash0 and grant consent. You can review and revoke connected applications under User Settings → Applications in Dash0. -
To confirm that the Dash0 MCP server has been configured: Open the Copilot panel on
Agentmode, then click on the icon toConfigure Tools...and scroll down to see the tools for the Dash0 MCP server:
Option 2: Auth Token
Before configuring the Dash0 MCP server with a Bearer token, create an auth token with the correct permissions:
- Go to your organization's Auth Tokens settings page
- Create a new auth token with one of the following permission levels:
- Full access (
*) - Recommended for full MCP functionality - Read-only (
*:read) - For read-only access to your telemetry data
- Full access (
Tokens with limited permissions (e.g., scoped to specific datasets or with only "Ingesting" permissions) will not work with the MCP server. The MCP server requires organization-wide read access to query your telemetry data.
Then add the configuration with the Authorization header:
{
"mcp": {
"servers": {
"dash0": {
"command": "npx",
"args": ["-y", "mcp-remote", "{{endpoint_mcp}}", "--header", "Authorization: Bearer {{token}}"],
"env": {
"DASH0_AUTH_TOKEN": "{{token}}"
}
}
}
}
}