Skip to content

Severity level definition#71

Open
emmuhamm wants to merge 1 commit intodevelopfrom
emmuhamm/severity-levels
Open

Severity level definition#71
emmuhamm wants to merge 1 commit intodevelopfrom
emmuhamm/severity-levels

Conversation

@emmuhamm
Copy link
Copy Markdown
Collaborator

Description

Fixes #56

Add the definition of severity levels for other people to use in the DUNE DAQ.

Its a separate PR cuz I'm sure this needs a wider discussion before we can agree to this.

Type of change

  • Documentation (non-breaking change that adds or improves the documentation)

Testing checklist

N/A

Further checks

N/A

Co-authored-by: Copilot <copilot@github.com>
@emmuhamm emmuhamm self-assigned this Apr 28, 2026
@emmuhamm emmuhamm added the documentation Improvements or additions to documentation label Apr 28, 2026
@emmuhamm emmuhamm linked an issue Apr 28, 2026 that may be closed by this pull request
@emmuhamm emmuhamm requested a review from PawelPlesniak April 28, 2026 09:54
Base automatically changed from emmuhamm/deploy-docs to develop May 8, 2026 13:46
@PawelPlesniak
Copy link
Copy Markdown
Collaborator

It is good to have this written down as a reference point. Some requests. In your example, you use Bad query for logs as an example of an ERROR message, but it is a WARNING message. A better example would be when we have the web proxy enabled.

Also for the CRITICAL example, lets stick to things that relate to our work that is publishable through python. The example you provided relates to a C++ app. I would suggest using "A process died unecpectedly" instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Doc]: FOR DISCUSSION: What do severity levels mean?

3 participants