open-telemetry/opentelemetry-collector

[Metric builder] Add external system states to be used in metric constraints

Open

#12,620 opened on Oct 31, 2022

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Go (2,146 forks)auto 404
cmd/mdatagenenhancementhelp wanted

Repository metrics

Stars
 (7,237 stars)
PR merge metrics
 (PR metrics pending)

Description

Originally suggested by @djaglowski in https://github.com/open-telemetry/opentelemetry-collector/pull/6358#discussion_r1000609067

Add ability to provide optional states of the monitored system that can be used in metric constraints like the following:

some.metric.with_min:
  ...
  constraints:
    min_version: 5.0
some.metric.with_max:
  ...
  constraints:
    max_version: 99.9
some.metric.with_minmax:
  ...
  constraints:
    min_version: 0.1
    max_version: 0.9
some.metric.requires_config:
  ...
  constraints:
    config_settings:
      - replication: enabled
some.metric.with_unusual_constraint:
  ...
  constraints:
    text: Only returned when...

Contributor guide

Research direction
Examine the existing metric builder and constraint system in the OpenTelemetry Collector codebase. Review the linked PR discussion to understand the proposed design for external system states. Identify where state retrieval and constraint evaluation occur.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40