{"version":"2.1.224","anchor":"mcp-events-forwarded-to-datadog-with-identifying-fields-remo","canonical_anchor":"mcp-events-forwarded-to-datadog-with-identifying-fields-remo","heading":"MCP events forwarded to Datadog, with identifying fields removed and a per-server cap","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/mcp-events-forwarded-to-datadog-with-identifying-fields-remo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### MCP events forwarded to Datadog, with identifying fields removed and a per-server cap\n\nMCP events are forwarded for logging with identifying fields stripped, and skipped entirely if analytics are off.\n\n**What**\n\nMCP events are now admitted to log forwarding, and every payload has its identifying fields deleted before send. Forwarding is skipped entirely when analytics are disabled.\n\n**Details**\n\n- Newly allowed: `tengu_mcp_degraded`, `tengu_mcp_list_changed`, `tengu_mcp_listen_reopen`, `tengu_mcp_sdk_generation`, `tengu_mcp_server_connection_failed`, `tengu_mcp_server_connection_succeeded`, `tengu_mcp_tripwire`.\n- Stripped fields include the server name, base URL, hashed server key, attribution hashes, hashed error details and a server digest.\n- Five of the MCP events are capped per event-and-server pair at 10 per 60 seconds, tracked over at most 200 keys; the number of suppressed events rides along on the next one that gets through as `droppedSinceLastForward`.\n\n**Evidence**\n\n`PEER_RATE_BOUND_EVENTS`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}