Default log locations

Content Platform for Cloud Scale Administration Guide

Version
2.6.x
File Size
1945 KB
Audience
anonymous
Part Number
MK-HCPCS008-10

Default log locations

By default, each service stores its logs on each instance on which the service instance runs, in its own folder at this path:

install_path/hcpcs/log

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.

Service Default log folder name Contains information about
Admin-App com.hds.ensemble.plugins.service.​adminApp The System Management application.
Database com.hds.ensemble.plugins.service.​cassandra
  • System configuration data.
  • Document fields and values.
Scheduling com.hds.ensemble.plugins.service.​chronos Workflow task scheduling.
N/A com.hds.ensemble.plugins.service.​containerAction Created by custom actions run by service plugins.
Metrics com.hds.ensemble.plugins.service.​​elasticsearch The storage and indexing of:
  • System events
  • Performance and failure metrics for workflow tasks
Network-Proxy com.hds.ensemble.plugins.service.​haproxy Network requests between instances.
Message Queue com.hds.ensemble.plugins.service.​kafka The transmission of data between instances.
Logging com.hds.ensemble.plugins.service.​logstash The transport of system events and workflow task metrics to the Metrics service.
Service-Deployment com.hds.ensemble.plugins.service.marathon The deployment of high-level services across system instances. High-level services are the ones that you can move and configure, not the services grouped under System Services.
Cluster-Worker com.hds.ensemble.plugins.service.​​mesosAgent The work ordered by the Cluster-Coordination service.
Cluster-Coordination com.hds.ensemble.plugins.service.​mesosMaster Hardware resource allocation.
Watchdog com.hds.ensemble.plugins.service.remoteAction Internal system processes.
Sentinel com.hds.ensemble.plugins.service.​sentinel The internal system processes.
Watchdog com.hds.ensemble.plugins.service.​watchdog General diagnostic information.
Synchronization com.hds.ensemble.plugins.service.​zookeeper The coordination of actions and database activities across instances.
S3-Gateway com.hitachi.aspen.foundry.service.​clientaccess.​data The client access data service.
Data-Lifecycle com.hitachi.aspen.foundry.service.​data-lifecycle.service The data lifecycle service.
Tracing-Agent com.hitachi.aspen.foundry.service.​jaeger.​​agent The tracing agent service.
Tracing-Collector com.hitachi.aspen.foundry.service.jaeger.​collector The tracing collector service.
Tracing-Query com.hitachi.aspen.foundry.service.​jaeger.​​query The tracing query service.
MAPI-Gateway com.hitachi.aspen.foundry.service.​mapi.​gateway The management API gateway.
Metadata-Policy-Engine com.hitachi.aspen.foundry.service.metadata.async.​policy.​engine The metadata asynchronous policy engine.
Grafana com.hitachi.aspen.foundry.service.metrics.​​grafana The dashboard service.
Mirror-Out-Policy com.hitachi.aspen.foundry.service.policy.mirror.out The mirror out (synch-to) service.
Mirror-In-Policy com.hitachi.aspen.foundry.service.policy.mirror.in The mirror in (synch-from) service.
S3-Notifications com.hitachi.aspen.foundry.service.policy.s3.notifications The S3 notifications service.
Metadata-Cache com.hitachi.aspen.foundry.service.metadata.cache The metadata cache.

Note: This service is deprecated.

Metadata-Coordination com.hitachi.aspen.foundry.service.metadata.coordination Metadata coordination.
Metadata-Gateway com.hitachi.aspen.foundry.service.metadata.gateway The metadata gateway.
Telemetry-Service com.hitachi.aspen.foundry.service.metrics.​prometheus Telemetry.
Message-Queue com.hitachi.aspen.foundry.service.rabbitmq.server The message broker.
Key-Management-Server com.hitachi.aspen.foundry.service.vault.vault The key management server.