Chat now with support
Chat with Support

Foglight for Application Operations 5.9.8 - Dependency Mapping User Guide

Creating a Netstat agent

To create a Netstat agent:
1
In the Configure Dependency Monitoring dashboard, click Create a new agent.
The Create a New Agent dialog box contains the configurable settings for a Netstat agent.
 
* 
IMPORTANT: These settings can be modified later, if needed.
2
Provide the required information about the hosts in the environment that you want to monitor.
•
Scan these hosts — list the hosts that you want the Netstat agent to scan every time it runs. The list can include host names, host IPs, or IP ranges for the hosts to be included in the scanning.
 
* 
NOTE: You can define up to 256 hosts in the agent scanning list through the UI. Larger scan lists may require a custom Agent Manager configuration and additional memory.
•
Exclude these hosts (optional) — list the host names, host IPs, or IP ranges for the hosts that the Netstat agent should exclude from the scan. The exclude list should be used for hosts which have connections to hosts in your scan list, but which are not actual dependencies. Examples may include: backup systems, virus file definition servers, end user subnets.
•
Ignore HTTP (port 80) and HTTPs (port 443) connections — Select to exclude from monitoring the traffic going through ports 80 and 443 of all hosts specified in the Scan these hosts box.
 
* 
NOTE: Ignoring ports 80 and 443 is a convenient way to exclude end users from the dependency model, which is recommended.
3
In the Credentials section, define the agent’s credentials for scanning the selected hosts.
If you have already defined the credentials for the target host list or you want to configure them later, select the Skip credential assignment check box and continue with Step 4.
If you want to use the account the Agent Manager is installed with, select the Use the same credential of the current running client for the above hosts check box and continue with Step 4.
For your convenience, you can define up to two sets of credentials, one for Windows hosts and the other for SSH access.
 
* 
IMPORTANT: The advanced setup view can help you assign credentials in a more granular way.
Provide the following information for each set of credentials:
•
User Name — defines the user account that can log in to the selected hosts and run the netstat command for scanning these hosts.
•
Password and Confirm Password — specify the account password.
•
Domain (for Windows credentials only) — specifies the domain for the selected user name.
•
Description — provides a short description of the credentials and their purpose.
•
Store your credentials in this lockbox — select a lockbox from the available options. A lockbox stores credentials to be assigned to an Agent Manager so that they can be used by all the agents in that Agent Manager.
•
Select the This is a challenge credential check box when you want to simulate a user logging in using a keyboard. This is necessary when the password authentication is disabled on the target hosts.
4
In the Agent Details section:
•
Deploy on client — select the remote client on which you want to deploy the new Netstat agent.
•
Agent name — type a name or a short description for the new Netstat agent.
•
Activate now — select if you want to activate the agent when it is created; clear the check box if you want to activate the agent later.
5
Click Create agent.
The agent package is deployed on the remote client indicated in the settings, then the agent is created. The Configure Dependency Monitoring dashboard is updated to show the newly created agent.
 
* 
IMPORTANT: When you deploy an agent for the first time, the operation may require a few seconds to complete.
Related topics:
•
Activating, deactivating, and deleting an agent
•
Configuring the agent collection schedule
•
Tracking the progress of dependency scans

Activating, deactivating, and deleting an agent

To start or stop the process of collecting dependency data, you can activate or deactivate a Netstat dependency agent instance at any time. An agent instance that is no longer required can be removed.
To activate, deactivate, or delete an agent:
1
In the Configure Dependency Monitoring dashboard, choose the agent that you want to modify by selecting the check box at the beginning of the agent’s row.
 
* 
TIP: To select all agents in the list, select the check box in the Agent Name table heading row.
2
To activate an inactive agent, click Activate on the toolbar.
When the operation is complete, the selected agent starts collecting dependency data and its status changes to Collecting data.
3
To deactivate an active agent, click Deactivate on the toolbar.
When the operation is complete, the selected agent stops collecting dependency data and its status changes to Not running.
4
To delete an agent, click Delete on the toolbar.
The Delete Agents Confirmation Dialog dialog box displays.
a
To delete all agent settings, select the Also delete settings (except credentials) check box.
b
To confirm the deletion, click Delete.
The selected agent is now deleted from the list of agents monitoring the dependencies in your environment.
Related topics:
•
Create a Netstat agent
•
Configuring the agent collection schedule
•
Tracking the progress of dependency scans

Configuring the agent collection schedule

To configure the agent collection schedule:
1
In the Configure Dependency Monitoring dashboard, Collection Schedule column, click the link available for your agent.
2
In the dialog box that appears, fill in the new collection interval and click Save.
The new collection schedule is saved and the settings are applied to the selected agent.
 
* 
NOTE: If a collection schedule is set to a short interval (for example, five minutes), and the agent cannot complete the scan of a large environment, the agent does not start a new data collection until the previous collection is complete.
Related topics:
•
Create a Netstat agent
•
Tracking the progress of dependency scans

