There are several monitoring options available to customers:
- Admin Tool
- Discovery log file.
- System State Web Service
- munin plugin
Discovery Log File¶
The engine’s log file is available in the engine’s working directory.named “log”.
The Discovery log file is named
discovery-n.log where n is the log sequence
number, starting at 0. For example, the first log file is named
tail the log file for insight into engine activity.
As of version 2.8.5, the Discovery engine uses the JDK 1.4 logging system. The logging
configuration file can be customized according to this system. The engine’s default logging
configuration file is located in the engine’s
releases directory. To configure custom
logging for a specific instance, copy logging.properties to the appropriate working directory
For more information on engine installation directories, refer to Recommended Installation Directory Hierarchy.
System State Web Service¶
The status of the engine is also exposed as a web service at http://example.com:port/ws/info/system-state which, if running properly, returns:
<?xml version="1.0" encoding="utf-8"?> <?xml-stylesheet type='text/xsl' href='/doc/style/xmlverbatim/xmlverbatimwrapper.xsl'?> <system-state> <running> <true /> </running> <queryable> <true /> </queryable> </system-state>
If the running element’s child has a value of true, then the engine is fully functioning and ready to receive queries.
For more information on the System State web service, refer to System State.
The Discovery Search Engine exposes a number of data points that are of interest on a web service at /ws/statistics. The statistics exposed are transient, all counters will reset when the engine stops.
For more information on using the munin plugin refer to the description of the Statistics web service.