-
Notifications
You must be signed in to change notification settings - Fork 994
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
fix: greptimedb can't work with version >= 0.5 #2095
Conversation
d933f25
to
fe851b8
Compare
Thank you very much for your help. |
Thanks for contribution. local test ok. 👍👍
I found it is other storage common bug due victoriaMetrics adaptation, we will fix it later. Btw, may i ask how is the protocol compatibility of greptime's prometheus api? We want to try greptime prometheus api in the future, just like victoriaMetrics as a recommond storage. Because we are designing new data stru and integrating the grafana page capabilities, . thanks. |
Sure, GreptimeDB totally supports Prometheus remote storage(and compatible with vmagent) protocols, please read the doc https://docs.greptime.com/user-guide/write-data/prometheus#a-note-for-victoriametrics-remote-write And if you want to use PromQL query API, it's supported too https://docs.greptime.com/user-guide/query-data/promql#greptimedb-s-http-api |
What's changed?
Close #1754
Fixed
GreptimeDbDataStorage
can't work with GreptimeDB >= 0.5:GrepTimeDbDataStorage
toGreptimeDbDataStorage
.Test with MySQL monitor:
Not relevant to this PR, but I found that Prometheus Collector is not working, it always adds a prefix
_
toapp
when saving data but not in queries.Checklist
Add or update API