Skip to content
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

Revisit redis receiver metrics #6942

Open
1 of 5 tasks
dmitryax opened this issue Dec 23, 2021 · 13 comments
Open
1 of 5 tasks

Revisit redis receiver metrics #6942

dmitryax opened this issue Dec 23, 2021 · 13 comments
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed receiver/redis Redis related issues

Comments

@dmitryax
Copy link
Member

dmitryax commented Dec 23, 2021

The following issues found with the redis receiver metrics:

  • Many metrics miss unit field.
  • Some metrics can be combined with an additional attribute, e.g. different metrics for memory -> one metrics + "state" attribute.
  • Start timestamp is inconsistent between sum and gauge metrics.
  • CPU metrics reported inconsistently, only 3 of 8 redis metrics reported:
    • used_cpu_sys -> redis.cpu.time{state=sys}
    • used_cpu_user -> redis.cpu.time{state=user}
    • used_cpu_sys_children -> redis.cpu.time{state=children}
    • used_cpu_user_children is skipped
    • used_cpu_sys_main_thread is skipped
    • used_cpu_user_main_thread is skipped
  • More than half of the redis metrics are not collected at all, they can be added as optional (disabled by default) metrics once [receiver/redis] Apply new mdatagen metrics builder #6938 is merged.
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Nov 14, 2022
@dmitryax dmitryax added help wanted Extra attention is needed and removed Stale labels Nov 14, 2022
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Mar 20, 2023
@dmitryax dmitryax removed the Stale label Mar 23, 2023
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label May 22, 2023
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 21, 2023
@dmitryax dmitryax reopened this Jul 21, 2023
@crobert-1 crobert-1 assigned crobert-1 and bjandras and unassigned crobert-1 Sep 6, 2023
@crobert-1
Copy link
Member

@bjandras has volunteered to take this.

@bjandras
Copy link
Contributor

bjandras commented Sep 6, 2023

Missing CPU metrics addressed in #14943.

@bjandras
Copy link
Contributor

bjandras commented Sep 6, 2023

Missing metric units addressed in #23573.

dmitryax pushed a commit that referenced this issue Sep 13, 2023
**Description:** Added command latency metric to the redis receiver.

**Link to tracking Issue:**
#6942

**Testing:** Added tests for parsing `latencystats` section of redis
info.

**Documentation:** Metric documentation in metadata.yaml
codeboten pushed a commit that referenced this issue Sep 14, 2023
Changed unit for `redis.cmd.latency` metric from
microseconds to seconds.

#6942

Co-authored-by: Alex Boten <aboten@lightstep.com>
jorgeancal pushed a commit to jorgeancal/opentelemetry-collector-contrib that referenced this issue Sep 18, 2023
**Description:** Added command latency metric to the redis receiver.

**Link to tracking Issue:**
open-telemetry#6942

**Testing:** Added tests for parsing `latencystats` section of redis
info.

**Documentation:** Metric documentation in metadata.yaml
jorgeancal pushed a commit to jorgeancal/opentelemetry-collector-contrib that referenced this issue Sep 18, 2023
…telemetry#26686)

Changed unit for `redis.cmd.latency` metric from
microseconds to seconds.

open-telemetry#6942

Co-authored-by: Alex Boten <aboten@lightstep.com>
@bjandras
Copy link
Contributor

Here's a breakdown of all available Redis metrics and their OTel counterparts (if implemented): https://docs.google.com/spreadsheets/d/1KRM5NuFnYxiW1EJ00wt-NF1LhrIbuWjn-iC-lAOrfQg/edit?usp=sharing. We can use it to select which metric to collect.

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Nov 27, 2023
@hughesjj
Copy link
Contributor

@bjandras Hey, how was that output generated btw? Doing some auditing on my end, would like to have a reproducible way (even if runbook-esque) to validate ongoing coverage improvement.

@github-actions github-actions bot removed the Stale label Nov 28, 2023
dmitryax pushed a commit that referenced this issue Jan 10, 2024
**Description:** Adds missing metrics for `slave_repl_offset` and adds
an integration test to configure a cluster to test such

**Link to tracking Issue:**
[`6942`](#6942)

**Testing:** `cd receiver/redisreceiver && make mod-integration-test`

**Documentation:** (autogenerated from mdatagen)
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jan 29, 2024
@crobert-1 crobert-1 removed the Stale label Jan 29, 2024
cparkins pushed a commit to AmadeusITGroup/opentelemetry-collector-contrib that referenced this issue Feb 1, 2024
**Description:** Adds missing metrics for `slave_repl_offset` and adds
an integration test to configure a cluster to test such

**Link to tracking Issue:**
[`6942`](open-telemetry#6942)

**Testing:** `cd receiver/redisreceiver && make mod-integration-test`

**Documentation:** (autogenerated from mdatagen)
Copy link
Contributor

github-actions bot commented Apr 1, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Apr 1, 2024
@atoulme atoulme removed the Stale label Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed receiver/redis Redis related issues
Projects
None yet
Development

No branches or pull requests

6 participants