Giters

HeavyHorst / remco

remco is a lightweight configuration management tool

Home Page:https://heavyhorst.github.io/remco/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Strange metrics from prometheus sink

freeseacher opened this issue · comments

commented

Hi
I got some time to check recently added prometheus sik support and got pretty strange metrics

that is all of them

# HELP go_gc_duration_seconds A summary of the pause duration of garbage collection cycles.
# TYPE go_gc_duration_seconds summary
go_gc_duration_seconds{quantile="0"} 1.97e-05
go_gc_duration_seconds{quantile="0.25"} 2.233e-05
go_gc_duration_seconds{quantile="0.5"} 3.3328e-05
go_gc_duration_seconds{quantile="0.75"} 4.0256e-05
go_gc_duration_seconds{quantile="1"} 0.000138654
go_gc_duration_seconds_sum 0.000700897
go_gc_duration_seconds_count 18
# HELP go_goroutines Number of goroutines that currently exist.
# TYPE go_goroutines gauge
go_goroutines 27
# HELP go_info Information about the Go environment.
# TYPE go_info gauge
go_info{version="go1.15.2"} 1
# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
# TYPE go_memstats_alloc_bytes gauge
go_memstats_alloc_bytes 2.670056e+06
# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
# TYPE go_memstats_alloc_bytes_total counter
go_memstats_alloc_bytes_total 4.974308e+07
# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
# TYPE go_memstats_buck_hash_sys_bytes gauge
go_memstats_buck_hash_sys_bytes 1.469807e+06
# HELP go_memstats_frees_total Total number of frees.
# TYPE go_memstats_frees_total counter
go_memstats_frees_total 818932
# HELP go_memstats_gc_cpu_fraction The fraction of this program's available CPU time used by the GC since the program started.
# TYPE go_memstats_gc_cpu_fraction gauge
go_memstats_gc_cpu_fraction 0.0015231990967114032
# HELP go_memstats_gc_sys_bytes Number of bytes used for garbage collection system metadata.
# TYPE go_memstats_gc_sys_bytes gauge
go_memstats_gc_sys_bytes 4.900856e+06
# HELP go_memstats_heap_alloc_bytes Number of heap bytes allocated and still in use.
# TYPE go_memstats_heap_alloc_bytes gauge
go_memstats_heap_alloc_bytes 2.670056e+06
# HELP go_memstats_heap_idle_bytes Number of heap bytes waiting to be used.
# TYPE go_memstats_heap_idle_bytes gauge
go_memstats_heap_idle_bytes 6.2799872e+07
# HELP go_memstats_heap_inuse_bytes Number of heap bytes that are in use.
# TYPE go_memstats_heap_inuse_bytes gauge
go_memstats_heap_inuse_bytes 3.784704e+06
# HELP go_memstats_heap_objects Number of allocated objects.
# TYPE go_memstats_heap_objects gauge
go_memstats_heap_objects 24874
# HELP go_memstats_heap_released_bytes Number of heap bytes released to OS.
# TYPE go_memstats_heap_released_bytes gauge
go_memstats_heap_released_bytes 6.1947904e+07
# HELP go_memstats_heap_sys_bytes Number of heap bytes obtained from system.
# TYPE go_memstats_heap_sys_bytes gauge
go_memstats_heap_sys_bytes 6.6584576e+07
# HELP go_memstats_last_gc_time_seconds Number of seconds since 1970 of last garbage collection.
# TYPE go_memstats_last_gc_time_seconds gauge
go_memstats_last_gc_time_seconds 1.6103504592878752e+09
# HELP go_memstats_lookups_total Total number of pointer lookups.
# TYPE go_memstats_lookups_total counter
go_memstats_lookups_total 0
# HELP go_memstats_mallocs_total Total number of mallocs.
# TYPE go_memstats_mallocs_total counter
go_memstats_mallocs_total 843806
# HELP go_memstats_mcache_inuse_bytes Number of bytes in use by mcache structures.
# TYPE go_memstats_mcache_inuse_bytes gauge
go_memstats_mcache_inuse_bytes 1736
# HELP go_memstats_mcache_sys_bytes Number of bytes used for mcache structures obtained from system.
# TYPE go_memstats_mcache_sys_bytes gauge
go_memstats_mcache_sys_bytes 16384
# HELP go_memstats_mspan_inuse_bytes Number of bytes in use by mspan structures.
# TYPE go_memstats_mspan_inuse_bytes gauge
go_memstats_mspan_inuse_bytes 58344
# HELP go_memstats_mspan_sys_bytes Number of bytes used for mspan structures obtained from system.
# TYPE go_memstats_mspan_sys_bytes gauge
go_memstats_mspan_sys_bytes 131072
# HELP go_memstats_next_gc_bytes Number of heap bytes when next garbage collection will take place.
# TYPE go_memstats_next_gc_bytes gauge
go_memstats_next_gc_bytes 4.194304e+06
# HELP go_memstats_other_sys_bytes Number of bytes used for other system allocations.
# TYPE go_memstats_other_sys_bytes gauge
go_memstats_other_sys_bytes 380569
# HELP go_memstats_stack_inuse_bytes Number of bytes in use by the stack allocator.
# TYPE go_memstats_stack_inuse_bytes gauge
go_memstats_stack_inuse_bytes 524288
# HELP go_memstats_stack_sys_bytes Number of bytes obtained from system for stack allocator.
# TYPE go_memstats_stack_sys_bytes gauge
go_memstats_stack_sys_bytes 524288
# HELP go_memstats_sys_bytes Number of bytes obtained from system.
# TYPE go_memstats_sys_bytes gauge
go_memstats_sys_bytes 7.4007552e+07
# HELP go_threads Number of OS threads created.
# TYPE go_threads gauge
go_threads 7
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 0.31
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1024
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 12
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 2.5690112e+07
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.61035043098e+09
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 7.42998016e+08
# HELP process_virtual_memory_max_bytes Maximum amount of virtual memory available in bytes.
# TYPE process_virtual_memory_max_bytes gauge
process_virtual_memory_max_bytes -1
# HELP promhttp_metric_handler_requests_in_flight Current number of scrapes being served.
# TYPE promhttp_metric_handler_requests_in_flight gauge
promhttp_metric_handler_requests_in_flight 1
# HELP promhttp_metric_handler_requests_total Total number of scrapes by HTTP status code.
# TYPE promhttp_metric_handler_requests_total counter
promhttp_metric_handler_requests_total{code="200"} 1
promhttp_metric_handler_requests_total{code="500"} 0
promhttp_metric_handler_requests_total{code="503"} 0
# HELP remco_backends_synced_total remco_backends_synced_total
# TYPE remco_backends_synced_total counter
remco_backends_synced_total{name="consul"} 4
remco_backends_synced_total{name="file"} 2
# HELP remco_files_staged_total remco_files_staged_total
# TYPE remco_files_staged_total counter
remco_files_staged_total 12
# HELP remco_files_synced_total remco_files_synced_total
# TYPE remco_files_synced_total counter
remco_files_synced_total 12
# HELP remco_files_template_execution_duration remco_files_template_execution_duration
# TYPE remco_files_template_execution_duration summary
remco_files_template_execution_duration{quantile="0.5"} NaN
remco_files_template_execution_duration{quantile="0.9"} NaN
remco_files_template_execution_duration{quantile="0.99"} NaN
remco_files_template_execution_duration_sum 384.0843696594238
remco_files_template_execution_duration_count 12
# HELP remco_HOSTNAME_runtime_alloc_bytes remco_HOSTNAME_runtime_alloc_bytes
# TYPE remco_HOSTNAME_runtime_alloc_bytes gauge
remco_HOSTNAME_runtime_alloc_bytes 2.609776e+06
# HELP remco_HOSTNAME_runtime_free_count remco_HOSTNAME_runtime_free_count
# TYPE remco_HOSTNAME_runtime_free_count gauge
remco_HOSTNAME_runtime_free_count 818930
# HELP remco_HOSTNAME_runtime_heap_objects remco_HOSTNAME_runtime_heap_objects
# TYPE remco_HOSTNAME_runtime_heap_objects gauge
remco_HOSTNAME_runtime_heap_objects 24723
# HELP remco_HOSTNAME_runtime_malloc_count remco_HOSTNAME_runtime_malloc_count
# TYPE remco_HOSTNAME_runtime_malloc_count gauge
remco_HOSTNAME_runtime_malloc_count 843653
# HELP remco_HOSTNAME_runtime_num_goroutines remco_HOSTNAME_runtime_num_goroutines
# TYPE remco_HOSTNAME_runtime_num_goroutines gauge
remco_HOSTNAME_runtime_num_goroutines 21
# HELP remco_HOSTNAME_runtime_sys_bytes remco_HOSTNAME_runtime_sys_bytes
# TYPE remco_HOSTNAME_runtime_sys_bytes gauge
remco_HOSTNAME_runtime_sys_bytes 7.4007552e+07
# HELP remco_HOSTNAME_runtime_total_gc_pause_ns remco_HOSTNAME_runtime_total_gc_pause_ns
# TYPE remco_HOSTNAME_runtime_total_gc_pause_ns gauge
remco_HOSTNAME_runtime_total_gc_pause_ns 700897
# HELP remco_HOSTNAME_runtime_total_gc_runs remco_HOSTNAME_runtime_total_gc_runs
# TYPE remco_HOSTNAME_runtime_total_gc_runs gauge
remco_HOSTNAME_runtime_total_gc_runs 18
# HELP remco_runtime_gc_pause_ns remco_runtime_gc_pause_ns
# TYPE remco_runtime_gc_pause_ns summary
remco_runtime_gc_pause_ns{quantile="0.5"} NaN
remco_runtime_gc_pause_ns{quantile="0.9"} NaN
remco_runtime_gc_pause_ns{quantile="0.99"} NaN
remco_runtime_gc_pause_ns_sum 700897
remco_runtime_gc_pause_ns_count 18
  1. the interesting one is one with HOSTNAME. why do we have HOSTNAME embeded in metric name here ?
  2. why do we have such strange remco_runtime_gc_pause_ns for quantiles ?
  3. do it differs from go_gc_duration_seconds ?

