Skip to content

Commit b2c306d

Browse files
authored
Remove 'Knowledge connectors' section from documentation
Removed the 'Knowledge connectors' section that described ingesting data from external monitoring platforms. Updated the list of available connectors accordingly.
1 parent a68036f commit b2c306d

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

articles/sre-agent/connectors.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,6 @@ Connectors are modular integrations that extend the SRE Agent's capabilities. Th
1919
| Type | Description | Possible use case |
2020
|--|--|--|
2121
| **Communication connectors** | Send notifications and updates to services like Outlook and Microsoft Teams. | When the SRE Agent detects an incident, it can email stakeholders or post updates in Teams. |
22-
| **Knowledge connectors** | Ingest data from external monitoring platforms such as Datadog, Dynatrace, and New Relic. | During troubleshooting, the agent can query telemetry from Datadog or Dynatrace. |
2322
| **Custom connectors** | Create a custom connection to an MCP server endpoint of your choice. The [Azure MCP Center](https://mcp.azure.com/?types.remote=true) gives you access to various MCP endpoints you can integrate into SRE Agent. | When connected to a custom endpoint, SRE Agent can gain insight into external services like GitHub, Hugging Face, Stripe, and many more. For a full list of cataloged MCP server endpoints, see [Azure MCP Center](https://mcp.azure.com/?types.remote=true).|
2423

2524
## Available connectors
@@ -29,7 +28,6 @@ Azure SRE Agent includes these connectors:
2928
- **Outlook** for sending email notifications.
3029
- **Microsoft Teams** to post messages to Teams channels.
3130
- **Custom MCP Servers** for integration with your own remote MCP server.
32-
- **Approved partners** to ingest telemetry data from Dynatrace, Datadog, and New Relic.
3331

3432
## Configure a connector
3533

0 commit comments

Comments
 (0)