search

openshift / origin-metrics

79 stars 113 forks source link

Access metrics from Hawkular-cassandra pod #426

Closed abhaynayak24 closed 4 years ago

abhaynayak24 commented 6 years ago

I entered the following command by providing my own certificate along with the rest of arguments discussed.

curl --insecure --cacert ca.crt -H "Authorization: Bearer 2XwxlTO_ls_HqpwTe5OWhGwuTu5qEzFxVGIhe761V7A" -H "Hawkular-Tenant: openshift-infra" -X GET https://hawkular-metrics.example.com/hawkular/metrics/metrics

and I got the expected output which is the metadata about all kinds of metrics, However, I tried to fetch the exact data using the following command as discussed in the openshift docs

curl --insecure --cacert ca.crt -H "Authorization: Bearer 2XwxlTO_ls_HqpwTe5OWhGwuTu5qEzFxVGIhe761V7A" -H "Hawkular-Tenant: openshift-infra" -X GET https://hawkular-metrics.example.com/hawkular/metrics/counter/data?tags=descrpitor_name:cpu/usage,pod_name:hawkular-cassandra

But its unable to fetch any data with the following error

"errorMsg":"RESTEASY003210: Could not find resource for full path: https://hawkular-metrics.example.com/hawkular/metrics/counter"

Am I doing something wrong here? because I followed the exact same format as discussed in the thread and yet I'm not able to generate similar outputs

openshift-bot commented 4 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 4 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 4 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 4 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/origin-metrics/issues/426#issuecomment-715328181): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.