Tracking the progress of dependency scans

In the Configure Dependency Monitoring dashboard, Scanning Progress column, when you follow the click to view progress link, the Dependency Progress Tracker dashboard opens.
Figure 2. The Dependency Progress Tracker dashboard
The dashboard includes the following components:
•
Switch Agent drop-down list — use to select the agent whose progress you want to track.
•
Scan selection buttons — First Scan, Previous Scan, Next Scan, Latest Scan, and drop-down list of available scan intervals. Use these options to select the interval of time during which you want to track the agent’s progress.
 
Table 2. Agent Properties view contains agent information
Column Name
Description
Agent Name
Name of the agent selected from the Switch Agent list.
Agent Host
Host on which the agent is deployed.
Completed/Total
Number of hosts included in the scanning list for which the scanning has completed / Number of hosts included in the scanning list.
Start Time
Date and time when the scanning has started.
Status
Status of the operation:
•
Collecting (the agent is running)
•
Idle (the agent is idle)
•
Suspend (the agent has stopped the collection)
Collection Schedule
Data collection interval.
 
Table 3. Scanned tab contains information about the hosts being scanned.
Column Name
Description
Seed Host IP
IP address of the host.
Host Name
Name of the host.
Type
Additional information about the IP/Hostname in the context of the agent setting. Displays the type of host the row represents (seed or reference host). The reference hosts are always children of a seed host in the tree.
Status
Host’s status after being scanned:
•
The host was unsuccessfully scanned . In this case, the information presented in the Message field is related only to that particular host.
•
The host was successfully scanned . In this case, the information presented in the Message field refers to other hosts that are related to this host, that are not in a scan or reference list, or had credential problems.
Duration (Second)
The time spent scanning the host.
End Time
Date and time when the scanning has stopped.
Message
Information collected for that host during the scan.
 
Table 4. Not Scanned tab contains information about the hosts being ignored during the scan.
Column Name
Description
IP Address
IP address of the host.
Host Name
Name of the host.
Status
The host was ignored during the scan . This situation occurs when the host fits one of the following conditions:
•
Discovered, but excluded because it is on the Exclude list
•
Discovered, but not scanned because it is not on a Scan list or on a Reference list
•
It is too far down the Reference list depth
Message
Reason for failing to scan this host.
 
* 
IMPORTANT: You can add ignored hosts to the scanning by selecting their check boxes and clicking Add To Scanning List or Add to Referenced List at the top of the tab. The selected hosts are included in the next scheduled scan as part of the scanning list or referenced list, respectively.
 
Table 5. Failed Scan tab: provides the information about the hosts that the agent failed to scan.
Column Name
Description
IP Address
IP address of the host.
Host Name
Name of the host.
Status
The agent failed to scan the host . This situation occurs when the host fits one of the following conditions:
•
Discovered, but failed due to lack of credentials, or incorrect credential
•
Discovered, but failed due to inability to connect (for example, if SSH is not enabled for this host)
Message
Reason for failing to scan this host (usually credentials issues).
 
* 
IMPORTANT: You can exclude failed hosts from scanning. Select the host and click Add To Excluded List or Add to Global Excluded List, at the top of the tab. The selected hosts are excluded from the next scheduled scan.
To fix the credential issues for a host, click Assign Credentials, at the top of the tab, and follow the instructions in the Configure Credential wizard.
The Netstat agent generates the following types of messages.
 
Table 6. Netstat agent messages.
Tab
Message Text
Message Description
Not Scanned
The Netstat command did not run on the host because of the TCP connection:{1}
{1} represents the more detail reason.
It lists all reason, separated by semicolon:
•
Local processes excluded:{$tcp_connection_summary_list};
•
Local ports excluded:{$tcp_connection_summary_list};
•
Reference ports excluded:{$tcp_connection_summary_list};
•
The TCP connection was not established:{$tcp_connection_summary_list};
The host exceeds the max scanning depth advanced setting:{1}
{1} represents the next scan depth that exceeds the max scanning depth setting from advanced ASP setting.
The host is not in the list:{1}
{1} represents the more detail reason:
The host is not in the scanning list, the private or global excluded host list, or the referenced list:{$tcp_connection_summary_list}
Failed Scan
Failed to create a remote connection from the agent to this host: WINSHELL :
{1},SSH : {1},WMI : {1}
{1} represents connection results for winshell, ssh, and wmi, respectively. The result is one of following:
•
Refused
•
Time out
•
Invalid Credential
•
No Credential
•
Unreachable
•
Offline
Failed to get the netstat command output after the remote connection was
established:{1}
{1} represents netstat execution result. The result is one of following:
•
Cannot get OS type information for this host
•
Unsupported OS type
•
Netstat command output is empty
Unexpected error occurred
Unexpected error occurred while scanning the host.
Related topics:
•
Create a Netstat agent
•
Activating, deactivating, and deleting an agent
•
Configuring the agent properties
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating