Skip navigation

ADDM: Make failures more understandable - perhaps include Severity

score 235
You have not voted. Product Team Review

ADDM: Make failures more understandable so that Administrators can focus on the important issues.

We are experiencing thousands of script errors (see table below) - during both Standard and Additional Discovery.  Currently, I don't know which failures are important and which ones I should ignore.  Perhaps ADDM should have a a Severity level (CRITICAL, WARNING, INFO) for each failure-reason, so that the ADDM Administrator knows what is important and what to focus on.  For example, I don't understand the following failure reasons:

 

  • During the standard discovery for UNIX, there is always a NoAccessMethod failure for getServices and getVirtualMachines.  So should this be a different error?  Maybe a different colour or severity?  Because it is not something that the Administrator should necessarily try and fix.   How would you fix it anyway? - if you thought it was important?
  • What actually does NoAccessMethod mean? NoAccessMethod appears to be used in two scenarios:  a) There is a real permission or credentials problem.  b) ADDM does not have a discovery method configured.  Would it not be sensible to have two separate failure-reasons for these two scenarios?  The ADDM Administrator can't change the product so does not need to know about (b).
  • What does this failure reason mean?  Request for information not part of the consolidated data (see query below).
  • What does this failure reason mean?  TRANSIENT_CallTimedout (see query below).
  • What does this failure reason mean?  BAD_PARAM_WrongPythonType (see query below).
  • Some failures such as NoSuchItem are not really failures.  ADDM is just poking around looking for things. So these should be INFO - or hidden from the Administrator because they can be ignored.

 

·         I am not sure that a Severity code is the correct way to make the failure reason more meaningful – but the product should make it crystal clear to the Administration what he/she should fix.  I leave it to you to decide what is the best way to implement this requirement.  Currently, it is just too confusing for the poor administrator (or maybe I am just too stupid).

 

Sample Query:

 

SEARCH DiscoveryAccess

WHERE

_last_marker

AND state = 'Finished'

EXPAND DiscoveryAccess:DiscoveryAccessResult:DiscoveryResult:

WHERE

failure_reason

SHOW

failure_reason, kind(#) AS "Discovered Item"

PROCESS WITH countUnique(0)

 

Result

 

Failure Reason

Discovered Item

Node Count

NoSuchItem

DiscoveredRegistryValue

49237

NoSuchDevice

DeviceInfo

36824

NoAccessMethod

DiscoveredCommandResult

27272

NoAccessMethod

VirtualMachineList

11078

NoAccessMethod

HBAInfoList

10774

NoSuchItem

DiscoveredFile

5812

Request for information not part of the consolidated data

DeviceInfo

4308

NoAccessMethod

NetworkConnectionList

2389

NoAccessMethod

DiscoveredFile

2322

NoAccessMethod

ServiceList

694

NoAccessMethod

FileSystemList

482

NoAccessMethod

DiscoveredRegistryValue

446

NoAccessMethod

DiscoveredWMIQuery

363

Request for information not part of the consolidated data

DiscoveredFile

358

NoAccessMethod

DiscoveredMACAddresses

253

NoSuchItem

RegistryListing

141

NoSuchItem

DirectoryListing

100

Endpoint has no available scan window or is in an excluded range

DeviceInfo

84

NoSuchItem

DiscoveredWMIQuery

66

User cancelled request

DeviceInfo

64

NoAccessMethod

RegistryListing

49

Request for information not part of the consolidated data

DiscoveredWMIQuery

45

NoAccessMethod

DiscoveredPackages

43

NoSuchItem

DiscoveredCommandResult

39

NoAccessMethod

ProcessList

34

Request for information not part of the consolidated data

DiscoveredCommandResult

32

NoAccessMethod

DiscoveredIPAddressList

28

NoAccessMethod

DirectoryListing

27

NoAccessMethod

DiscoveredPatches

25

No credentials

DiscoveredMainframeList

21

Request for information not part of the consolidated data

DiscoveredRegistryValue

18

NoAccessMethod

DiscoveredNetworkInterfaceList

18

TRANSIENT_CallTimedout

DeviceInfo

7

BAD_PARAM_WrongPythonType

DiscoveredPackages

3

TIMEOUT_CallTimedOutOnClient

DiscoveredRegistryValue

2

UNKNOWN

DeviceInfo

1

TIMEOUT

DeviceInfo

1

Request for information not part of the consolidated data

RegistryListing

1

NoAccessMethod

InterfaceList

1

Execution Failure

DeviceInfo

1

BAD_PARAM_WrongPythonType

ServiceList

1

BAD_PARAM_WrongPythonType

HBAInfoList

1

Comments

Vote history