addmi 16-discovery monitoring

© 2009 BMC Educational Services

Discovery Monitoring

Keeping Access In Grade A Condition


Monitoring Discovery Outline

3 Main Aspects

1. Per Run How did the run I scheduled go? Current/Recent Runs

2. Per Credential/Slave How well are my credentials working for me? Credential/Slave usage feedback

3. Current State What are my current access levels like? Discovery Dashboard


Monitoring Per Run


Per Discovery Run

Monitor from the Recent Runs list Discovery > Discovery Status > Recent Runs

Click on the run of interest to see details


Discovery Run Summary

Click through to see a list view of endpoint for that Discovery State Example Shown: No Access


Discovery Run Detailed Reports

Endpoint Access Analysis Useful general starting point

Endpoint Timings Look for performance hotspots

Possible Host Devices Look for Hosts that you don’t yet

have access to

Possible Process to Port Issues Look for hosts that need

lsof/sudo to get connection mapping


Monitoring Per Credential or Per Slave


Per Credential/Slave

Success rate feedback is calculated for all core discovery credentials

Start at the Discovery Tab and then the Credentials second level navigation


Login Credentials Success Rate


Slave Management Success Rate


SNMP Credentials Success Rate


Understanding Success Rate (1)

100% Success: shown in Green

Credential has been selected for Discovery All recent attempts have successfully established a session



Partial Success: shown in Yellow

Credential has been selected for Discovery There were issues with some sessions

Summarised by type of issue



Never Used: shown in Blue

Credential has never selected for Discovery



100% Failure: shown in Red

Credential has been used All attempts have failed

Summarised by type of issue

If the credential has worked in the recent past this will also be indicated This may mean that there has been a recent access change that should

be investigated


What Is Counted As a Failure?

Any failure to establish a Unix or Windows session

Where a session is established but HostInfo or InterfaceList methods do not complete This will prevent a Host node being updated DeviceInfo will already exist as we have a session

Where a session is established with a credential marked as “Become Super User” fails to SU This will be reported as a success and a failure


Investigating Credential Success Issues


Monitoring by Current State


Current State Reporting (1)

There is a specific Discovery Dashboard


Current State Reporting (2)

Reports are also available under the Discovery tab Discovery Reports


Current UNIX and Windows Access

Check to see that the access methods and Windows slaves you expect are in use

Check in Probe sector for access regressions or Hosts without credentials rolled out


Discovery Radar

Classifies the last access to IPs that Discovery thinks are hosts


Discovery Radar - Details (1)

Update [Normal] Host updated via cached

credential

Update [Credential Search] Host updated but several

credentials tried



Access Regression [Credential Failure] Host failed to update as no

credential established a session

Access Regression[Other Failure] Host failed to update as there

were other failures



Unknown Host[Credential Failure] No Host was created as no

credential established a session

Unknown Host[No Credential Available] Host failed to update as there

were other session failures


Further Resources

Online Documentation: http://www.tideway.com/confluence/display/81/Documentation

Tideway Foundation

Version 7.2

Documentation

Title

addmi 16-discovery monitoring

Technology