Icinga / Icinga/icinga-powershell-plugins

Feature request - more thresholds for Invoke-IcingaCheckPerfcounter

Open
#383 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
55
Forks
30
PR merge metrics
No merged PRs in 30d

Description

With Invoke-IcingaCheckPerfcounter it is possible to specify an array of perfcounters to be checked but only one warning and one critical threshold. It would be great if you can specify individual thresholds for each checked perfcounter.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Invoke-IcingaCheckPerfcounter entry point and inspect how its warning and critical thresholds are applied to the perfcounter array. Done means each checked perfcounter can use its own warning and critical thresholds while existing single-threshold behavior remains supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.