-
Notifications
You must be signed in to change notification settings - Fork 48
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
Expose JVM metrics with Prometheus inline exporter #67
Comments
Attempt at avoiding the exception reported here: BrunoBonacci#67 (comment)
Attempt at avoiding the exception reported here: BrunoBonacci#67 (comment)
* Rename variable that shadows type fn Attempt at avoiding the exception reported here: #67 (comment) * Better name for collector-registry Co-authored-by: piotr-yuxuan <piotr-yuxuan@users.noreply.github.com>
This issue if fixed (thanks @piotr-yuxuan) it will be released with the next release (v0.7.2 or v0.8.0) |
Reopening as this issue needs more work. |
Currently the μ/log Prometheus publisher converts events into metrics by creating a new metrics for every numerical value. One option/workaround is to add a If you want all metrics you will need to "flatten" a nested map while I will think whether this could be something that it is done |
Hello, thanks for this nice project! I've been stumbling upon one exception, and one unexpected behaviour while trying to expose JVM metrics to Prometheus scrapper:
So far the counter
clojure_core_mulog_jvm_metrics_sampled
increases, but no further metrics are exposed. I think this snippet is pretty close to the doc so I'm a bit puzzled.On my machine this behaviour appeared consistent accross versions
0.5.0
,0.6.0
,0.7.0
, and0.7.1
.The text was updated successfully, but these errors were encountered: