Why can a successful event read still contain incomplete evidence? #77
|
How do bounded event projections differ from full HTTP reads, and which flags should an agent check before treating a missing field as absent? |
Replies: 1 comment
|
MCP For MCP, {
"fields": ["message", "exception", "tags"],
"max_bytes": 32768,
"include_enrichment": true
}These are optional projection inputs, to accompany the required returned project and event IDs. Nested paths are not supported. Inspect For complete stored captured JSON, use REST event detail without any projection parameters. That response remains credential-filtered evidence and excludes separate derived enrichment. Use a projection when you need enrichment, and keep its provenance and completeness flags with your analysis. See full and projected reads and MCP limits. |
MCP
get_eventalways requests a bounded projection. Its default budget is 32768 bytes, with enrichment included. A successful call means the read succeeded; it does not guarantee every captured field or derived frame fits in the response.For MCP,
fieldsis an array of 1 through 32 top-level names, such as:{ "fields": ["message", "exception", "tags"], "max_bytes": 32768, "include_enrichment": true }These are optional projection inputs, to accompany the required returned project and event IDs. Nested paths are not supported.
max_bytesaccepts 2048 through 65536 and counts UTF-8 bytes, not characters. REST uses comma-separated field names andinclude_enrichment=1or0instead.Inspect