Skip to main content

We've Moved!

Product Documentation has moved to
Hitachi Vantara Knowledge

Logs and diagnostic information

Each service maintains its own set of logs. By default, the logs are maintained in the install_path/hci/log folder on each instance in the system. During installation, you can configure each service to store its logs in a different, non-default location.

Log management

You can manage any of the HCI log files yourself, deleting or archiving them as necessary.

NoteDeleting log files might make it more difficult for HCI support personnel to resolve issues you might encounter.

System logs are managed automatically in these ways:

  • All log files are periodically added to a compressed file and moved to install_path/hci/retired/. This occurs at least one time a day, but can also occur:
    • Whenever you run the log_download script.
    • Hourly, if the system instance's disk space is more than 60% full.
  • After a log file grows larger than 10MB in size, the system stops writing to that file, renames it, and begins writing to a new file. For example, if exampleService.log.0 grows too large, it is renamed to exampleService.log.1 and the system creates a new exampleService.log.0 to write to.
Retrieving logs and diagnostic information

The log_download tool lets you easily retrieve logs and diagnostic information from all instances in the system. This tool is located at this path on each instance:


For information about running the tool, use this command:

install_path/hci/bin/log_download -h

  • When using the log_download tool, if you specify the --output option, do not specify an output path that contains colons, spaces, or symbolic links. If you omit the --output option, you cannot run the script from within a folder path that contains colons, spaces, or symbolic links.
  • When you run the log_download script, all log files are automatically compressed and moved to the folder install_path/retired/.
  • If an instance is down, you need to specify the option --offline to collect the logs from that instance. If your whole system is down, you need to run the script log_download with the option --offline on each instance.
Default log locations

By default, each service stores its logs in its own folder at this path:


This table shows the default log folder names for each service. Depending on how your system was configured when first deployed, your system's logs might not be stored in these folders.

Related serviceDefault log directory nameContains information about
Admin-Appcom.hds.ensemble.plugins.service.​adminAppThe System Management application.
Cluster-Coordinationcom.hds.ensemble.plugins.service.​mesosMasterHardware resource allocation.
Cluster-Workercom.hds.ensemble.plugins.service.​mesosAgentWork ordered by the Cluster-Coordination service.
  • System configuration data.
  • Document fields and values.
Indexcom.hds.ensemble.plugins.service.solrIndex collections and search indexes.
Loggingcom.hds.ensemble.plugins.service.​logstashThe transport of system events and workflow task metrics to the Metrics service.
Metricscom.hds.ensemble.plugins.service.​elasticsearchThe storage and indexing of:
  • System events
  • Performance and failure metrics for workflow tasks
Message Queuecom.hds.ensemble.plugins.service.​kafkaTransmission of data between instances.
Monitor-Appcom.hds.ensemble.plugins.service.​mapAppThe HCM application.
Network-Proxycom.hds.ensemble.plugins.service.​haproxyNetwork requests between instances.
Schedulingcom.hds.ensemble.plugins.service.​chronosWorkflow task scheduling.
Search-Appcom.hds.ensemble.plugins.service.searchAppThe Search App
Sentinelcom.hds.ensemble.plugins.service.​sentinelInternal system processes.
Service-Deploymentcom.hds.ensemble.plugins.service.marathonThe deployment of high-level services across system instances. High-level services are the ones that you can move and configure (such as Index), not the services grouped under System Services.
Synchronizationcom.hds.ensemble.plugins.service.​zookeeperCoordination of actions and database operations across instances.
Watchdogcom.hds.ensemble.plugins.service.remoteActionInternal system processes
Watchdogcom.hds.ensemble.plugins.service.​watchdogGeneral diagnostic information.
Workflow-Agent jobscom.hds.ensemble.plugins.job.workflowWorkflows


  • Was this article helpful?