-
Notifications
You must be signed in to change notification settings - Fork 334
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
feat: specify prom server start addr #1111
Conversation
f3c01c0
to
795054d
Compare
Codecov Report
@@ Coverage Diff @@
## develop #1111 +/- ##
===========================================
+ Coverage 85.09% 85.16% +0.07%
===========================================
Files 473 474 +1
Lines 68605 68897 +292
===========================================
+ Hits 58380 58679 +299
+ Misses 10225 10218 -7 |
|
e6ee740
to
aeb012a
Compare
aeb012a
to
50c261e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Now we have two similar configurations prometheus_options
and prom_options
...... Could you also update the configuration reference in our docs repo?
Shall we create an issue for this? I'm not sure whether we already have an issue tracking this. |
* feat: specify promql server start addr * refactor: rename promql to prom in Prometheus API server scenario
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
start prometheus API server with specified addr, so the
/query
and/query_range
can be accessible outside of container by running the standalone mode:cargo run -- standalone start --prom-addr=0.0.0.0:4004