Telemetry with an agent

Use telemetry for aggregated trends and request tools for individual calls. MSP client telemetry is get_msp_client_telemetry and is documented with Partners.

There is no need to create telemetry. Call get_guide with guide_key: "telemetry" before the first query.

Calls

• get_proxy_telemetry requires clientId and proxyId.
• get_credential_telemetry requires clientId and credentialId.
• get_client_telemetry requires clientId and returns one organisation-wide series.
• get_proxies_telemetry requires clientId and returns a separate series for each proxy.

Every tool optionally accepts interval (minute, hour, day, or month), ISO-8601 startDate, ISO-8601 endDate, and limit.

Example

{
  "tool": "get_proxy_telemetry",
  "arguments": {
    "clientId": "b3a1c7d2-5e44-4f0a-9c1e-7d2f8a6b1c90",
    "proxyId": "5d8a1c30-4e72-4b19-8f6a-0c3d9e7b1a25",
    "interval": "hour",
    "startDate": "2026-11-02T00:00:00Z",
    "endDate": "2026-11-03T00:00:00Z"
  }
}

The result contains newest-first telemetry buckets. Use list_proxy_requests with the same time range when a bucket needs call-level investigation.

Next