You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm using Thanos Ruler and trying to add a an API based query url to its configuration.
Referring from the Thanos Official docs of building Thanos Ruler (https://thanos.io/tip/components/rule.md/#query-api), we configured the oauth based token access via a Configmap in the below format.
As per our requirement, we were able to fetch the Bearer Token and add to this configmap after every scheduled interval.
Thanos Ruler tries to reach the querier but always returned with response:
"no query API server reachable".
Can anyone pls explain me where I'm doing it wrong. Also it would be great, if you can provide some sample configurations to refer to.
The text was updated successfully, but these errors were encountered:
Hello 👋 Looks like there was no activity on this issue for the last two months. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.
Hi,
I'm using Thanos Ruler and trying to add a an API based query url to its configuration.
Referring from the Thanos Official docs of building Thanos Ruler (https://thanos.io/tip/components/rule.md/#query-api), we configured the oauth based token access via a Configmap in the below format.
As per our requirement, we were able to fetch the Bearer Token and add to this configmap after every scheduled interval.
Thanos Ruler tries to reach the querier but always returned with response:
"no query API server reachable".
Can anyone pls explain me where I'm doing it wrong. Also it would be great, if you can provide some sample configurations to refer to.
The text was updated successfully, but these errors were encountered: