Logs and diagnostic information
Each service maintains its own set of logs. By default, the logs are maintained in the install_path/hcpcs/log
directory on each instance in the system. During installation, you can configure each service to store its logs in a different, non-default location.
You can manage any of the HCP for cloud scale log files yourself if you want to. That is, you can delete or archive them as necessary.
System logs are managed automatically in these ways:
- All log files are periodically added to a compressed file and moved to install_path/hcpcs/retired/. This occurs at least once 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.
- Whenever you run the
- When 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 the file
exampleService.log.0
grows too large, it is renamed toexampleService.log.1
and the system creates a new file namedexampleService.log.0
to write to.
The tool log_download
lets you easily retrieve logs and diagnostic information from all instances in the system. This tool is located at this path on each instance:
install_path/hcpcs/bin/log_download
For information about running the tool, use this command:
install_path/hcpcs/bin/log_download -h
- When using the tool
log_download
, if you specify the option--output
, do not specify an output path that contains colons, spaces, or symbolic links. If you omit the option--output
, you cannot run the script from within a directory path that contains colons, spaces, or symbolic links. - When you run the script
log_download
, all log files are automatically compressed and moved to the directory install_path/hcpcs/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.
By default, each service stores its logs in its own directory at this path:
install_path/hcpcs/log
This table shows the default log directory names for each service. Depending on how your system was configured when first deployed, your system's logs may not be stored in these directories.
For information about the services, see Services list.
Default log directory name | Related service | Contains information about |
com.hds.ensemble.plugins.service.adminApp | Admin-App | The System Management application. |
com.hitachi.aspen.foundry.service.Aspen | Aspen | The HCP for cloud scale application. |
com.hds.ensemble.plugins.service.cassandra | Database |
|
com.hds.ensemble.plugins.service.chronos | Scheduling | Workflow task scheduling. |
com.hitachi.aspen.foundry.service.clientaccess.data | S3-Gateway | Client access data service. |
com.hds.ensemble.plugins.service.elasticsearch | Metrics | The storage and indexing of:
|
com.hds.ensemble.plugins.service.haproxy | Network-Proxy | Network requests between instances. |
com.hitachi.aspen.foundry.service.tracing.agent | Tracing-Agent | Agent service |
com.hitachi.aspen.foundry.service.tracing.collector | Tracing-Collector | Collector service |
com.hitachi.aspen.foundry.service.tracing.query | Tracing-Query | Query service |
com.hds.ensemble.plugins.service.kafka | Message Queue | Transmission of data between instances. |
com.hds.ensemble.plugins.service.logstash | Logging | The transport of system events and workflow task metrics to the Metrics service. |
com.hitachi.aspen.foundry.service.mapi.gateway | MAPI-Gateway | Management API gateway |
com.hds.ensemble.plugins.service.marathon | Service-Deployment | The 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. |
com.hds.ensemble.plugins.service.mesosAgent | Cluster-Worker | Work ordered by the Cluster-Coordination service. |
com.hds.ensemble.plugins.service.mesosMaster | Cluster-Coordination | Hardware resource allocation. |
com.hitachi.aspen.foundry.service.metadata.policy.engine | Metadata-Policy-Engine | Metadata asynchronous policy engine |
com.hitachi.aspen.foundry.service.metrics.prometheus | Telemetry-Service | Telemetry |
com.hds.ensemble.plugins.service.sentinel | Sentinel | Internal system processes. |
com.hds.ensemble.plugins.service.watchdog | Watchdog | General diagnostic information. |
com.hds.ensemble.plugins.service.zookeeper | Synchronization | Coordination of actions and database operations across instances. |