This section provides answers to the following frequently asked questions (FAQs) about the SolGeneos Agent configuration and operation.
- Can the sampling rate be less than 30 seconds?
- Why do obsolete data views show up in Active Console after changing the view name?
- How do I create dynamic views?
- Solace rules in the include file do not work when included in the gateway configuration
- Why do I get duplicate log entries in solgeneosagent.log?
- Why is my samplingStatus in Active Console not updated when the agent stops?
- Why do I get error code 102 (HOST_NOT_TRUSTED) when running the agent?
A monitor’s sampling rate is required to be 30 seconds or greater because smaller polling interval may impact the router performance and therefore the agent’s performance. Sampling rate can be set to a value below 30 seconds if:
- the agent is running in development mode for testing purposes
- the monitor is doing low performance impact queries, such as
ServiceStatusMonitor, which do not send SEMP requests to the router, but instead simply gather statistics
To run the agent in development mode, add “
-DdevMode=true” to the agent’s VM startup option.
To allow a monitor to have a sampling rate less than 30 seconds even when the agent is running in production mode, override
getSamplingRateFloor() method in monitor class to return a value other than 30. Caution must be exercised when overriding this method because the agent and the router’s performance could be affected.
If a data view with certain name is already added to a gateway through NetProbes, changing its name, group header, sampler, and managed entity will not cause the view removed from the gateway. The only way to remove it is to restart the NetProbes.
SolGeneos Agent provides a default implementation of the
View interface called
BaseView. All the static views configured through monitor properties are loaded as
BaseView objects. Monitor developers can call the
BaseView constructor to create views on the fly to create new view instance, and can add/remove them to/from the monitor’s
viewMap by using the following monitor methods:
Solace rules do not work from an include file, but they will work if they are part of the top level configuration.
- Open up the gateway configuration editor. You should see the configuration Gateway > Includes > solace_include.xml > Gateway.
- Open up the Actions folder (Gateway > Includes > solace_include.xml > Gateway > Actions), right-click the Email action, and select Copy.
- Select the Actions folder under Gateway > Actions.
- If prompted to “Create Actions”, select Yes.
- Paste the “Email” action.
- Copy the “Solace” folder under Gateway > Includes > solace_include.xml > Gateway > Rules, and paste it under Gateway > Rules.
This may be due to log4j’s appender additivity feature. Basically, each enabled logging request for a given logger is forwarded to all the appenders in that logger, as well as the appenders higher in the hierarchy. In other words, appenders are inherited additively from the logger hierarchy. For example:
The warning log output by a class under
solgeneosagent are forwarded to file appender
A1 twice, which results in duplicate log entries in the log file.
There are two ways to avoid the problem:
- Remove append
solgeneosagentlogger. This way, the logger inherits the logger appender
- Add the following line to disable additivity:
This problem could occur if you override the
reportView method in your monitor implementation but forget to call
checkSignedIn method in the
NetProbeService class before updating the data view.
If you get error code 102 (HOST_NOT_TRUSTED) when running the agent, that means you probably configured “Trusted API Hosts” on the NetProbe, and the hostname where the agent is running on is not in that list.