[Infra UI] Allow for passing arbitrary KQL expressions in the entry urls #23316
Labels
Feature:Metrics UI
Metrics UI feature
loe:small
Small Level of Effort
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
By introducing a parameter (e.g.
?filter=...
) that allows passing arbitrary KQL expressions in thelink-to
entry routes (see #23246), other parts of the UI can pre-populate the filter with expressions that the infra ui can not interpret. Examples for that would be APM filtering by a transaction id or an ip address.The KQL expression should be combined using a conjunction with the other filters derived from the parameters (such as the hostname or container id filter). The route
/link-to/host-logs/host1?filter=transaction.id:123
would result in the KQL expression(${CONFIGURED_HOSTNAME_FIELD}:host1) and (transaction.id:123)
being used as the initial filter.The text was updated successfully, but these errors were encountered: