However, we do NOT have an equivalent place to store connector information. Ideally, we'd be storing the rule id, space ids, name at a minimum. This would allow us to search over these fields. Today, you can do some unwieldy searches over connectors via the kibana.saved_objects nested fields, but runtime field access can get slow, especially when filtering fields (checking every document); and having the name available for alerting rules has ended up working out well for diagnostics:
We have the luxury of ECS's
rule
property to fill in details about alerting rules:https://github.com/elastic/kibana/blob/6a61c43f06a87936f68dbc357bb6f5be06e5dbe3/x-pack/plugins/event_log/generated/mappings.json#L173-L219
However, we do NOT have an equivalent place to store connector information. Ideally, we'd be storing the rule id, space ids, name at a minimum. This would allow us to search over these fields. Today, you can do some unwieldy searches over connectors via the
kibana.saved_objects
nested fields, but runtime field access can get slow, especially when filtering fields (checking every document); and having thename
available for alerting rules has ended up working out well for diagnostics:https://github.com/elastic/kibana/blob/6e3af2b5240532faf4a29edc0d1769d87bd43957/x-pack/plugins/event_log/generated/mappings.json#L270-L294