Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prometheus 2.2.1 Getting Error in query_range #4197

Closed
abhi11 opened this Issue May 25, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@abhi11
Copy link

abhi11 commented May 25, 2018

I get error when I run the following.

curl -i http://10.182.11.105:9090/api/v1/query_range?query=up&start=1527199200&end=1527199500&step=15s

I am running this on a linux machine.
I get the following error. I have also used the rfc3339 format but that shows the same error.

{"status":"error","errorType":"bad_data","error":"cannot parse \"\" to a valid timestamp"}
@hoffie

This comment has been minimized.

Copy link

hoffie commented May 26, 2018

This seems to be the error message which is printed when no start or end parameters are seen by Prometheus at all. Can you confirm that curl sends the proper request by adding -v?

When running your example verbatim in bash, the shell will interpret the & signs and will fork the call.
When escaping the URL, your example works for me in bash:

curl -i 'http://10.182.11.105:9090/api/v1/query_range?query=up&start=1527199200&end=1527199500&step=15s'
@krasi-georgiev

This comment has been minimized.

Copy link
Member

krasi-georgiev commented May 27, 2018

This is a question for the users group 👍
https://groups.google.com/forum/#!forum/prometheus-users
The developers here are busy solving bugs 🐞

I would recommend looking through the official docs and examples as well as searching in the google groups as there is a good chance that you will find the answer immediately.
https://prometheus.io/docs/introduction/overview/

@abhi11

This comment has been minimized.

Copy link
Author

abhi11 commented May 29, 2018

Thanks !! I have figured it out.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.