Traverse severity mappings - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Traverse severity mappings - Connect IT Community | Kaseya

QUESTION
What are the numeric/hex codes for Traverse severities?

RESOLUTION
Traverse has a number of entities, such as as test, device, container, etc. depicted with severities with a specific numeric code and color.

The numeric codes as stored in the database are as follows:

* Means an account or device is not configured. Mainly used for status
UNCONFIGURED = 0x00000008;

* Suspended severity. 128 in decimal
SUSPENDED = 0x00000080;

* OK is 2048 in decimal
OK = 0x00000800;

* Transient severity. 16384 in decimal.
TRANSIENT = 0x00004000;

* Unknown severity. 32768 in decimal.
UNKNOWN = 0x00008000; (in the Traverse web user interface, this will appears as -1)

* Unreachable severity. 524288 in decimal.
UNREACHABLE = 0x00080000;

* WARNING is 8388608 in decimal.
WARNING = 0x00800000;

* CRITICAL is 134217728 in decimal.
CRITICAL = 0x08000000;

* FAIL is the state that occurs when the test failed and no test values was returned. 1073741824 in decimal.
FAIL = 0x40000000; (will appear as red in the Traverse web user interface)

Note:
The Traverse web user interface raw data tabular view as also the result.list command will map the database values for UNKNOWN, etc. to -1, -2, etc.

APPLIES TO
All Traverse versions

REFERENCE
-