Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Archive > 2017December18 - Deletes > Trap message dispays hex encoded string

Trap message dispays hex encoded string

Table of contents
Created by Gary O'Donovan, last modified by Kevin.Swinson on Dec 18, 2017

Views: 766 Votes: 0 Revisions: 8

Overview

This article details the reason for trap messages being displayed in hex.

Environment

All NPM versions

Detail

Normally string variables (octet string) included with a trap message are displayed/rendered as ASCII characters when processed by the Traverse Message Handler.  However, if a string contains any non-printable characters, then the string is displayed as hex encoded bytes.

Last modified

Tags

Classifications

Public