The 'apache' probe is not gathering metrics.  Also, when configuring the probe in the IM console, many of the metrics show a yellow caution sign as shown in Figure 1.

Figure 1:

When configuring the URL, it does test successfully as shown in Figure 2.

Figure 2:

To get the metric keywords that UIM needs, the URL for apache needs to be:

http://ApacheServerName/server-status?auto

- UIM v8.5.1
- apache probe v1.70

Modify the URL in the apache probe properties to include '?auto' as shown in Figure 3.

Figure 3:

Please consult the documentation on the UIM apache probe for the other requirements:

http://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/apache-apache-http-server-monitoring.html

Ensure that 'Extended Status' is turned on in the apache web server httpd.conf file. For example:

#

# ExtendedStatus controls whether Apache will generate "full" status

# information (ExtendedStatus On) or just basic information (ExtendedStatus

# Off) when the "server-status" handler is called. The default is Off.

#

ExtendedStatus On

Also, configure the /server-status to be allowed from the robot IP address.  

For example in the '/etc/httpd/conf/httpd.conf' file:

#

# Allow server status reports generated by mod_status,

# with the URL of http://servername/server-status

# Change the ".example.com" to match your domain to enable.

#

<Location /server-status>

    SetHandler server-status

    Order deny,allow

    Deny from all

    Allow from <robot_ip_address>

</Location>

In this one  particular case, the customer changed the URL to localhost instead of server name and the metrics started collecting.