Skip to content

gc_count runtime metrics are reported as gauges but contain process counters #3832

Open
@SpamapS

Description

@SpamapS

Current behaviour

All GC.stats are reported as gauges

Expected behaviour
Counters produce graphs like this:

image

This isn't terribly useful as a gauge, and should be reported as a count.

This is a bit tricky as some of the other stats are _count but do represent gauges.

Steps to reproduce

Just enable ruby runtime metrics and graph runtime.ruby.gc.gc_count or runtime.ruby.gc.major_gc_count

Environment

  • datadog version:

1.23.3

  • Configuration block (Datadog.configure ...):
  require 'ddtrace'
  ::Datadog.configure do |c|
    c.agent.host = ENV["DDTRACE_HOST"]

    c.profiling.enabled = Settings.datadog.profiling_enabled
    c.tracing.log_injection = false

    c.tracing.instrument :rails, service_name: "x-app"
    c.tracing.instrument :active_support, cache_service: "x-cache"
    c.tracing.instrument :action_pack, service_name: "x-controller"
    c.tracing.instrument :active_model_serializers
    c.tracing.instrument :active_record, service_name: "x-postgres"
    c.tracing.instrument :pg, service_name: "postgres", comment_propagation: 'full'

    c.tracing.instrument :redis # service_name defaults to "redis"

    c.tracing.instrument :http #net/http
    c.tracing.instrument :rest_client

    c.runtime_metrics.enabled = true
    c.runtime_metrics.statsd = TFE::Clients.rtstatsd
  • Ruby version:

3.1.5

  • Operating system:

Linux (various) & MacOS

  • Relevant library versions:

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugInvolves a bugcommunityWas opened by a community member

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions