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

update doc to v3.1.0 #44

Merged
merged 1 commit into from
Apr 25, 2022
Merged

update doc to v3.1.0 #44

merged 1 commit into from
Apr 25, 2022

Conversation

kqzh
Copy link
Contributor

@kqzh kqzh commented Apr 25, 2022

No description provided.

README-CN.md Outdated
@@ -10,9 +10,11 @@

一些收集的 metrics 是:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

语句不通

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

改成 目前收集的 metrics 是 ?

Copy link
Contributor

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use kernel release version?

Copy link
Contributor Author

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

Copy link
Contributor

@veezhang veezhang Apr 25, 2022

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,

  1. nebula release v3.1.0
  2. stats release v3.1.0
  3. you find bug in stats, then stats release v3.1.1
  4. nebula release v3.1.1

So what version is the stats?

Copy link
Contributor Author

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

Copy link
Contributor

@veezhang veezhang left a 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
Copy link
Contributor

@veezhang veezhang Apr 25, 2022

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,

  1. nebula release v3.1.0
  2. stats release v3.1.0
  3. you find bug in stats, then stats release v3.1.1
  4. nebula release v3.1.1

So what version is the stats?

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 this pull request may close these issues.

3 participants