Versions
Kibana: 7.8.1
APM Server: 7.8.1
Elasticsearch: 7.8.1
We have a shared APM deployment for all developer environments (each dev env is network isolated from the other), but I'm seeing the top level service map showing services from other people's environments (me and @lloydmeta here).
If I click on a single service first, then bring up the map I don't see this behavior. Just a lone service which I think is expected at this stage since we haven't worked out trace linking just yet.
The deployment houses data from a large number of developer setups with a variety agent of versions (mostly 1.17, but maybe 1.8 or 1.18 as well).
We may have some here from when they were all just "environment:dev" as well.
cc @ogupte and @henrikno who I chatted with about this on slack
Versions
Kibana: 7.8.1
APM Server: 7.8.1
Elasticsearch: 7.8.1
We have a shared APM deployment for all developer environments (each dev env is network isolated from the other), but I'm seeing the top level service map showing services from other people's environments (me and @lloydmeta here).
If I click on a single service first, then bring up the map I don't see this behavior. Just a lone service which I think is expected at this stage since we haven't worked out trace linking just yet.
The deployment houses data from a large number of developer setups with a variety agent of versions (mostly 1.17, but maybe 1.8 or 1.18 as well).
We may have some here from when they were all just "environment:dev" as well.
cc @ogupte and @henrikno who I chatted with about this on slack