Elastic apm tenancy - How it works?

[miguel.longo]

Kibana version: 8.6.2

Elasticsearch version: 8.6.2

APM Server version: 8.6.2

APM Agent language and version: Java elastic-apm-agent.jar:1.43.0

I need help to understand how tenancy works in the elasticsearch, kibana and apm stack.

I started by creating aliases in elasticsearch by filtering for a specific label. Then, I created a role where each role allows access to a specific space in kibana.

In this space, within observability, I edited the APM settings to use the aliases I created. Each space has it's aliases.

Logging in with the user with applied the role in kibana, the segmentation works, the user only sees services, transactions, spans and logs according to the alias filter. However, it cannot list all dependencies related to the alias. If I open a transaction, like a database query, I can see the dependecy in span details and if I open it on discovery, I can see the labels in it.

How can I list the dependencies? What could be wrong?

Below is the applied alias:

POST /_aliases?pretty
{
  "actions": [
    {
      "add": {
        "index": "traces-apm*",
        "alias": "teamA-traces-apm",
        "filter": {
          "term": {
            "labels.team": "teamA"
          }
        }
      }
    },
    {
      "add": {
        "index": "logs-apm*",
        "alias": "teamA-logs-apm",
        "filter": {
          "term": {
            "labels.team": "teamA"
          }
        }
      }
    },
    {
      "add": {
        "index": "metrics-apm*",
        "alias": "teamA-metrics-apm",
        "filter": {
          "term": {
            "labels.team": "teamA"
          }
        }
      }
    }
  ]
}

Thanks guys!