fix: correct loggly syslog emergency severity#13390
Open
moying2026 wants to merge 1 commit into
Open
Conversation
Author
|
补充一下背景:这个 PR 修正了 loggly 插件和 rfc5424 工具里 syslog emergency 级别的拼写错误(EMEGR → EMERG),同时更新了中英文文档,并补了一个回归测试。本地因为没装 OpenResty,没能跑完整套测试,但改动范围很小,只涉及字符串修正和文档,不影响其他逻辑。麻烦有空时帮忙 review,谢谢。 |
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.
Description
This PR corrects the syslog emergency severity name used by the
logglyplugin and the RFC5424 utility fromEMEGRtoEMERG.EMERGis the standard syslog severity name for severity value0. The current typo makesseverity: "EMERG"fail schema validation and the docs currently advertise the misspelled value.Checklist
logglyseverity enum fromEMEGRtoEMERGapisix.utils.rfc5424severity map fromEMEGRtoEMERGEMERGis accepted and the old misspelling is rejectedTests
git diff --checkmake test TEST_FILE=t/plugin/loggly.t(not run successfully in my local environment because OpenResty is not installed:WARNING: OpenResty not found)