influxdata/telegraf

[inputs.icinga2] differ between handled and unhandled host/service problems

Open

#9,115 opened on Apr 12, 2021

View on GitHub
 (1 comment) (2 reactions) (0 assignees)Go (4,161 forks)batch import
feature requesthelp wantedsize/l

Repository metrics

Stars
 (9,892 stars)
PR merge metrics
 (Avg merge 2d 12h) (136 merged PRs in 30d)

Description

Feature Request

Opening a feature request kicks off a discussion.

Proposal:

In the current version of the icinga inputs plugin, the current state of a host or service will be collected. However, you cannot distinguish between handled and unhandled hosts/services.

Current behavior:

You have only this host/service states:

state - The state: UP/DOWN for hosts, OK/WARNING/CRITICAL/UNKNOWN for services

Desired behavior:

A new tag where you can see if host/service problems are handled or not. You already see it in Icingweb --> Overview --> Tactical Overview, but it would be nice if telegraf can collect these metrics as well. image

Use case:

I want to know how many hosts/services problems I have and how many of them are already handled.

Contributor guide

Research direction
Investigate the Icinga2 plugin code in Telegraf to find where host/service states are collected. Add a new tag or field to indicate if a problem is handled (acknowledged) based on Icinga2 API response properties such as 'downtime depth' or 'acknowledgement'.
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.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
65