Feature resources

The Feature Resources functionality under Admin > Resources > System Performamce can be used to manage Plixer Scrutinizer feature sets, as an alternative to individually enabling/disabling FA algorithms and alarm policies via their respective configuration views.

The page’s main view lists all available feature sets, alongside the following details:

  • Current state (green: active, grey: inactive)

  • Importance

  • Number of active alarms indicating resource issues for the feature set

  • Expected CPU core usage per collector

  • Expected RAM usage per collector

  • Number of FA algorithms associated with the feature set

  • Number of alarm policies associated with the feature set

Users are also able to toggle between graphs showing algorithms, policies, CPUs, or RAM per feature set.

Activating/deactivating feature sets

To allow teams to better adapt Plixer Scrutinizer’s functions to monitoring and resource requirements, related FA algorithms and their associated alarm policies can be deactivated/disabled by feature set.

Clicking on a feature set name opens the information tray, where it can be activated or deactivated via a toggle. All FA algorithms and alarm policies included in the feature set are also listed in this tray.

Important

Deactivating services may result in loss of functionality and/or other issues. Contact Plixer Technical Support for assistance.

Low resource fallback modes

When the total expected resource utilization for all enabled feature sets results in the current allocations falling below the recommended values for the observed exporter count and flow rate, Plixer Scrutinizer can automatically pause certain functions as low resource fallback.

There are two low resource fallback modes that can be enabled:

  • LRF_mode_pauseFeatureSets - Pause feature sets before pausing exporters

  • LRF_mode_pauseExporters - Pause only exporters

When low resource fallback becomes necessary, feature sets are paused based on their importance value (lowest first, 100 = never paused).

Features and/or exporters will automatically be resumed when the configured CPU core and RAM allocations can support additional computational load.

Hint

Regularly check the state of the server health (leftmost) virtual LED in the web interface admin views. As long as it remains green, features and/or exporters will not be paused. While in this state, Plixer Scrutinizer will also continuously attempt to resume paused feature sets.

Additional low resource fallback settings

The following settings under Admin > Settings > Collector Settings can be modified to further customize low resource fallback behavior:

  • Cooldown period before pausing the next feature set or group of exporters

  • Number of exporters to pause or resume as a group/chunk

  • Flow rate multiplier/percentage for accommodating brief, recoverable spikes