Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Syslog severity number mapping in the example #2091

Merged

Conversation

tigrannajaryan
Copy link
Member

Emergency and Alert were incorrectly ordered (Emergency is was
less severe but it is actually more severe in Syslog).

This fixes the mapping.

Fixes #2042

Emergency and Alert were incorrectly ordered (Emergency is was
less severe but it is actually more severe in Syslog).

This fixes the mapping.

Fixes open-telemetry#2042
@tigrannajaryan tigrannajaryan enabled auto-merge (squash) November 3, 2021 20:04
@tigrannajaryan
Copy link
Member Author

tigrannajaryan commented Nov 3, 2021

docfx action is not feeling well, unclear what the problem is.

@tigrannajaryan
Copy link
Member Author

We have 2 approvals which supposedly should be enough but I still can't merge. Let's get one more approval if possible.

@bogdandrutu bogdandrutu merged commit bcf9820 into open-telemetry:main Nov 4, 2021
@tigrannajaryan tigrannajaryan deleted the feature/tigran/syslogmapping branch March 3, 2022 17:03
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this pull request Oct 31, 2024
Emergency and Alert were incorrectly ordered (Emergency is was
less severe but it is actually more severe in Syslog).

This fixes the mapping.

Fixes open-telemetry#2042

Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should Syslog Emergency map to FATAL instead of ERROR3?
5 participants