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

http api query failed using '+' #4199

Closed
beijiaxu opened this Issue May 28, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@beijiaxu
Copy link

beijiaxu commented May 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.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented May 28, 2018

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.

@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.