cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

How do I capture the Severity Level for Database Errors?

genesius_jarom1
Organizer

Hi,

At this DCRUM documentation link is listed the various metrics available.

https://community.dynatrace.com/community/display/...

How do I capture the Severity Level for Database Errors?

Database errors

The number of database errors in the database analyzer:


  • For TDS, which includes Sybase and MS SQL Server, any value
    from the following table is considered an error.
  • For MySQL, if an ERR_Packet is returned, the error count is
    incremented.

An error with a severity level of 19 or higher stops the
execution of the current SQL batch and the error message is written to the error
log.


Errors that can be corrected by the
user:

11: The given object or
entity does not exist.

12: SQL statements that do not use
locking because of special options. In some cases, read operations performed by
these SQL statements could result in inconsistent data, because locks do not
guarantee consistency.

13: Transaction deadlock
errors.

14: Security-related errors such as permission
denied.

15: Syntax errors in the SQL
statement.

16: General errors that can be corrected by
the user.


Software errors that cannot be corrected by the user and
that require system administrator action:

17: The SQL statement caused the database server to run out of
resources (such as memory, locks, or disk space for the database) or to exceed
some limit set by the system administrator.

18: There is a
problem in the database engine software, but the SQL statement completes
execution, and the connection to the instance of the database engine is
maintained. System administrator action is required.

19: A
non-configurable database engine limit has been exceeded and the current SQL
batch has been terminated.


System problems:

20-25: Fatal errors, meaning that the database engine task that
was executing a SQL batch is no longer running. The task records information
about what occurred and then terminates. In most cases, the application
connection to the instance of the database engine also terminates. If this
happens, depending on the problem, the application might not be able to
reconnect.

Thanks in advance for your help.

God bless,

Genesius

2 REPLIES 2

raffaele_talari
Inactive

Hi Genesius,

I'm not aware of any way to capture the severity level...but I leave the last word to the Senior experts! 🙂

Ciao, Raffaele

brett_behm
Newcomer

On the CAS, DB return codes that are unsuccessful are put into 1 of 2 buckets: errors and warnings. These are hard coded in the product and cannot be changed. In the CAS you will just see counts for errors and warning and availability settings allow you to tag each one as a "failure" or "successful" operations. By default errors are tagged as application failures and warnings are considered successful.

Now if you enable ADS reporting and specifically configure this for "error and warning" reporting or all reporting, those exact error messages will show up in an ADS report. For example the TDS severity level is recorded and reported in every TDS error produced. So if you want to see the exact error including its severity (at least for TDS and Sybase), enable ADS and drill down into an error report.