Accessing Log Files – SearchStax
SearchStax® Managed Solr log files help you track down variations in performance and potential bugs in your application.
Some of the log files may be viewed from the Managed Solr dashboard. Other types of logging are available through the agency of SearchStax support engineers.
Solr Server Logs
Managed Solr provides access to the Solr Dashboard, where you can enable logging of Solr, out-of-memory, and garbage-collection events. Managed Solr also provides download access to those logs.
You can set up Solr logging in the Solr Dashboard:
Solr Dashboard log changes affect only one server
Managed Solr connects to the Solr Dashboard of one Solr node chosen randomly by a load balancer. Changes to logging levels affect only one server of the cluster. When you return to the Solr Dashboard to undo your log settings later, you maynot be connected to the same node. This can make it difficult to back out your changes.
To cleanly reset all servers to default logging, perform a rolling restart of the cluster. Each server returns to default logging as it restarts.
You can monitor significant Solr events on an adjacent screen in the Solr dashboard:
See Configuring Logging in the Apache Solr documentation.
You can download the log files from the Managed Solr dashboard. In the Cloud Manager, go to the dashboard of a specific deployment. Click the Logs menu in the horizontal menu bar. Managed Solr displays controls that let you download log files from any specific Solr server and from the cluster’s load balancer.
The file list is updated once per hour. The logs roll over every 24 hours, and are retained for seven days. Premium customers may request longer retention periods.
Managed Solr Activity Log
Managed Solr automatically records all significant user actions that occur in the Managed Solr dashboard. To view them, click Activity Log in the left-side navigation panel.
Activity Log entries are retained indefinitely.
Help with Log Files
Premium customers may ask SearchStax support for help tracking down memory and performance issues. This often involves enabling logging on servers that the SearchStax end-user cannot reach.
For this type of help please reach out to the SearchStax Support Desk.