Converse agora com nosso suporte
Chat com o suporte

Foglight for Infrastructure 5.9.4 - User Guide

Using Foglight for Infrastructure Monitoring log files with Foglight Log Monitor Monitoring IBM PowerVM environments
Before you begin Managing PowerVM HMC agents Monitoring your PowerVM environment
Advanced system configuration and troubleshooting Reference
Foglight for Infrastructure views Foglight Log Monitor views Rules Metrics
Appendix: Building regular expressions in Foglight

Reviewing frequently asked questions

Foglight for PowerVM™ offers a collection of frequently asked questions that provide quick insight into resource utilization levels for the applications, desktops, user sessions, and the overall infrastructure in your monitored system. The question mechanism is interactive, guiding you to choose a category and specify additional parameters.

You can find the available questions on the FAQts tab of the Infrastructure Environment dashboard.

Figure 49. FAQts tab

On this tab, the Categories pane contains several question groups. Selecting a category shows the questions belonging to that category in the Questions pane. From there, clicking a question shows the answer on the right.

Figure 50. Finding answers

Monitoring a partition or VIOS with Foglight for Infrastructure

If you want to monitor a VIOS or a partition with Foglight for Infrastructure, you can quickly create a Host agent. Foglight for PowerVM allows you to monitor the health of the system infrastructure associated with a monitored VIOS or a partition. For complete information about host agents, see Using Foglight for Infrastructure agents.

a
On the FAQts tab, in the Categories pane, select VIOS or All Questions.
b
In the Questions pane, select Which VIOS are not monitored by Host Agent.
c
In the Which VIOS are not monitored by Host Agent pane, select a VIOS, and click Add VIOS Hosts Monitoring.
a
On the FAQts tab, in the Categories pane, select Partition or All Questions.
b
In the Questions pane, select Which partitions are not monitored by Host Agent.
c
In the Which partitions are not monitored by Host Agent pane, select a partition, and click Add Partition Hosts Monitoring.
The Add LPAR Host - List wizard appears.
3
In the Add LPAR Host - List wizard, on the Agent Manager page, select the Agent Manager that you want to associate with the Host agent you are about to create.
a
Click Agent Manager and select the Agent Manager host that you want to use to associate with the Host agent. The list includes only the Foglight Agent Managers to which the Foglight for Infrastructure agent package is already deployed.
b
Ensure that the Virtual / Guest check box is cleared.
c
Click Next.
The Add LPAR Host - List wizard refreshes, showing the Host List page.
4
In the Add LPAR Host - List wizard, on the Host List page, review the list of VIOS or partition instances that you selected for monitoring.
b
Click Next.
5
On the Credentials Verification page, select one of the following options:
Do not configure a credential: Select this option if you want to configure the credential for this component at a later time. Click Next and continue to Step 8.
Add host(s) to a new credential: Select this option if you want to create a new credential for this component. This option is suitable if none of the existing credentials have the connection details needed to access the new host. Click Next and continue to Step 6.
Add host(s) to an existing credential: Select this option if you want the Host agent to use an existing credential to access this component. This option is suitable if an existing credential has the security data needed to access this component (such as user name and password), but you need to edit its resource mappings to include this component. Click Next and continue to Step 7.
a
On the Credential Type page that appears, select the desired credential type.
b
On the Credential Type page, click Next.
The Credential Properties page appears.
c
On the Credential Properties page, provide the required information. The level of required data depends on the selected credential type. For example, a User Name and Password credential needs a user name and a password, while a Challenge Response credential requires a user name along with a question/response pair.
d
On the Credential Properties page, click Next.
The Credential Name and Lockbox page appears.
e
On the Credential Name and Lockbox page, provide a name to identify the credential, and select a lockbox in which you want to keep the credential. A lockbox can be used to group credentials for access and/or security. The default System lockbox is sufficient for smaller installations.
f
On the Credential Name and Lockbox page, click Next.
The Resource Mapping page appears.
g
On the Resource Mapping page, ensure that the VIOS or partition components that you want to associate with this credential are selected.
h
On the Resource Mapping page, click Next.
The Policies page appears.
i
Optional—On the Policies page, define one or more policies for this credential. A policy defines the number of times a credential can be used, the number of allowed authentication failures, the time range during which the credential is valid, or the length of time the credential data can be cached on the client. For example, you can specify the number of times the credential can be used, or the time period during which it can be used. For complete information about the available credential policies, see the Administration and Configuration Help.
j
On the Policies page, click Next. Continue to Step 8.
a
On the Credential page that appears, select an existing credential that you want the Host agent to use to access this component.
b
On the Credential page, click Next.
The Resource Mapping page appears.
c
On the Resource Mapping page, ensure that the VIOS or partition components that you want to associate with this credential are selected.
d
On the Resource Mapping page, click Next. Continue to Step 8.
8
On the Summary page that appears, review the information about the monitored component, selected Agent Manager, and the credential.
9
Click Finish.
After a few moments, a new host appears on the Hosts dashboard and a new instance of the monitoring Host agent is created. The Agent Creation Successful dialog box appears. Review the information in this dialog box.

 

Advanced system configuration and troubleshooting

This contains platform-specific configuration information for configuring Foglight® for Infrastructure on Windows® when using Windows Management Instrumentation (WMI) or Windows Remote Management (WinRM) for remote monitoring access.

For more details, see the following topic:

Advanced system configuration for WinRM

Even though the local user will now have access to Windows Remote Management (WinRM), not all performance monitoring classes allow non-administrative users to access their instances. Some performance classes will still need advanced configuration for the non-administrative user to be able to perform queries/execute methods on their object instances. To perform the advanced configuration for non-administrative users, make sure to log into the remote machine using the Administrator account.

The advanced configuration for non-administrative users includes the following steps:

The non-administrative users must be added into the Performance Monitor Users group that enables the access to the object instances and the Event Log Readers group that grants the permission for reading event logs.

To add a non-administrative user to the above user groups:

After adding a non-administrative user to the needed user groups, you will see the following result if the user permission is not allowed through SDDL.

To grant the WinRM RootSDDL permission to a non-administrative user:

After setting WinRM RootSDDL for a non-administrative user, log into the remote machine using the administrative user credentials and execute the following command:

You will see the following result, if the non-administrative user does not have the permission to the namespace.

To grant the permission to the namespace for the current non-administrative user:

9
Repeat Step 3 to Step 8 to grant all permissions for Security > Root and Security > Root > mscluster.

Most services data can be collected if the Performance Monitor Users group has been granted the permission to services. If you still fail to collect some service data because of permission issues, on the remote machine, execute the following command where <service_name> is the Service name in the Service Property dialog box:

The permissions of the Built-in Administrator (BA) will appear after executing the above command. Execute the following command to grant the additional permissions, as needed.

The following sample demonstrates how to grant permission to the SCMANAGER service:

3
Add “(A;;CCLCRPRC;;;S-1-5-32-558)” between “D:” and “(A;;CC;;;AU)”, and execute the sc sdset command to grant the permission to the SCMANAGER service. For example, execute the following command:

 

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação