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

Can you add support for victoriametrics? #59

Closed
denisgolius opened this issue Sep 8, 2020 · 5 comments
Closed

Can you add support for victoriametrics? #59

denisgolius opened this issue Sep 8, 2020 · 5 comments

Comments

@denisgolius
Copy link

Add support for victoriametrics
Because https://grafana.com/grafana/dashboards/1860 already can get data from VM datasource

@denisgolius denisgolius changed the title Catn you add support for victoriametrics? Can you add support for victoriametrics? Sep 8, 2020
@starsliao
Copy link
Owner

I am going to replace my prometheus storage with victoriametrics.

But are they not compatible? Do I need to add Victoriametrics support to the grafana dashboard separately?

@denisgolius
Copy link
Author

denisgolius commented Sep 15, 2020

I am going to replace my prometheus storage with victoriametrics.

But are they not compatible? Do I need to add Victoriametrics support to the grafana dashboard separately?

It fully compatible. Add new datasource with Prometheus type, but use Victoriametrics address. You can always get a help on Slack or Github issues .

@starsliao
Copy link
Owner

我将用victoriametrics替换我的prometheus存储。
但是它们不兼容吗?我是否需要分别向grafana仪表板添加Victoriametrics支持?

它完全兼容。添加具有Prometheus类型的新数据源,但使用Victoriametrics地址。您总是可以在SlackGithub问题上获得帮助。

I tried to use Victoriametrics, and found the problem you mentioned in grafana: the table display will be abnormal.
Then I used Victoriametrics v1.38.1, and the table in grafana showed normal again.
This is the official link about this issue: VictoriaMetrics/VictoriaMetrics#720

@valyala
Copy link

valyala commented Sep 21, 2020

FYI, it looks like the source of the issue has been identified and fixed at VictoriaMetrics/VictoriaMetrics#720 . The bugfix will be included in the next release of VictoriaMetrics.

@starsliao
Copy link
Owner

starsliao commented Oct 4, 2020

VictoriaMetrics v1.42.0 has fixed this bug

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

No branches or pull requests

3 participants