You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I call metrics.jvm.core/instrument-jvm during startup, there is no corresponding metrics.jvm.core/uninstrument-jvm to call during shutdown. This causes problems for me during tests that check startup and shutdown behavior; if I call instrument-jvm twice I get an error "A metric named jvm.attribute.vendor already exists".
I suppose a less desirable alternative that would still address my use-case would be to make instrumentation idempotent. A clean shutdown would be my preference.
The text was updated successfully, but these errors were encountered:
If I call
metrics.jvm.core/instrument-jvm
during startup, there is no correspondingmetrics.jvm.core/uninstrument-jvm
to call during shutdown. This causes problems for me during tests that check startup and shutdown behavior; if I callinstrument-jvm
twice I get an error "A metric named jvm.attribute.vendor already exists".I suppose a less desirable alternative that would still address my use-case would be to make instrumentation idempotent. A clean shutdown would be my preference.
The text was updated successfully, but these errors were encountered: