Evaluating the sensor error message
Sensor error message occurs when the sensor cannot process the data that is sent back by the probe. Different versions of the sensor error message indicate different processing errors.
Types of sensor error messages
Error: The generic constructor that indicates the sensor can not process the data.
EvalError: Indicates that an error has occurred in the global
RangeError: Indicates that a numeric variable or parameter is outside of its valid range in the sensor.
ReferenceError: Indicates an error occurs when the sensor processing attempts to dereference a variable that has not been declared.
SyntaxError: Indicates a syntax error in the sensor.
TypeError: Indicates that an operand or argument that is passed to a sensor function is incompatible with the type expected by that operator or function.
URIError: Indicates that
decodeURI()are passed invalid parameters in the sensor.
Finding the cause of the sensor error message
To find the cause of this error, you identify the following:
- The error
- The name of the sensor where the error occurred
- The datestamp of the error
- The associated stack trace of the error
To identify the error, the name of the sensor, and the datestamp of the error:
- Navigate to Discovery > Discovery Log
- To find the error, filter on the Level name of Error.
- You can also view the error and the datestamp in the Error Gauge on the Discovery dashboard.
- Note the Created field of the error record.
- This timestamp is used to find the proper stack trace.
- Note the Short Message field of the error record
- This field shows the name of the sensor where the error has occurred.
In the following example, a generic sensor error occurred at in the SMI – Fiber Channel Switch sensor at 4:03 on 10-24-2014.
In the following example, a sensor TypeError occurred in the Windows – Installed Software sensor.
To find the stack trace:
- Navigate to System Logs > Errors.
- Search for the date and time that matches the value in the 'Created field of the error record in the discovery log.
- The Message field of that entry contains the full stack trace of the error.
- The stack trace contains the error message, the sys_id of the script, and the line number where the error occurred.
In the following example, the stack trace shows the following:
- Line 3: The Ci.controller variable is undefined.
Fixing the sensor error message
- Navigate to the module in Discovery that the error occurred.
- In the example, you navigate to Discovery Definition > Script Includes.
- Fix the error.
- In the example, you search for DiscoverySmiFcSwitchSensor in the Name field.