Fredhopper offers monitoring points via HTTP and command line. For the RESTful status messages via HTTP, each monitoring point can be accessed using the paths below at http://<SERVERNAME>:8177. For the command line, the Deployment Agent provides access to all control points in the system. The following table contains a selection of the monitoring actions:
| Operation | HTTP access point | Command line access point | Note |
|---|---|---|---|
| Verify that Deployment Agent is running | http://<SERVERNAME>:8177 | curl -s --connection-timeout 20 http://<SERVERNAME>:8177/environment -l | grep "200" | grep "OK" | The Deployment Agent should always be active and must be the first Fredhopper process started. The HTTP access point needs to provide Status 200 OK if the DA is running and available. |
| Verify that process is running/stopped | /instance/<INSTANCE>/process/<PROCESSNAME>/verb/status | bin/deployment-agent-client invoke <INSTANCE> <PROCESS> status | Checks the status (RUNNING, STOPPED) of all known processes (kitchen, qserver, xmlloader, searchindexer, treebuilder, syncserver, syncclient) with a given instance. |
| Verify that qserver is active | /instance/<INSTANCE>/process/qserver/monitor/mbeans.fredhopper.com:type=QServer/QServerState | bin/deployment-agent-client get-jmx <INSTANCE> qserver mbeans.fredhopper.com:type=QServer QServerState | If "Active" is returned, the server is available. "Inactive" indicates the server is booting or shutting down. |
| Verify the role of the qserver | /instance/<INSTANCE>/process/qserver/monitor/mbeans.fredhopper.com:type=QServer/DeploymentServerRole | bin/deployment-agent-client get-jmx <INSTANCE> qserver mbeans.fredhopper.com:type=QServer DeploymentServerRole | Indexer should return 'staging', live instances should return 'live' |
| Verify that search is available for specific universe-locale combination | /instance/<INSTANCE>/process/qserver/monitor/mbeans.fredhopper.com:engine=<UNIVERSE>-<LOCALE>,server=Server,type=Search/Alive | bin/deployment-agent-client get-jmx <INSTANCE> qserver mbeans.fredhopper.com:engine=<UNIVERSE>-<LOCALE>,server=Server,type=Search Alive | This will return "true" if a search is configured and available for the given universe-locale combination. |
| Number of items currently loaded in a specific instance | /instance/<INSTANCE>/process/qserver/monitor/mbeans.fredhopper.com:type=ItemStore/ItemCount | bin/deployment-agent-client get-jmx <INSTANCE> qserver mbeans.fredhopper.com:type=ItemStore ItemCount | This will return the total number of items currently loaded, including all variants. |
| Number of items in the navigation index for specific universe | /instance/<INSTANCE>/process/qserver/monitor/mbeans.fredhopper.com:type=Tree,universe=<UNIVERSE>/NavigationIndexSize | bin/deployment-agent-client get-jmx <INSTANCE> qserver mbeans.fredhopper.com:type=Tree,universe=<UNIVERSE> NavigationIndexSize | This will return the total number of items in the navigation index for the universe. Most interesting to monitor is the number of items in the products universe. |
| Number of items in the search indices for specific universe/locale combination | /instance/<INSTANCE>/process/qserver/monitor/mbeans.fredhopper.com:engine=<UNIVERSE>-<LOCALE>,indextype=<INDEX>,server=Server,type=Search/Size | This will return the number of items per universe-locale-index type combination. Available index types are
|
|
| Check if indexer and all associated live servers are up and running | not available | bin/chk-up <INSTANCE> | Checks every 20 seconds if indexer qserver and all its associated live qserver are up and are returning items. The output is: yyyymmdd-hhmmss <INSTANCE> roundtriptime host port nr-of-items The tool uses the REST interface. An alerts is given if a qserver is not responsive |
| Check if FAS query returns a correct result | not available | bin/ws-query <HOST> <PORT> "<FAS_QUERY>" | The FAS query can be any FAS query url argument. The output is every 30 seconds: yyyymmdd hh:mm:ss qid nr-items page-time round-trip-time query Example: bin/ws-query localhost 8180 "fh_location=//instance01/en_US" 20100507 10:24:20 4081 7612 0.06 0.303 //instance01/en_US |
| Check latest publishing | not available | bin/chk-publishing <INSTANCE> | Shows timestamp and size of latest published business.xml. |
| Check current index | not available | bin/chk-valid-index <INSTANCE> | Checks the index of the given <INSTANCE> and all its sub indexes against minimal number of items configured with the MINITEMS setting in config/fasrc. It will exit with error code if the index is not valid. You can check this on the indexer to prevent that bad indices are put live during the reindex process. |
| Check configured instances | http://localhost:8177/instance | bin/deployment-agent-client list-instances | Shows all known instances on the server |
| Check GC counts | /instance/<INSTANCE>/process/<PROCESS>/monitor/java.lang:name=ConcurrentMarkSweep,type=GarbageCollector/CollectionCount | {{bin/deployment-agent-client get-jmx <INSTANCE> <PROCESS> java.lang:name=ConcurrentMarkSweep,type=GarbageCollector CollectionCount }} | Shows number of Full GCs since last start of the process. |
| Qserver Uptime | /instance/<INSTANCE>/process/<PROCESS>/monitor/java.lang:Runtime/Uptime | Uptime in milli seconds |
Kommentare
0 Kommentare
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.