Description
Join validated RFC syslog facility 0–23 and severity 0–7 into the numeric priority, without message serialization.
Syslog PRI combines a facility code and severity code in one integer: priority = 8 × facility + severity. The integer is framed in angle brackets at the beginning of a syslog message; a PRI token is only one part of that message.1
Join validated RFC syslog facility 0–23 and severity 0–7 into the numeric priority, without message serialization.
When to use this tool
Use this tool to join validated RFC syslog facility 0–23 and severity 0–7 into the numeric priority, without message serialization.
How to use the tool and how it works
- Enter facility, severity using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.priority. Use the ordering, boundary rules and absence conditions described below.
Require facility from 0 through 23 and severity from 0 through 7, then return 8 × facility + severity.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| facility | Syslog facility integer 0–23. | A finite safe integer within the operation’s stated bounds. |
| severity | Syslog severity integer 0–7. | A finite safe integer within the operation’s stated bounds. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.priority | Numeric syslog priority 0–191. |
{
"input": {
"facility": 20,
"severity": 5
},
"output": {
"result": {
"priority": 165
}
}
}Limitations and assumptions
- These are numeric facility/severity codes; names and application-specific labels are not resolved.
- Structured log records have id, time, source, level, message and sequence fields. time is a finite caller-defined numeric scale; sequence is an integer from 0 through 1,000,000,000,000. Use the same time units for windows and gap edges.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Keep original record order and provenance alongside summaries. Sort, partition by source or normalize aliases explicitly before applying a rule that depends on those choices.
References
-
RFC 5424: The Syslog Protocol — RFC Editor
-
Tool behavior and example: Syslog Priority Component Join — tool.io
Similar or alternative tools
- Syslog Priority Component Split
Split a validated syslog priority integer into facility and severity bit-field values.
- Syslog Priority Token Formatter
Parse or format one complete RFC 5424 syslog priority token in the 0–191 range; no full message parsing.