Skip to content

OpenTrace

Connect OpenTrace so OpsPilot can read your code alongside your telemetry.

OpsPilot knows what your systems are doing. OpenTrace knows what your code is: what calls what, who owns a file, and what changed in which pull request. Connect your OpenTrace account and OpsPilot can use both when it answers you, so a question about a service that started erroring can reach the change that touched it.

Navigate to Integrations from the left-hand sidebar, then select OpenTrace.

What it adds

With OpenTrace connected, OpsPilot can draw on your code as well as your telemetry when it answers you:

  • What calls what - the relationships between your services and components
  • Who owns a file - who to ask, or who to tell
  • What changed in which pull request - the change history behind the code

That means a question about a service that has started erroring can reach the change that touched it, rather than stopping at the symptom.

Your own account

You connect your own OpenTrace account, and OpsPilot uses it only in your conversations. Each person connects their own account - it isn't shared across the organisation.

Connect yours from Integrations → User MCPs, where OpenTrace appears under Data with a Connect button. The agent uses that connection only in chat, never in scheduled work and never on anyone else's behalf.

Permission tiers

OpenTrace runs Read-only, which is the default and the only tier. It requires nothing to enable.

OpenTrace declares no capabilities, so it doesn't provision dashboards or alerts of its own - it adds context to the answers OpsPilot gives you.

Installing

Click Install on the OpenTrace card in the integration catalog, or from the integration's detail view. The install dialog confirms which account the install will serve and shows the permission tier. Click Install to confirm.

Need more help?

Contact support in the chat bubble and let us know how we can assist.