RFC 5674: Alarms in Syslog
In plain English — editorial summary, not part of the RFC
This document describes how to send alarm information in syslog. It includes the mapping of ITU perceived severities onto syslog message fields. It also includes a number of alarm-specific SD-PARAM definitions from X.733 and the IETF Alarm MIB. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5674
- Published
- October 2009
- Authors
- S. Chisholm; R. Gerhards
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5675Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG MessagesCurrent
October 2009
- RFC 5676Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) NotificationsCurrent
October 2009
- RFC 6632An Overview of the IETF Network Management StandardsCurrent
June 2012
- RFC 9940Some Key Terms for Network Fault and Problem ManagementCurrent
April 2026
- RFC 5848Signed Syslog MessagesCurrent
May 2010
- RFC 6587Transmission of Syslog Messages over TCPCurrent
April 2012
- RFC 9662Updates to the Cipher Suites in Secure SyslogCurrent
October 2024
- RFC 5693Application-Layer Traffic Optimization (ALTO) Problem StatementCurrent
October 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?