[APM] Service Groups Beta: Dynamic Refresh

[sorenlouv]

Related: https://github.com/elastic/kibana/issues/128623 Depends on: https://github.com/elastic/apm-server/issues/8139

Problem In 8.2 we released a POC of Service Groups. This persists the selected services in the group at group creation time. This means that any new services matching the service group filter will not be included in the group, until the end user edits the group.

Solution

Instead of persisting the selected service in the group, we want to apply the given filter at runtime. No additional design is needed to accomplish this but the user behaviour will be different.

Consequences of this change

• There will no longer be a limit on the number of services in a group
• Users will be restricted to filtering by dimensions available in metric documents
• Computing the service count for a group will happen at runtime and thus incur a performance penalty
• When selecting a group only the services with data for the selected time range will be displayed

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[chrisdistasio]

Reached agreement in Aug 25 meeting with @Mpdreamz , @sqren , @dannycroft , @alex-fedotyev , @simitt on the following 8.5 scope for beta release:

• will proceed with saved query approach
• query is only possible on a limited set of fields/dimensions that support txn metrics (Agent.name, Service.name, Service.language.name, Service.environment, Labels.<xyz>) to begin