EM 13c: Environment Variable Values are Ignored for File Path Definition for the Log File Metric in EM 13c Cloud Control
Last updated on JUNE 07, 2017
Applies to:Enterprise Manager Base Platform - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
You want to monitor log files on a host with Enterprise Manager (EM) 13.2 Cloud Control (Plug-in Update 1), and you have the same file names for these logs on many servers.
The file paths to these files are different for each server and can be represented by a user environment variable.
For example, you wish to monitor the following file for the character string 'Info':
But, each server has a different path to the 'Server Instance', because the instance name, i.e., PPDB060, changes from host to host and another host may have an instance named PPDB061, for example.
In order to monitor this log using the Log File Monitor metric, you would need to use an environment variable, in this case:
which is defined with a different value for each host as described above.
However, when you create a new Log File Monitor metric in EM 220.127.116.11 Plug-in Update 1 and provide a value for the 'Log File Name' field, prefixed with the environment variable parameter value:
and wait for the metric collection to run (default = 15 minutes), no results are returned.
Instead, you see a Metric Collection Error:
Metrics: Log File Monitor
Error Triggered: Jun 1, 2017 10:42:40 AM
Error Type: Collection Problem
Message: Missing file(s): %ESSPATH%\diagnostics\logs\essbase\essbase\essbase.log
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms