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

Error when saving GreptimeDB as Prometheus data source #3496

Closed
Tracked by #3492
tisonkun opened this issue Mar 13, 2024 · 4 comments · Fixed by #3604
Closed
Tracked by #3492

Error when saving GreptimeDB as Prometheus data source #3496

tisonkun opened this issue Mar 13, 2024 · 4 comments · Fixed by #3604
Assignees

Comments

@tisonkun
Copy link
Collaborator

tisonkun commented Mar 13, 2024

readNumberAsString: invalid number, error found in #10 byte of ...|"result":[{"metric":|..., bigger context ...|"success","data":{"resultType":"scalar","result":[{"metric":{"name":""},"values":[],"value":[4.0|... - There was an error returned querying the Prometheus API.

@Finnmccarthy
Copy link

Also having the same issue while attempting to add greptimedb as a Prometheus data source in Grafana. Are there any work arounds for this issue?

readNumberAsString: invalid number, error found in #10 byte of ...|"result":[{"metric":|..., bigger context ...|"success","data":{"resultType":"scalar","result":[{"metric":{"name":""},"values":[],"value":[4.0|... - There was an error returned querying the Prometheus API.

@waynexia
Copy link
Member

Also having the same issue while attempting to add greptimedb as a Prometheus data source in Grafana. Are there any work arounds for this issue?

readNumberAsString: invalid number, error found in #10 byte of ...|"result":[{"metric":|..., bigger context ...|"success","data":{"resultType":"scalar","result":[{"metric":{"name":""},"values":[],"value":[4.0|... - There was an error returned querying the Prometheus API.

Just ignore this error should be fine. The data source is configured successfully.

@tisonkun
Copy link
Collaborator Author

@waynexia Thanks for your information. But why do we get this error message? Could we get rid of it?

@waynexia
Copy link
Member

Working on it... PR this afternoon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants