Skip to content

Doc: Updates IWKB for perf lib errors #501

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.

Sign up for GitHub

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

Merged
LordHepipud merged 1 commit into from
Mar 25, 2022
Merged

Doc: Updates IWKB for perf lib errors #501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions doc/knowledgebase/IWKB000008.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,10 +18,8 @@ The issue on this method is, that even while we only load the `Processor` Perfor

## Solution

At the moment there is no solution available to resolve this issue. Permissions to these counters cannot be granted. Disabling these Performance Counter endpoints is not suitable as well, because it might break different applications and it is also **not** adviced to run the Icinga Agent or checks in `LocalSystem` context for security reasons.
Permissions to these counters cannot be granted individually and disabling these is also not a suitable option. One way to resolve this problem, is to use [JEA Profiles](../130-JEA/01-JEA-Profiles.md) for monitoring or switch to the feature [Forward Checks to Internal API](../110-Installation/30-API-Check-Forwarder.md).

Right now a workaround would be the experimental feature [Forward Checks to Internal API](../110-Installation/30-API-Check-Forwarder.md), which is not yet ready for production.

As Performance Counter libraries are loaded during startup, they will only occur once you start the Icinga for Windows service with this daemon. Every single check executed afterwards will use Performance Counter libraries, but the current shell session has already loaded required components and therefor only access objects we want.
As Performance Counter libraries are loaded during startup within the REST-Api, they will only occur once you start the Icinga for Windows service daemon. Every single check executed afterwards will use Performance Counter libraries, but the current shell session has already loaded required components and therefor only access objects we want.

As a result, no additional errors or warnings are added to the EventLog.