Monitoring
Fusion Server has functions built in for observability and monitoring with Fusion’s tools or third-party monitoring tools.
Fusion system metrics
Fusion system metrics are logged and available in the UI, in log files, and through the REST API.- For an overview of noteworthy metrics that are logged and indexed, see System Metrics.
- See System Administration with the Fusion UI.
- Read about System Admin APIs, including APIs for metrics and cluster status, in the REST API Reference Guide.
Additional tools for monitoring Fusion
- Read about other necessary areas to monitor, such as Java Virtual Machines, Unix file systems, networks, and applications like Solr in Monitor Fusion 4.x.x.
- Read about using notifications or alerts in Messaging Service.
- Read about monitoring techniques and guidelines in Cluster Monitoring and Troubleshooting.
- Read about health checks for components of your Fusion deployment in Check the System State.
Check the System State
Check the System State
Fusion runs several components as separate JVMs running on different ports. Each of the components is capable of reporting its status. The proxy component reports status for all of the other components.The response should look similar to the following. If ‘ping’ is true for each service, all of the system components are running.The response will be a JSON response, similar to the following:The As an alternative check, you can also query the The response looks like something like this:As an alternative check, you can also query the The response looks like something like this:
Status Check for Zookeeper and connectors-classic
To see whether each component has been started, a simple API call to the proxy (running on port 8764 by default) will return the status of each component of the system.Solr Health Check
The Fusion UI and API services are not accessible if ZooKeeper and Solr are not in healthy state. A Solr health check can be performed with a ping request, for example:status should be OK if Solr is able to return results for queries.REST API Services Health Check
All of the Fusion API backend services (except Connectors and the UI) are started at port 8765 when the run.sh script is executed. The Fusion UI depends on all these services.If all the services are started without any issues, then the below ping request should return the responseok.system/status endpoint, which returns the status.Connectors Classic Health Check
You can perform a health check of the Connectors Classic Service by sending a ping request to port 8984. Similar to the previous ping request, the returned response isok if the service started successfully.system/status endpoint, which returns the status.For more information
In the Lucidworks Knowledge Base:- General guidelines about monitoring Solr.
- An example of using a third-party tool, Pager Duty, to monitor Fusion.