-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[V2]Add Script for metrics markdown table #5941
[V2]Add Script for metrics markdown table #5941
Conversation
Signed-off-by: vvs-personalstash <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5941 +/- ##
=======================================
Coverage 96.46% 96.46%
=======================================
Files 355 355
Lines 20149 20149
=======================================
Hits 19436 19436
Misses 526 526
Partials 187 187
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
In terminal, run |
scripts/metrics-md.py
Outdated
@@ -0,0 +1,101 @@ | |||
import json |
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.
- move this into script/utils
- please document how to use that
- include generated MD file(s) - you can put then under cmd/jaeger/docs/migration
Signed-off-by: vvs-personalstash <[email protected]>
|
||
| Metric Name | Inner Parameters | | ||
|-------------|------------------| | ||
| go_gc_duration_seconds | | |
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.
@Wise-Wizard we should investigate how these standard Go metrics are being generated in v1 and decide how we can enable them in v2.
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, will look in that
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.
this is what we might want: https://github.com/open-telemetry/opentelemetry-go-contrib/blob/main/instrumentation/runtime/runtime.go
ideally Collector would expose those automatically, but it's not implemented currently -- open-telemetry/opentelemetry-collector#2155
@@ -0,0 +1,92 @@ | |||
### Common Metrics | |||
|
|||
| Metric Name | Inner Parameters | |
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.
Inner Parameters
The official term in Prometheus is Labels
scripts/utils/metrics-md.py
Outdated
print('Dict successfully converted to md') | ||
|
||
# Usage | ||
fn = '' #Enter the path of the JSON file generated by compare_metrics.py |
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.
- let's move compare_metrics.py to utils too.
- could we just add the logic here to compare_metrics.py ? Maybe as an optional parameter
--out=json|md
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.
- I still don't see instructions how to run these things - the compare_metrics.py seems to hardcode the input file names like
./V1_Metrics.json
-- please document how those JSON files should be produced.
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 should i create a separate documentation md file for this in scripts/utils or should i just add the instruction as comments
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.
in comments is fine, this isn't something we'd use often
| processor_batch_timeout_trigger_send | processor, service_instance_id, service_name, service_version | | ||
| receiver_accepted_spans | receiver, service_instance_id, service_name, service_version, transport | | ||
| receiver_refused_spans | receiver, service_instance_id, service_name, service_version, transport | | ||
| target_info | service_instance_id, service_name, service_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.
arguably this is equivalent to jaeger_build_info
|
||
| Metric Name | Inner Parameters | | ||
|-------------|------------------| | ||
| jaeger_badger_compaction_current_num_lsm | | |
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.
the storage-specific files will have large overlap with all-in-one, I recommend filtering out only the storage-related metrics.
@@ -0,0 +1,92 @@ | |||
### Common 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.
could we just have a single table with a format similar to ### Equivalent Metrics
? When one side is missing, put n/a
Signed-off-by: vvs-personalstash <[email protected]>
e2545d4
to
02f40db
Compare
Signed-off-by: vvs-personalstash <[email protected]>
@yurishkuro I have made changes as per your reviews,kindly review if there are any changes or errors i may have not noticed |
Description of the changes
Checklist
jaeger
:make lint test
jaeger-ui
:yarn lint
andyarn test