Add basic metrics in storage service #872
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
critical27
requested review from
darionyaphet,
CPWstatic,
dangleptr,
boshengchen and
laura-ding
|
Unit testing passed. |
wadeliuyi
reviewed
Sep 1, 2019
wadeliuyi
reviewed
Sep 1, 2019
|
Unit testing failed. |
|
Jenkins go, please don't abort - -! |
|
Unit testing passed. |
|
Unit testing passed. |
1 similar comment
|
Unit testing passed. |
|
Unit testing passed. |
1 similar comment
|
Unit testing passed. |
|
Unit testing passed. |
|
Unit testing passed. |
laura-ding
reviewed
Sep 17, 2019
Yeah, u r right |
|
Unit testing passed. |
|
How to get the metrics? Could you describe it in the summary? |
|
Unit testing passed. |
dangleptr
previously approved these changes
Oct 10, 2019
|
Unit testing failed. |
add some basic stats in storage
|
Unit testing passed. |
|
Unit testing passed. |
rebase on upstream/master address @darionyaphet's comments
|
Unit testing passed. |
darionyaphet
approved these changes
Oct 12, 2019
|
Unit testing passed. |
whitewum
pushed a commit
to whitewum/nebula
that referenced
this pull request
Oct 16, 2019
1. Add basic metrics for data operation in storage service 2. Add a storage integrity test tool in storage-perf. close vesoft-inc#287 Now we support following metrics: get_bound, bound_stats, vertex_props, edge_props, add_vertex, add_edge, del_vertex, update_vertex, update_edge. We can get qps or latency from these metrics (add suffix), for example: vertex_props_qps or vertex_props_latency. You can get a single metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats=vertex_props_qps.rate.60 If you want get multiple metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats=vertex_props_qps.rate.60,vertex_props_latency.avg.60,vertex_props_latency.p99.60&returnjson" We can get qps, avg latency and p99 latency in a minutue. You can get all metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats" The storage integrity tool is used for verifying data integrity in storage. It only works for single replica for now. You can use it like this: ./storage_integrity --meta_server_addrs=192.168.8.5:60001 --first_vertex_id=100 --width=1000 --height=1000 meta_server_addrs is the meta server addresss. first_vertex_id is the first vertex id which we inserts. width and height is the width and height of the big matrix.
|
relate to #185 |
yixinglu
pushed a commit
to yixinglu/nebula
that referenced
this pull request
Feb 16, 2020
1. Add basic metrics for data operation in storage service 2. Add a storage integrity test tool in storage-perf. close vesoft-inc#287 Now we support following metrics: get_bound, bound_stats, vertex_props, edge_props, add_vertex, add_edge, del_vertex, update_vertex, update_edge. We can get qps or latency from these metrics (add suffix), for example: vertex_props_qps or vertex_props_latency. You can get a single metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats=vertex_props_qps.rate.60 If you want get multiple metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats=vertex_props_qps.rate.60,vertex_props_latency.avg.60,vertex_props_latency.p99.60&returnjson" We can get qps, avg latency and p99 latency in a minutue. You can get all metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats" The storage integrity tool is used for verifying data integrity in storage. It only works for single replica for now. You can use it like this: ./storage_integrity --meta_server_addrs=192.168.8.5:60001 --first_vertex_id=100 --width=1000 --height=1000 meta_server_addrs is the meta server addresss. first_vertex_id is the first vertex id which we inserts. width and height is the width and height of the big matrix.
tong-hao
pushed a commit
to tong-hao/nebula
that referenced
this pull request
Jun 1, 2021
1. Add basic metrics for data operation in storage service 2. Add a storage integrity test tool in storage-perf. close vesoft-inc#287 Now we support following metrics: get_bound, bound_stats, vertex_props, edge_props, add_vertex, add_edge, del_vertex, update_vertex, update_edge. We can get qps or latency from these metrics (add suffix), for example: vertex_props_qps or vertex_props_latency. You can get a single metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats=vertex_props_qps.rate.60 If you want get multiple metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats=vertex_props_qps.rate.60,vertex_props_latency.avg.60,vertex_props_latency.p99.60&returnjson" We can get qps, avg latency and p99 latency in a minutue. You can get all metrics like this: curl -G "http://127.0.0.1:50005/get_stats?stats" The storage integrity tool is used for verifying data integrity in storage. It only works for single replica for now. You can use it like this: ./storage_integrity --meta_server_addrs=192.168.8.5:60001 --first_vertex_id=100 --width=1000 --height=1000 meta_server_addrs is the meta server addresss. first_vertex_id is the first vertex id which we inserts. width and height is the width and height of the big matrix.
yixinglu
pushed a commit
to yixinglu/nebula
that referenced
this pull request
Jan 31, 2023
Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com> Co-authored-by: Romi <romi.chen@vesoft.com> Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
close #287
Now we support following metrics:
get_bound, bound_stats, vertex_props, edge_props, add_vertex, add_edge, del_vertex, update_vertex, update_edge.We can get qps or latency from these metrics (add suffix), for example:
vertex_props_qpsorvertex_props_latency.You can get a single metrics like this:
curl -G "http://127.0.0.1:50005/get_stats?stats=vertex_props_qps.rate.60If you want get multiple metrics like this:
curl -G "http://127.0.0.1:50005/get_stats?stats=vertex_props_qps.rate.60,vertex_props_latency.avg.60,vertex_props_latency.p99.60&returnjson"We can get qps, avg latency and p99 latency in a minutue.
You can get all metrics like this:
curl -G "http://127.0.0.1:50005/get_stats?stats"The storage integrity tool is used for verifying data integrity in storage. It only works for single replica for now. You can use it like this:
./storage_integrity --meta_server_addrs=192.168.8.5:60001 --first_vertex_id=100 --width=1000 --height=1000meta_server_addrsis the meta server addresss.first_vertex_idis the first vertex id which we inserts.widthandheightis the width and height of the big matrix.