-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/Flinkmetricsreceiver] Apache Flink Metric Receiver #10121
[receiver/Flinkmetricsreceiver] Apache Flink Metric Receiver #10121
Conversation
d086817
to
5744c6e
Compare
32ced72
to
f8eed3a
Compare
receiver/flinkmetricsreceiver/testdata/apiresponses/jobmanager_metric_names.json
Outdated
Show resolved
Hide resolved
receiver/flinkmetricsreceiver/testdata/apiresponses/jobmanager_metric_values.json
Outdated
Show resolved
Hide resolved
receiver/flinkmetricsreceiver/testdata/apiresponses/jobs_ids.json
Outdated
Show resolved
Hide resolved
receiver/flinkmetricsreceiver/testdata/apiresponses/jobs_metric_names.json
Outdated
Show resolved
Hide resolved
553ec66
to
1743f8f
Compare
I updated pr feedback @djaglowski and it is ready to be looked at again please. |
7f104f5
to
7465bfc
Compare
PR is ready for review again please @djaglowski |
9e336d0
to
07cce9f
Compare
Ready to be looked at again @djaglowski please |
flink.jvm.cpu.load: | ||
enabled: true | ||
description: The CPU usage (%) of the JVM for a jobmanager or taskmanager. | ||
unit: 1 |
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.
removed
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'm confused. I thought you said this metric is measured in %. That's my interpretation from the article you linked.
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.
@JonathanWamsley PTAL
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.
yeah, I could not find a unit though and searching through the metadata.yaml mongo atlas had that convention. so I put it in. I thought you were saying with "%?" to remove that convention or something.
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 the units be %
or not?
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 they should be. The unit can be 1 but not %
because that will break in the metadata generation. Maybe "{percentage}"
instead?
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.
"%"
should work
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.
updated unit
receiver/flinkmetricsreceiver/testdata/expected_metrics/metrics_golden.json
Show resolved
Hide resolved
07cce9f
to
6eeaae2
Compare
83f006e
to
7e49410
Compare
enum: [ jobmanager, taskmanager ] | ||
|
||
attributes: | ||
operator_name: |
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 can be a followup issue, but I think this should probably be user-visible as name
.
operator_name: | |
operator_name: | |
value: name |
operator_name: | ||
description: The operator name. | ||
type: string | ||
garbage_collector_name: |
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.
garbage_collector_name: | |
garbage_collector_name: | |
value: name |
…lemetry#10121) * wip before integration and concurrency * tidy up client names * wip integration test * wip integration test * update to flinkmetrics and integration test * move attributes to resource attributes * add flink integration files * update model import name * add changelog and tidy up * update mod and lint check * update with pr feedback * update pr feedback with status header * unexport process methods * go tidy up * add partial metrics collecting on taskmanager, jobs, and subtasks * go tidy update * fix shadow declaration of err * update pr feedback * tidy up * apply scope version update * make expected responses easier to test when metadata/generated files update * update to host.name and move status table * combine jobmanager and taskmanager metrics * tidy up * update generated files * fix mod version * update pr feedback * tidy up * seperated checkpoint in_progress as non-monotonic sum metric * tidy up local receiver * update version * update cpu descriptions * fix taskmanager/jobs bug and added tests with multiple taskmanagers/jobs * space * change non_heap to nonheap * update unit
Description: Add New Component: Apache Flink Metric Receiver
Link to tracking Issue: New Component: Apache Flink Metric Receiver
Testing: A series of testing was added including:
Documentation: README.md documentation.md