ansible/awx

Make Info Metrics more easy to query

Open

#3,781 opened on Apr 29, 2019

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Python (3,333 forks)batch import
Hacktoberfestcomponent:apigood first issue

Repository metrics

Stars
 (13,071 stars)
PR merge metrics
 (Avg merge 24d 6h) (30 merged PRs in 30d)

Description

ISSUE TYPE
  • Bug Report
SUMMARY

Currently awx_system_info and awx_instance_info metrics are returned as labels with values, which makes it difficult to query just the value of one key. As a result, you can't query individual key's for their values in prometheus, for example: awx_system_info{anisble_version}. This has already been fixed for licenses.

We should make the rest of these individual metrics so that they can be individually queried. i.e.: "I am a customer who likes to see my Ansible version and tower version in Dashboard for Tower in Grafana"

ENVIRONMENT
  • AWX version: 4.0.0

Contributor guide

Research direction
Identify all info metrics (awx system info, awx instance info) in the codebase. Examine how license metrics were already fixed for reference. Convert each label encoded metric into separate gauge metrics. Update the Prometheus exporter code and ensure backward compatibility.
Tech stack
python
Domain
backendobservability
Issue type
Bug
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.
Half day
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.
Clear
Prerequisites
PythonPrometheusAWX metrics system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45