Rotating File Logs for Log Actions
(Doc ID 1136635.1)
Last updated on JANUARY 13, 2018
APM - Application Performance Management - Version 6.5.5 to 6.5.4 [Release 6.5] Information in this document applies to any platform.
This only applies to BTM release 6***
Using the Environment Monitor (EM), you can create custom configurations for your agents. One of the available actions you can add to a configuration is the Log action. You associate a Log action with a Log Destination.
A configuration offers four types of custom logging destinations, allowing you to log to:
a SOAP service
the container log (where the Agent sends all of its logging)
a Java program logger (also available on .NET)
a flat file that you specify
(You can read about all of these in the online EM documentation.)
When writing to a flat file, it’s often desirable to rotate the logs to prevent them from becoming too large or to allow for organized archiving. Whereas both container logs and a program logger have built-in rotation facilities, your own flat file does not.
However, it’s possible to implement automatic time-based flat file log rotation through a custom configuration on the Agent. This technote discusses how to do this.
The BTM has a logging policy template, that does allow for file rotation based on size or time, but if you want more control over what gets logged, when during processing it's logged, and the location of the target log file, you'll need to use a custom configuration and implement log rotation through this solution.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!