probably i should mention @syndicut

commented
  1. the interesting one is one with HOSTNAME. why do we have HOSTNAME embeded in metric name here ?

It's inherited from go-metrics default config,

remco/vendor/github.com/armon/go-metrics/start.go

Line 56 in 82e977b

EnableHostname: true, // Enable hostname prefix
EnableHostname option.

  1. why do we have such strange remco_runtime_gc_pause_ns for quantiles ?
  2. do it differs from go_gc_duration_seconds ?

go-metrics has separate mechanism for gathering runtime stats:

remco/vendor/github.com/armon/go-metrics/metrics.go

Line 236 in 82e977b

func (m *Metrics) emitRuntimeStats() {

I think it's useless in prometheus sink, because it's pretty much duplicates what prometheus library collects by default.

I can make all set of options configurable from config, so hostname and runtime stats can be disabled from config and make a note about it in prometheus sink config.

commented

Thank you for pointing this out and trying telemetry feature, I'm glad that I'm not the only one using it :-)

commented
  1. the interesting one is one with HOSTNAME. why do we have HOSTNAME embeded in metric name here ?

Also, hostname is added only for gauges, some motivation about it:
hashicorp/go-metrics#28 (comment)

commented

Also, hostname is added only for gauges, some motivation about it

it seems pretty odd for me. sounds like it should be label named instance that one was specifically designed for it

commented

Also, hostname is added only for gauges, some motivation about it

it seems pretty odd for me. sounds like it should be label named instance that one was specifically designed for it

It's kinda possible via https://github.com/armon/go-metrics/blob/2bc64ebd2914430b52dfc5c90c00722afec193ba/start.go#L17 EnableHostnameLabel , though it still be hostname label, not instance

commented

So my PR made it to master and you can now configure go-metrics behaviour to avoid unnecessary metrics:
https://github.com/HeavyHorst/remco/blob/master/docs/content/config/configuration-options.md#telemetry-configuration-options