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

Rename JFR streaming to JFR metrics #749

Closed
wants to merge 4 commits into from

Conversation

trask
Copy link
Member

@trask trask commented Feb 20, 2023

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.

@jack-berg
Copy link
Member

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 jfr-telemetry overly broad?

@trask
Copy link
Member Author

trask commented Feb 20, 2023

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 jfr-telemetry overly broad?

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

  • runtime-metrics-jfr
  • runtime-metrics-jmx

@mateuszrzeszutek
Copy link
Member

WDYT about renaming runtime-metrics to runtime-telemetry-jmx instead?

is there a benefit to having a single module for all JFR-based telemetry, or do you think we would split things out?

Don't we usually try to have all possible telemetry signals in one package? E.g. HTTP metrics, Kafka metrics

@jack-berg
Copy link
Member

is there a benefit to having a single module for all JFR-based telemetry, or do you think we would split things out?

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.

WDYT about renaming runtime-metrics to runtime-telemetry-jmx instead?

Sounds good to me. runtime-telemetry-jmx and runtime-telemetry-jfr

@trask
Copy link
Member Author

trask commented Feb 22, 2023

Sounds good to me. runtime-telemetry-jmx and runtime-telemetry-jfr

👍

should we just not publish the contrib module for now?

cc @roberttoyonaga

@jack-berg
Copy link
Member

@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.

@trask
Copy link
Member Author

trask commented Feb 22, 2023

Closing, will send PR to disable publishing instead.

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.

5 participants