-
Notifications
You must be signed in to change notification settings - Fork 130
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
Rename JFR streaming to JFR metrics #749
Conversation
I anticipate other telemetry like events and other perhaps profiles (depending on how that area takes shape) being produced by this instrumentation. The metrics suffix seems too restrictive. Is |
is there a benefit to having a single module for all JFR-based telemetry, or do you think we would split things out? when this goes over to instrumentation repo, one naming I was thinking of is
|
WDYT about renaming
Don't we usually try to have all possible telemetry signals in one package? E.g. HTTP metrics, Kafka metrics |
There's definitely some setup / boilerplate code that would need to be shared amongst the different signals. I can't imagine the handlers for the additional pieces being so heavy weight that users would want it split out into multiple modules.
Sounds good to me. |
👍 should we just not publish the contrib module for now? |
@trask if you're willing to sponsor it for inclusion in instrumentation I think we should postpone publishing rather than publishing under different coordinates in subsequent releases. |
Closing, will send PR to disable publishing instead. |
I think this would good to do before 1.23.0 release, since we only just enabled publishing of this module, and I don't think
jfr-streaming
a great fit.