6.4 kmes.config.value.rejected

  • Event type: kmes.config.value.rejected
  • Defined in: kmes.evman
  • Tier: essential
  • Gating: none — every rejected configuration value is recorded
  • Cardinality: once per rejected value

The record that KMES read a configuration value, rejected it, and carried on with what it had. Emitted when the stored value is missing, of the wrong type, or out of range.

Validation is reject-or-keep, never clamp: a valid value is applied and an invalid one is ignored, with the last known-good value retained. That makes this event the only place the divergence is visible — the registry records what an administrator wrote, and this records what KMES is running on. An operator reading only the registry will believe a change took effect that did not.

These records are emitted before the configuration commit and are deliberately not part of the commit decision: a failure to construct one must never roll back a hot-swap that otherwise succeeded.

6.4.1 Fields #

FieldTypePresenceMeaning
config.key.pathstrrequiredThe registry key the reported value lives under, in canonical form.
config.namestrrequiredThe name of the configuration value being reported on, within config.key.path.
config.expected.typeuint.enumrequiredThe registry type the value is required to have.
config.expected.minuintrequiredThe smallest value accepted for this setting.
config.expected.maxuintrequiredThe largest value accepted for this setting.
config.received.kindstr.enumrequiredHow the stored value failed validation.
config.received.typeuint.enumwhen config.received.kind == wrong-typeThe registry type the value actually had.
config.received.valueuintwhen config.received.kind == out-of-rangeThe value that was stored and rejected.
config.valueuintrequiredThe value retained.

Every record also carries the header fields of the envelope, which no payload repeats.

Generated from kmes.evman by pkm/tools/gen-events-book.py. Edit the fragment, not this page.

Edit this page