How do status, time, text, and tag filters combine? #75
|
When a search combines environment, tags, and time bounds, can different occurrences satisfy different parts of the query? Are MCP and HTTP filters identical? |
Replies: 1 comment
|
All event predicates must match the same event. An issue with one production occurrence and a different development occurrence carrying Common MCP filters are Use explicit UTC RFC3339 bounds with The interfaces differ. MCP See HTTP filters and MCP inputs. |
All event predicates must match the same event. An issue with one production occurrence and a different development occurrence carrying
region=eudoes not match a production-plus-region query unless a single occurrence satisfies both conditions. Time, release, level, and other event predicates follow the same rule.Common MCP filters are
q,environment,release,level,from,to, andtags. Environment, release, and level are exact stored-value matches. MCP tags use an object such as{"region":"eu"}; REST uses query parameters such astag.region=eu. Both support up to 16 tag predicates.Use explicit UTC RFC3339 bounds with
Zor+00:00.fromis inclusive andtois exclusive. URL-encode query…