fix(codecs): accept short-form syslog severity keywords in encoder#25731
Merged
Conversation
The Severity enum only accepted full-form names (e.g. "critical",
"emergency", "informational") but the VRL functions to_syslog_severity
and to_syslog_level use short-form names ("crit", "emerg", "info").
This caused severity values to silently fall back to the default
"informational" when short-form keywords were used.
Add strum serialize aliases so the syslog encoder accepts both
short-form and full-form severity names: emerg/emergency, crit/critical,
err/error, warn/warning, info/informational, and the deprecated "panic"
alias.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pront
approved these changes
Jul 1, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The syslog codec's
Severityenum only accepts full-form keywords ("critical","emergency","informational", etc.) but the VRL functionsto_syslog_severityandto_syslog_leveluse short-form keywords ("crit","emerg","info", etc.). When a short-form value reaches the syslog encoder,FromStrparsing fails silently and the severity falls back to the defaultInformational(6).This adds strum
serializealiases so the encoder accepts both forms:emerg/emergency/panic→ Emergency (0)crit/critical→ Critical (2)err/error→ Error (3)warn/warning→ Warning (4)info/informational→ Informational (6)Vector configuration
How did you test this PR?
Extended the existing
test_parsing_logicunit test inlib/codecs/src/encoding/format/syslog.rsChange Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
Notes
@vectordotdev/vectorto reach out to us regarding this PR.pre-pushhook, please see this template.make fmtmake check-clippy(if there are failures it's possible some of them can be fixed withmake clippy-fix)make testgit merge origin masterandgit push.Cargo.lock), pleaserun
make build-licensesto regenerate the license inventory and commit the changes (if any). More details on the dd-rust-license-tool.