Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign uphttp api query failed using '+' #4199
Comments
This comment has been minimized.
This comment has been minimized.
|
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
May 28, 2018
This comment has been minimized.
This comment has been minimized.
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
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.
beijiaxu commentedMay 28, 2018
Proposal
Use case. Why is this important?
need memory_uage metric (node_memory_MemTotal - (node_memory_MemFree + node_memory_Cached + node_memory_Buffers))
Bug Report
What did you do?
use graph query and query http api
What did you expect to see?
metric value
What did you see instead? Under which circumstances?
graph query success but http api failed
{
"status": "error",
"errorType": "bad_data",
"error": "parse error at char 79: unexpected identifier "avg_over_time" in paren expression, expected ")""
}
Environment
CentOS 7.3
System information:
Linux 3.10.0-514.el7.x86_64 x86_64
Prometheus version:
2.2.1
Alertmanager version:
Logs:
no log print in journalctl
While using graph query metric, I can see '+' is encoded to '%2B', I tried to replace '+' with '%2B', http api query succeeded.
But I use web console to encodeURI('+'), it doesn't encode this word.