Severity
Severity is an assessment or classification of how serious or impactful an issue, event, condition, or finding is, often expressed as an ordered level.
100 SQL Server Mistakes and How to Avoid Them
An error severity level is a SQL Server classification indicating the informational, user-correctable, administrative, or fatal nature of an error.
- How it is used
- Guides error-handling decisions by distinguishing informational, recoverable, administrative, and fatal SQL Server conditions.
- How deep it goes
- Classifies all 25 levels and explains TRY..CATCH behavior, error logging, and THROW’s fixed level without detailing engine internals.
- Examples
- Uses invalid object names, foreign-key failures, duplicate keys, custom messages, and a sales-order procedure to illustrate severity.
- What you can do after
- Evaluate/understand which SQL Server errors can enter CATCH, need administrative action, or may be fatal.
Read how 100 SQL Server Mistakes and How to Avoid Them explains severity →
Acing the CCNA Exam: Volume 2 Advanced Networking and Security
A Syslog severity level is an ordinal classification of event importance that controls which Syslog events are logged or transmitted.
- How it is used
- Controls which Syslog events reach consoles, VTY lines, buffers, and Syslog servers during monitoring and troubleshooting.
- How deep it goes
- Defines all eight IOS levels, gives operational examples, and shows threshold commands, but defers detailed debug operation.
- Examples
- Uses LINK-3-UPDOWN, SEC_LOGIN-5-LOGIN_SUCCESS, LINK-5-CHANGED, and spanning-tree debug output as concrete severity examples.
- What you can do after
- Configure and verify Syslog thresholds for each destination while recognizing severity values in IOS messages.
Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains severity →
Azure Security
Alert severity is a classification indicating the urgency and assessed likelihood or impact of a security alert.
- How it is used
- Prioritizes Defender for Cloud security alerts for investigation and notification routing.
- How deep it goes
- Defines four alert levels with threat examples and relates them to dashboard triage; it does not prescribe full investigation procedures.
- Examples
- Uses credential-theft tooling, unusual-location sign-ins, routine log clearing, and medium-or-higher email routing.
- What you can do after
- Operate/configure alert notification thresholds and evaluate which Defender for Cloud alerts warrant investigation first.
The Art of Code
A log severity level classifies the importance or urgency of a log record for filtering and routing.
- How it is used
- Uses severity to filter and route log records appropriately across development, production, and monitoring environments.
- How deep it goes
- Defines common levels and their filtering role, but does not detail a formal severity hierarchy or routing configuration.
- Examples
- Shows Java SLF4J ERROR statements for invalid numbers and date parsing, including contextual values and exceptions.
- What you can do after
- Apply severity via SLF4J logging statements that preserve useful errors while filtering less important records.
Troubleshooting Java, Second Edition
Severity is a classification of how seriously an application event or condition affects operation.
- How it is used
- Uses severity to prioritize investigations, raise alarms, and control which application events are stored.
- How deep it goes
- Defines four levels and demonstrates configuration and output, but does not develop a broader severity taxonomy.
- Examples
- Demonstrates Error, Warn, Info, and Debug through Java logging calls, Log4j configuration, and digit-extraction output.
- What you can do after
- Configure Log4j severity thresholds and interpret whether output represents critical, handled, routine, or diagnostic activity.
Read how Troubleshooting Java, Second Edition explains severity →
The Design of Web APIs, Second Edition
Severity is a classification indicating the seriousness or urgency of a rule violation or diagnostic finding.
- How it is used
- Guides readers from detected API guideline violations toward the appropriate response and remediation.
- How deep it goes
- Explains severity choices, rule splitting, and overrides, but stops short of defining a universal priority policy.
- Examples
- Uses a camel-case query parameter warning, separated search-parameter rules, and imported rules whose severity is overridden.
- What you can do after
- Configure Spectral rules with meaningful priorities, precise messages, and context-sensitive overrides.
Read how The Design of Web APIs, Second Edition explains severity →
Think Like a CTO
Severity is the degree of harmful impact or consequence associated with an issue or finding.
- How it is used
- Uses severity to prioritize corrective effort, failure learning, and the ordering of due-diligence findings.
- How deep it goes
- Explains consequence-based prioritization and diagnostic questions, but stops short of defining a formal scoring scale or severity matrix.
- Examples
- Uses recurring failures, client-specific issues, seasonal downtime, repeated actors, and database failure with power loss.
- What you can do after
- Evaluate findings by consequence and choose proportionate corrective effort or business-continuity investment.
Related concepts
- syslog messagepart of · A Syslog message is a structured event record generated by a device or one of its services to report an occurrence or status change.
- logging levelequivalent to · A logging level is a severity or verbosity classification or setting that determines which log messages a logging system processes, emits, or retains.
- logging consoleconfigured by · logging console is a Cisco IOS command that enables console logging and optionally sets its minimum event severity threshold.
- security alertconfigures · A security alert is a notification or record indicating that observed activity may threaten a system’s security or constitute a security incident.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.