Description of problem: The "thanos-querier" somehow rewrites the "cluster"-field with the name of the Openshift-cluster, as opposed to when doing the exact same query but on the "prometheus" API endpoint Version-Release number of selected component (if applicable): 4.9 How reproducible: Customer is able to reproduce at will. Steps to Reproduce: Thanos-querier API endpoint : $ curl --noproxy "*" -sLk --data-urlencode "query=opensearch_cluster_nodes_number" -H "Authorization: Bearer xxxx" "https://thanos-querier-openshift-monitoring.apps.smals-75.paas.acc.cloud.smals.be/api/v1/query" | jq-win64.exe ... { "status": "success", "data": { "resultType": "vector", "result": [ { "metric": { "__name__": "opensearch_cluster_nodes_number", "cluster": "smals-75", "container": "opensearch", "endpoint": "http", ... Prometheus API endpoint : $ curl --noproxy "*" -sLk --data-urlencode "query=opensearch_cluster_nodes_number" -H "Authorization: Bearer xxxx" "https://prometheus-k8s-openshift-monitoring.apps.smals-75.paas.acc.cloud.smals.be/api/v1/query" | jq-win64.exe ... { "status": "success", "data": { "resultType": "vector", "result": [ { "metric": { "__name__": "opensearch_cluster_nodes_number", "cluster": "opensearch-test", "container": "opensearch", "endpoint": "http", Actual results: Expected results: Additional info:
Can you provide a Mustgather otherwise it might be difficult for uns to exactly understand what might be happening
Actually, Thanos querier is working as expected because it will always include the external labels from Prometheus. Not sure how much of an annoyance it is for the customer but maybe we can improve our documentation to illustrate better the differences between Thanos and Prometheus APIs.
apologies case is now linked, the must-gather is attached to the case
Hello Joao, >Actually, Thanos querier is working as expected because it will always include the external labels from Prometheus. Not sure how much of an annoyance it is for the customer but maybe we can improve our > >documentation to illustrate better the differences between Thanos and Prometheus APIs. Initially I thought this was the case - documentation bug rather than a code bug. do we have it documented anywhere that this is the expected behaviour? Thanks
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira. https://issues.redhat.com/browse/OCPBUGS-9450