ch04 preprocessing: add Check for not supported value and error handlers - #401
Open
WMP wants to merge 1 commit into
Open
ch04 preprocessing: add Check for not supported value and error handlers#401WMP wants to merge 1 commit into
WMP wants to merge 1 commit into
Conversation
…dlers Documents how "not supported" items (and "unknown" triggers) generate internal events that bloat the events/event_tag tables and overload the housekeeper, and how to tame the flood with the "Check for not supported value" preprocessing step plus error handlers (Custom on fail -> Discard value). Includes real examples (virtual network interfaces, empty SNMP slots, Prometheus pattern on vanished pods) and notes LLD filters as the cleaner first line of defence. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new subsection "Check for not supported value and error handlers" to
the preprocessing page (
ch04-zabbix-collecting-data/preprocessing.md).The chapter already lists Check for not supported value among the available
preprocessing steps, but never explains it, and error handlers (Custom on fail)
are not documented anywhere in the book. This fills that gap.
What it adds
unsupported agent key) becomes not supported, and how that — together with
triggers going to unknown — generates internal events that bloat the
events/event_tagtables and overload the housekeeper.Set error to.
Check for not supported value → Discard valueto stopa not-supported flood at the source.
argument on
/sys/class/net/<if>/speed, empty SNMP hardware slots returninggenError, and aPrometheus patternstep failing when the source object(e.g. a pod) disappears (handled via the step's own error handler, since the
collection itself succeeded).
caution that discarding errors hides them, so it should be used deliberately.
Why
These steps are the standard, supported way to keep a large environment's
database from filling with internal-event noise, yet they are easy to miss.
Documenting them with concrete examples makes the behaviour discoverable.
Notes
###subsection,!!! tipadmonition, ~80-column wrapping). One file changed; no images required.
Sources
https://www.zabbix.com/documentation/current/en/manual/config/items/preprocessing
https://www.zabbix.com/documentation/current/en/manual/config/items/item
https://www.zabbix.com/documentation/current/en/manual/config/events/sources
https://www.zabbix.com/documentation/current/en/manual/discovery/low_level_discovery
generating millions of internal events/day from virtual or absent entities).