-
Notifications
You must be signed in to change notification settings - Fork 26
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
update doc to v3.1.0 #44
Conversation
README-CN.md
Outdated
@@ -10,9 +10,11 @@ | |||
|
|||
一些收集的 metrics 是: |
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.
语句不通
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.
改成 目前收集的 metrics 是
?
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.
ok
@@ -69,12 +71,12 @@ scrape_configs: | |||
```shell | |||
$ docker run -d --restart=always --name nebula-stats-exporter -p 9100:9100 \ | |||
-v "<<PATH_OF_CONFIG_FILE>>:/config.yaml" \ | |||
vesoft/nebula-stats-exporter:v0.0.6 --bare-metal --bare-metal-config=/config.yaml | |||
vesoft/nebula-stats-exporter:v3.1.0 --bare-metal --bare-metal-config=/config.yaml |
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.
use kernel release version?
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.
yes, because release-tag will use v3.1.0, I think unite is better
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.
Is the version definition strictly consistent, or just the first two?
For examples,
- nebula release v3.1.0
- stats release v3.1.0
- you find bug in stats, then stats release v3.1.1
- nebula release v3.1.1
So what version is the stats?
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.
if stats don't have change, stats release v3.1.1, otherwise v3.1.2, promise x.y compatible nebula
@@ -22,4 +22,4 @@ maintainers: | |||
name: nebula-exporter | |||
sources: | |||
- https://github.com/vesoft-inc/nebula | |||
version: 0.0.6 | |||
version: 3.1.0 |
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.
ditto
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
@@ -69,12 +71,12 @@ scrape_configs: | |||
```shell | |||
$ docker run -d --restart=always --name nebula-stats-exporter -p 9100:9100 \ | |||
-v "<<PATH_OF_CONFIG_FILE>>:/config.yaml" \ | |||
vesoft/nebula-stats-exporter:v0.0.6 --bare-metal --bare-metal-config=/config.yaml | |||
vesoft/nebula-stats-exporter:v3.1.0 --bare-metal --bare-metal-config=/config.yaml |
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.
Is the version definition strictly consistent, or just the first two?
For examples,
- nebula release v3.1.0
- stats release v3.1.0
- you find bug in stats, then stats release v3.1.1
- nebula release v3.1.1
So what version is the stats?
No description provided.