Top 10 Agent parameters

Agent configuration parameters
The main file on the Agent side of things with configuration parameters is the emd.properties file. This file is located in the <EMHOME>/sysman/config directory.
A lot of parameters are quite useful in an enterprise environment. Just to hi-light some of these, I've compiled a list of 10 common parameters that can get potentially changd and tweaked.

The EMHOME directory is the directory the Agent will use for all files it needs at runtime. The value of that directory can be obtained by issuing this command:

$ emctl getemhome

The Countdown...

10. EMAGENT_PERL_TRACE_LEVEL
Use this parameter in combination with the
All PERL metrics scripts the Agent executes can be told to provide more tracing details in the emagent_perl.trc file with this parameter.
The default setting for the PERL tracing is WARN

9. EMD_URL
The URL the Agent will use to identify itself with. This is the unique identifier the OMS and repository will use to contact this Agent. The value of this parameter is determined at install time, and should never be changed afterwards.
The name of the Agent (oracle_emd target) should match the host and port part of this URL.
If the Agent is secured, both this EMD_URL and REPOSITORY_URL parameter should both be using the HTTPS URI.

8. enableMetricBrowser
A boolean flag to indicate whether or not the extra listener to display and show the metrics of the Agent is enabled or not. This is a debugging feature designed to check and verify on the Agent metrics.
Under normal conditions, this extra http listener should not be enabled: It uses extra resources of the Agent, and can also consume extra incoming connections, depending on the number of people accessing the metric browser.
The default value for this parameter is FALSE.

7. MaxInComingConnections
The maximum number of incoming concurrent connections from an OMS the Agent will handle. If the OMS tries to establish more connections, the extra requests will have to wait until one of the active ones terminates.
The default value for this parameter is 25. This value can be increased if more than 25 monitored targets of the same type discovered. Increasing this value beyond 50 is not recommended.

6. proxyHost / proxyPort / dontProxyFor
These three parameters should be used together. They control the proxy settings the Agent will use for the monitoring operations. Typically beacons will be accessing URL and webpages outside the scope of the local monitoring. To allow these web operations to complete successfully, these proxy parameters can be used.

5. RemoteAPITimeout
The amount in seconds the Agent will wait for a response before timing out a command send to the OMS. Every command the Agent sends (an API call to the OMS) should return within this time period.
On a busy system, with thousands of Agents, and several OMS machines active, this value can be increased if there is evidence found of timeout failures.
If the Agent times out an operation, a message like this will be written in the emagent.trc file:

The remote api of type has timed out
Increasing it above 10 minutes (600 seconds) is not recommended.
Default value is 300 seconds (5 minutes)

4. REPOSITORY_URL
The URL the Agent will use to initiate contact with the OMS. This needs to point to a valid address of either the OMS itself, or an SLB if there are several OMS machines in an HA-deployed infrastructure.
If the Agent is secured, both this URL and EMD_URL parameter should both be using the HTTPS URI.

3. REPOSITORY_PROXYHOST / REPOSITORY_PROXYPORT
And also: REPOSITORY_PROXYPWD, REPOSITORY_PROXYREALM, and REPOSITORY_PROXYUSER.
All these parameters control the proxy behavior for the Agent when talking to the OMS. These parameters are ONLY used all the communication based on the REPOSITORY_URL, and are not used for the monitoring of targets (eg: Beacons)

2. TrcFileMaxRolls / TrcFileMaxSize
The Agent will rotate the trace files based on these settings. After a certain size is reached (TrcFileMaxSize), the Agent will roll-over the active trace file (emagent.trc) to emagent.trc.1, and decrement the numbers of any existing emagent.trc.<num> upto the maximum allowed number of files (TrcFileMaxRolls).
If the maximum number of trace files is reached, the oldest one (emagent.trc.5 by default) will be removed prior to rolling-over the current trace file.
The same applies for the Agent log files. Those files can be controlled with these parameters: LogFileMaxRolls and LogFileMaxSize.
The default values for these files are 256Kb per log/trace file (MaxSize), with a maximum of 5 files (MaxRolls) kept before removing the oldest one.

1. tracelevel.
This is not exactly a single parameter, but all logging and tracing settings are controlled by this one set of parameters.
All out-of-the-box tracing should be done using the default value of 'WARN'. Only when debugging or investigating an issue, should this level be changed, and only for the duration of the testing/debugging.

Comments:

Hi, This post is very informative! Can you speak about the Upload parameters, like upload backoff percentage, and upload timeout? I have a lot of agents that communicate to the OMS over a very slow network, and there is competition from other software using that network. When it is time for the agents to do an upload they time out and go into "Agent Unreachable" Thanks, Pedro

Posted by Pedro on March 14, 2010 at 10:48 AM PDT #

Great rundown! Would love to see this as a part of the agent templates to push out properties (like pushing out a template for monitoring) across all 3000+ agents :)

Posted by Courtney Llamas on March 24, 2010 at 11:02 PM PDT #

A little known fact about 10gR5 is, that there is a new EMCLI command that allows the setting and changing of Agent properties: $ emcli set_agent_property -agent_name agent.acme.com:3872 -name=UploadInterval -value=15 And granted that it's not like a template that you can roll it out to thousands of machines at once, but it does give you the flexibility to change Agent properties from a central location. But wrap a shell script around it to set properties for multiple Agents, and you have a solution to make changes from a central location to multiple Agents

Posted by werner.de.gruyter on April 05, 2010 at 05:47 AM PDT #

I truly appreciate you taking the time to post this. I really liked reading it and am looking forward to more posts from you! Keep 'em coming.

Posted by cheap wow gold on August 02, 2010 at 12:48 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Latest information and perspectives on Oracle Enterprise Manager.

Related Blogs




Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
3
5
6
7
9
10
11
12
13
14
15
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today