The go prometheus client exposes a set of metrics about the go runtime,
primarily around memory allocation, in addition to any that your
application itself may choose to create. e.g.
# HELP go_gc_duration_seconds A summary of the pause duration of garbage
collection cycles.
# TYPE go_gc_duratio
Right but Prometheus / Grafana is just a collector of the data output by
runtime/metrics. Where introscope / glowroot are configured at the java
command line to and pull that information out of the java JVM. Please
correct me if I am wrong?
Thanks!!
On Tuesday, August 16, 2022 at 9:20:45 AM
Monitoring and observability are best practices regardless of what language
you use. We use a combination of Prometheus / Grafana and metrics exported
by runtime/metrics. We also include custom metrics tailored to our
application's use-case.
Prometheus is not a standard Linux tool, but it is open
My company relies heavily on Java., Java apps we run require Introscope or
Glowroot to monitor them and many outages have been solved using those
tools. If we were to write our apps in Go -- would we need an application
monitoring tool, or would standard Linux tools suffice?
Thanks-- Rich
--
