Requirement

Implement a filtering method based on tags for the SPM ui. This issue has been previously raised in #5438 (and later in #7521)

We would love to see data per environment but as of now, there's no option to do it in the UI, thus forcing us to have two separate instances to see the different data.

Problem

Having to do duplicate instances for filtering data in the UI.

Proposal

• Add a tags field to the API endpoint.
• Add a tags field to the BaseQueryParameters struct
• Add support for Prometheus. This requires modifying the query generation logic to inject a label selector into the PromQL queries. For example, a filter for env=prod would add {..., environment="prod"} to the query sent to Prometheus.
  For this part, please read the dimension related details inside spanmetrics connector. We may need to somehow add tags dimension to the spanmetrics configuration for prometheus to filter data precisely.
• Add support for Elasticsearch/OpenSearch. This involves updating the query builder (specifically, the buildBoolQuery method) to include a new filter clause in the search query. This clause will ensure that only documents containing the specified tags are returned from Elasticsearch.

Note for ES/OS: we need a nested field that may look like this :

{

          "nested": {
            "path": "tags",
            "query": {
              "bool": {
                "must": [
                  {"term": {"tags.key": "..."}},
                  {"term": {"tags.value": "..."}}]}}}},

)

We can reuse the function that created a nested ES query

Open questions

This issue is open to anyone, feel free to work on it.