JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Worked recipe

Decide which computer alerts need urgent attention

This recipe compares a general severity rating with separate questions about outages, security, data loss, and payment failures.

Original by Jeroen Erne / NexibeoClassification

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits and license

“11 · Log triage” by Jeroen Erne / Nexibeo. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 Jeroen Erne (https://nexibeo.com, https://completeaitraining.com)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

An error message does not always need someone to wake up, while a warning may describe a serious problem. This recipe asks Jev to interpret computer logs and help separate urgent alerts, work for later, and messages that need no action.

The program asks about the affected component, whether intervention is needed, and several specific consequences. It compares an alert rule based on one severity score with a rule based on questions about outages, security, data, and money. Ordinary software decides when to notify someone.

The specific questions caught more critical examples in the author's sample, but one declined payment still caused an unnecessary alert. Wording must distinguish a single failed purchase from a widespread failure. Grouping repeated messages can reduce requests, but important differences must not disappear.

Key takeaways

  1. Define the consequences that justify waking someone.
  2. Check unnecessary alerts as well as missed emergencies.
  3. Review how repeated messages are grouped before judging only one representative.

Each computer log message is sent to Jev for judgment. Real logs can contain account details, secret credentials, or other private data, so remove or approve such content before sending it. This is the author's small-sample comparison, not a verified production alerting system; JevMade did not run it.

GitHub cookbook · Source reviewed

Read the original guide
More guides →See the experiments →