You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In pgwatch2, we monitor server log events like ERROR, FATAL and count their occurences.
This is far too generic and i doubt the usefulness of this information at (e.g. ERROR can be just
a mistyped query or the like).
Instead, i suggest to count the server log events according their SQLSTATE classes. The first
two bytes of an SQLSTATE identifier describes the message class a specific message belongs to (e.g. 53 for insufficient resources). This way we can distuingish specific error conditions and expose them in a more meaningful context.
This discussion was converted from issue #235 on January 09, 2024 14:02.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In pgwatch2, we monitor server log events like ERROR, FATAL and count their occurences.
This is far too generic and i doubt the usefulness of this information at (e.g. ERROR can be just
a mistyped query or the like).
Instead, i suggest to count the server log events according their SQLSTATE classes. The first
two bytes of an SQLSTATE identifier describes the message class a specific message belongs to (e.g. 53 for insufficient resources). This way we can distuingish specific error conditions and expose them in a more meaningful context.
Beta Was this translation helpful? Give feedback.
All reactions