Monitoring
Your system provides a number of mechanisms that allow you to monitor the health and performance of the system and all of its instances and services.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring instances
You can use the System Management application, CLI, and REST API to view a list of all instances in the system.
Related topics:
System Management application instructions
Viewing all instances
To view all instances, in the System Management application, click on Dashboard > Instances
The page shows all instances in the system. Each instance is identified by its IP address.
This table describes the information shown for each instance.
| Property | Description |
|---|---|
|
State |
One of these: •Up — The instance is reachable by other instances in the system. •Down — The instance cannot be reached by other instances in the system. |
|
Services |
The number of services running on the instance. |
|
Service Units |
The total number of service units for all services and job types running on the instance, out of the recommended service unit limit for the instance. An instance with a higher number of service units is likely to be more heavily utilized by the system than an instance with a lower number of service units. The Instances page displays a blue bar for instances running less than the recommended service unit limit. The Instances page displays a red bar for instances running more than the recommended service unit limit.
For more information on service units and service unit recommendations, see Service units. |
|
Load Average |
The load averages for the instance for the past one, five, and ten minutes. |
|
CPU |
The sum of the percentage utilization for each CPU core in the instance. |
|
Memory Allocated |
This section shows both: •The amount of RAM on the instance that's allocated to all services running on that instance. •The percentage of this allocated RAM to the total RAM for the instance. |
|
Memory Total |
The total amount of RAM for the instance. |
|
Disk Used |
The current amount of disk space that your system is using in the partition on which it is installed. |
|
Disk Free |
The amount of free disk space in the partition in which your system is installed. |
Viewing the services running on an instance
To view the services running on an individual instance, in the System Management application:
1.Click on Dashboard > Instances.
2.Click on the instance you want.
The page lists all services running on the instance.
For each service, the page shows:
•The service name
•The service state. One of these:
oHealthy — The service is running normally.
oUnconfigured — The service has yet to be configured and deployed.
oDeploying — The system is currently starting or restarting the service. This can happen when:
–You move the service to run on a completely different set of instances.
–You repair a service.
For information on viewing the status service operations, see Monitoring service operations.
oBalancing — The service is running normally, but performing some background maintenance operations.
oUnder-protected — In a multi-instance system, one or more of the instances on which a service is configured to run are offline.
oFailed — The service is not running or the system cannot communicate with the service.
•CPU Usage — The current percentage CPU usage for the service across all instances on which it's running.
•Memory — The current RAM usage for the service across all instances on which it's running.
•Disk Used — The current total amount of disk space that the service is using across all instances on which it's running.
Related CLI command(s)
getInstance
listInstances
For information on running CLI commands, see CLI reference.
Related REST API method(s)
GET /instances
GET /instances/{uuid}
For information on specific REST API methods, in the System Management application, click on the help icon (
). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring services
You can use System Management application, CLI, and REST API to view the status of all services for the system.
System Management application instructions
Viewing all services
To view the status of all services, in the System Management application, click on Services.
For each service, the page shows:
•The service name
•The service state. One of these:
oHealthy — The service is running normally.
oUnconfigured — The service has yet to be configured and deployed.
oDeploying — The system is currently starting or restarting the service. This can happen when:
–You move the service to run on a completely different set of instances.
–You repair a service.
For information on viewing the status service operations, see Monitoring service operations.
oBalancing — The service is running normally, but performing some background maintenance operations.
oUnder-protected — In a multi-instance system, one or more of the instances on which a service is configured to run are offline.
oFailed — The service is not running or the system cannot communicate with the service.
•CPU Usage — The current percentage CPU usage for the service across all instances on which it's running.
•Memory — The current RAM usage for the service across all instances on which it's running.
•Disk Used — The current total amount of disk space that the service is using across all instances on which it's running.
Viewing individual service status
To view the detailed status for an individual service, click on the service on the Services page.
In addition to the information above, the page shows:
•Instances — A list of all instances on which the service is running.
•Volumes — To view a list of volumes used by the service, click on the row for an instance in the Instances section. For more information, see Viewing volumes.
•Network: [Internal|External] — Which network type this service uses to receive communications.
This section also displays a list of the ports that the service uses.
For more information, see Networking.
•Configuration settings — The settings you can configure for the service.
•Service Units — The total number of service units currently being spent to run this service. This value is equal to the service's service unit cost times the number of instances on which the service is running. For more information, see Service units.
•Service unit cost — The number of service units required to run the service on one instance. For more information, see Services.
•Service Instance Types — For services that have multiple types, the types that are currently running.
•Instance Pool — For floating services, the instances that this service is eligible to run on. For more information, see Services.
•Events — A list of all system events for the service.
Related CLI command(s)
getService
listServices
For information on running CLI commands, see CLI reference.
Related REST API method(s)
GET /services
GET /services/{id}
For information on specific REST API methods, in the System Management application, click on the help icon (). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring jobs
You can use System Management application, CLI, and REST API to monitor jobs. You can monitor information for all jobs, for all jobs of a type, or for each job individually.
|
Note: Some functions described here are not used with HCP for cloud scale. They are not visible in the System Management application, or have no effect when used. |
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring all jobs
You can use System Management application, CLI, and REST API to view the status of all jobs for the system. For information on jobs, see Jobs.
|
Note: Some functions described here are not used with HCP for cloud scale. They are not visible in the System Management application, or have no effect when used. |
System Management application instructions
To view the status of all jobs, in the System Management application, click on Jobs.
On this page, the All Jobs section shows cumulative information for all jobs in the system.
•Service Units — The total number of service units currently being spent for running jobs.
This value is determined by where your system's job types are allowed to run.
Each job type has its own service unit cost. If an instance is configured to run multiple job types, only the job type with the highest service unit cost counts.
For example, suppose that your system has 4 instances and supports two job types: X, which costs 50 service units, and Y, which costs 25. Job type X is configured to run on 3 instances. Job type Y is configured to run on those same 3 instances, plus an additional instance (4 total). In this case, your total service unit cost for jobs is equal to 175:
50 + 50 + 50 + 25 = 175
For information on configuring which instances job types can run on, see Configuring where jobs run.
•Total CPU — The total CPU percentage utilization for all jobs across all instances in the system.
•Total Memory — The total RAM consumed by all jobs across all instances in the system.
•Total Disk — The total disk space consumed by all jobs across all instances in the system.
The Job Types section shows a box for each job type that the system supports.
Related REST API method(s)
GET /jobs
For information on specific REST API methods, in the System Management application, click on the help icon (). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring job types
You can use System Management application, CLI, and REST API to view the status of all jobs of a particular type. For information on jobs, see Jobs.
|
Note: Some functions described here are not used with HCP for cloud scale. They are not visible in the System Management application, or have no effect when used. |
System Management application instructions
To view the detailed status for all jobs of a type, in the System Management application, click on Jobs. Then click on the box for the job type you want.
The Job Type page shows cumulative information for all jobs of the selected type.
•Total CPU — The total CPU percentage utilization for all jobs of this type across all instances in the system.
•Total Memory — The total RAM consumed by all jobs of this type across all instances in the system.
•Total Disk — The total disk space consumed by all jobs of this type across all instances in the system.
The Jobs section lists each individual job of this type. For more information, see Monitoring individual jobs.
The Instances section shows a list of all system instances where jobs of this type are currently running.
The Pool section shows the instances that jobs of this type are allowed to run on. For information on configuring this, see Configuring where jobs run.
The Events section shows a list of all events related to this job type.
Related REST API method(s)
GET /jobs/types
For information on specific REST API methods, in the System Management application, click on the help icon (). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring individual jobs
You can use System Management application, CLI, and REST API to view the status of individual jobs. For information on jobs, see Jobs.
|
Note: Some functions described here are not used with HCP for cloud scale. They are not visible in the System Management application, or have no effect when used. |
System Management application instructions
To view the detailed status for all jobs of a type, in the System Management application:
1.Click on Jobs.
2.Click on the box for the job type you want.
3.Click on the box for the job you want.
The Job page shows this information about the job:
•Error Count — A tally of the number of errors encountered by the system when running the job or relocating it to other instances.
•Status — One of these:
oIdle — The job has not run yet or, for jobs that have a schedule, the job is not scheduled to be running at the current time.
oPending — The job has been submitted for execution but is not yet running.
oRunning — The job is being executed.
oCompleted — The job finished execution without error.
oFailed — The job finished execution with errors.
oCanceled — The job has been canceled and is no longer running.
•If the task is configured to run according to a schedule, the Status panel shows this icon:
For more information, see Scheduling jobs.
•Service Units — The per-instance cost for this job's type. Individual jobs do not cost any service units to run. For more information, see Monitoring job types.
•Total CPU — The total CPU percentage utilization for this job across all instances in the system.
•Total Memory — The total RAM consumed by this job across all instances in the system.
•Total Disk — The total disk space consumed by this job across all instances in the system.
The Instances section shows a list of all system instances where the job is currently running.
To view information about the volumes that the job uses, click on the row for an instance in the Instances section. For more information, see Viewing volumes.
The Pool section shows the instances that job is allowed to run on. For information on configuring this, see Configuring where jobs run.
The Events section shows a list of all events related to this job.
Related REST API method(s)
GET /jobs/status/{uuid}
For information on specific REST API methods, in the System Management application, click on the help icon (). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring processes
The Processes page lets you view information about what the system is doing. This includes any service operations you started and any internal maintenance processes the system needs to run.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring service operations
You can use the System Management application, CLI, and REST API to monitor all service operations. These operations include:
•The initial deployments of services when the system was installed.
•Service relocation operations that you initiate. For information, see Moving and scaling services.
For each service operation, the system shows:
•The name of the service involved
•The status of the operation
•The number of steps completed out of the total number of steps for the operation
System Management application instructions
1.Click on the Processes panel.
The Service Operations tab shows information about in-progress and completed service operations.
Related CLI command(s)
listSystemTasks
getSystemTask
For information on running CLI commands, see CLI reference.
REST API instructions
GET /tasks/system
GET /tasks/system/{uuid}
For information on specific REST API methods, in the System Management application, click on the help icon (). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Monitoring system processes
You can use System Management application, REST API, and CLI to view the progress of internal system processes. These include package installation tasks and regularly scheduled system maintenance activities such as log rotation.
For each process, your system shows:
•The process name
•The process state
•The times at which each step in the process run occurred
System Management application instructions
1.In the System Management application, click on Processes.
2.To view the currently running processes, click on the System tab.
3.To view the scheduled processes, click on the Scheduled tab.
Related CLI command(s)
listSystemTasks
getSystemTask
System processes have a type of SCHEDULED or ONE-TIME.
For information on running CLI commands, see CLI reference.
REST API instructions
GET /tasks/system
GET /tasks/system/{uuid}
System processes have a type of SCHEDULED or ONE-TIME.
For information on specific REST API methods, in the System Management application, click on the help icon (). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
System events
Your system maintains a log of system events that you can view through the System Management application, CLI, and REST API.
System Management application instructions
To view all system events, in the System Management application, click on Events.
Related CLI command(s)
queryEvents
To view events through the CLI, your requests need to specify which events you want to retrieve.
For example, this JSON request body searches the event log for all events that have a severity level of warning:
{
"severities": [
"warning"
]
}
For information on running CLI commands, see CLI reference.
REST API instructions
POST /events
To view events through the REST API, your requests need to specify which events you want to retrieve.
For example, this JSON request body searches the event log for all events that have a severity level of warning:
{
"severities": [
"warning"
]
}
For information on specific REST API methods, in the System Management application, click on the help icon (). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Alerts
Your system displays alert messages to notify you of situations that require your attention. You can view these alerts through the System Management application, CLI, and REST API.
Each alert corresponds to a system event. For information on:
•Viewing system events, see System events.
•Receiving emails when events occur, see Creating email notification rules.
List of alerts
|
Severity |
Alert Description |
Action |
|---|---|---|
|
Severe |
Instance <ip-address> disk usage severe threshold |
The specified instance has less than 10% free disk space. Add additional storage to the instance. Important: If an instance runs out of disk space, the system may become unresponsive. |
|
Severe |
Master Instance <ip-address> is down |
One of these: •Restart the instance hardware or virtual machine. •Restart the run script on the instance. This script is located in the bin directory in the install directory. |
|
Severe |
Service is down |
Check the health of your instances. If one is down, do one of these: •Restart the instance hardware or virtual machine. •Restart the run script on the instance. This script is located in the bin directory in the install directory. Otherwise, if your instances are healthy and the problem persists, contact support. |
| Severe | Worker Instance <ip-address> is down |
One of these: •Restart the instance hardware or virtual machine. •Restart the run script on the instance. This script is located in the bin directory in the install directory. |
|
Warning |
Instance <ip-address> disk usage warning threshold |
The specified instance has less than 25% free disk space. Add additional storage to the instance. Important: If an instance runs out of disk space, the system may become unresponsive. |
| Warning | Package installation failed |
Your system failed to install a package that you uploaded. For information on •Packages, see Packages. •Viewing the status of the package installation task, see Monitoring system processes. |
|
Warning |
Service below recommendation |
The service is currently running on fewer than the recommended number of instances. Configure this service to run on additional instances. For information on: •The number of instances that each service should run on, see Service list. •Scaling services, see Moving and scaling services. •Adding new instances, see Adding new instances. |
|
Warning |
Service under-protected |
A service has lost redundancy; that is, one or more instances on which that service is running are unresponsive. Check the health of your instances. If one is down, do one of these: •Restart the instance hardware or virtual machine. •Restart the run script on the instance. This script is located in the bin directory in the install directory. Otherwise, if your instances are healthy and the problem persists, contact support. |
|
Warning |
SSL server certificate chain expires soon |
A certificate in the SSL server certificate chain for this system expires soon. If the certificate chain expires, users will be unable to access the system. |
|
Warning |
SSL server certificate chain expired |
The SSL server certificate chain for this system contains an expired certificate. Users cannot access the system until the certificate chain is replaced. |
|
Info |
Package installation in progress |
Your system is currently installing a package that you uploaded. Depending on the contents of the package, this may take a while. For information on •Packages, see Packages. •Viewing the status of the package installation task, see Monitoring system processes. |
| Warning | The certificate for the storage component (storage_id) is about to expire in n days | Renew the storage component certificate. |
| Info | The storage component (storage_id) is unavailable | Verify that the storage component id is correct and valid and that the storage component is active. |
System Management application instructions
To view alerts, click on the user icon (
) in the top righthand corner of each System Management application page, then click on Notifications.
REST API instructions
GET /alerts
For information on specific REST API methods, in the System Management application, click on the help icon (). Then:
•To view the administrative REST API methods, click on REST API - Admin.
For general information about the administrative REST API, see REST API reference.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Creating email notification rules
For the system to send email notifications, you need to create a rule that specifies who to email, what email server to use, what events to send emails about, and what information to include in email messages.
•Enable — Turns on email notifications.
•Host — The hostname or IP address of the email server.
•Port — The port on which the email server listens for email messages.
•Security — The security protocol used by the email server (SSL or STARTTLS) or None if the email server doesn’t use a security protocol.
•Authenticated — Enable this if the email server requires authentication, then specify:
oIn the Username field, the username for an email account that’s authorized to establish the connection between the system and the email server.
oIn the Password field, the password for the email account.
You use the email notification message settings to configure a template for formatting all email notifications sent by the system.
•From — The email address from which you want email notifications to be sent.
•Subject — The email subject.
•Body — The email message body.
Message variablesThis table lists the variables you can use to construct the email notification template. When it sends an email notification, the system replaces the variables with event-specific information.
| Variable | Description |
|---|---|
|
$severity |
Event severity: INFO, WARNING, or SEVERITY |
|
$subject |
A short description of the event |
|
$message |
Event message text |
|
$userName |
Name of the user responsible for the event |
|
$objectId |
Unique identifier for component affected by the event |
|
$subsystem |
Category for the component affected by the event |
|
$objectSourceId |
Unique identifier of the internal system component or process that was the source of the event. Value is [unknown] for most events. |
•Email addresses — A comma-separated list of email addresses to send notification emails to.
•Severity Filter — The event severities about which to send email notifications. Can be one or more of these: INFO, WARNING, SEVERITY.
System Management application instructions
1.Click on the Configuration panel.
2.Click on Notifications.
3.Click on the Create button.
4.In the Type field, select Email.
5.Enter a name for the notification rule.
6.Configure the SMTP settings and message settings for the notification rule.
7.Specify a comma-separated list of emails to send notifications to.
8.Specify a severity filter for the notification role.
9.Click on the Create button.
Related CLI command(s)
createNotificationRule
For information on running CLI commands, see CLI reference.
REST API instructions
POST /notifications
For information, see the administrative REST API documentation page and click on notifications > POST /notifications.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Creating syslog notification rules
When you create a syslog notification rule, the system sends log messages to your syslog server for each applicable system event.
•Enable — Turns on syslog notifications.
•Host — The hostname or IP address of the syslog server.
•Port — The port on which the syslog server listens for log messages.
•Facility — Category for the messages sent by this notification rule.
You use the syslog notification message settings to configure a template for formatting all syslog notifications sent by this notification rule.
•Message — The message to send. You can use these variables as part of the message.
| Variable | Description |
|---|---|
|
$severity |
Event severity: INFO, WARNING, or SEVERITY |
|
$subject |
A short description of the event |
|
$message |
Event message text |
| $time |
Time at which the event occurred |
|
$userName |
Name of the user responsible for the event |
|
$subsystem |
Category for the component affected by the event |
|
$objectId |
Unique identifier for component affected by the event |
| $objectType |
The type of the component affected by the event. |
|
$objectSourceId |
Unique identifier of the internal system component or process that was the source of the event. Value is [unknown] for most events. |
| $objectSourceType | Type of the internal system component or process that was the source of the event. Value is [unknown] for most events. |
•Sender Identity — Identity of the sender for the event. Sent with every syslog message.
The event severities about which to send email notifications. Can be one or more of these: INFO, WARNING, SEVERITY.
System Management application instructions
1.Click on the Configuration panel.
2.Click on Notifications.
3.Click on the Create button.
4.In the Type field, select Syslog.
5.Enter a name for the notification rule.
6.Configure the settings for the notification rule.
7.Specify a severity filter for the notification rule.
8.Click on the Create button.
Related CLI command(s)
createNotificationRule
For information on running CLI commands, see CLI reference.
REST API instructions
POST /notifications
For information, see the administrative REST API documentation page and click on notifications > POST /notifications.
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.
Logs and diagnostic information
Each service and job type maintains its own set of logs. By default, the logs are maintained in the /<install-directory>/log directory on each instance in the system. During installation, each service and job type can be configured to store its logs in a different, non-default location.
Log management
You can manage any of the system log files yourself if you want to. That is, you can delete or archive them as necessary.
|
Note: Deleting log files may make it more difficult for system support personnel to resolve issues you may encounter. |
System logs are managed automatically in these ways:
•All log files are periodically added to a compressed file and moved to /<install-directory>/retired/. This occurs at least once a day, but can also occur:
oWhenever you run the log_download script.
oHourly, if the system instance's disk space is more than 60% full.
•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 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:
/<install-directory>/bin/log_download
For information on running the tool, run:
/<install-directory>/bin/log_download -h
|
Note: •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 directory 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 /<install-directory>/retired/ directory. •If an instance is down, you need to specify the --offline option to collect the logs from that instance. If your whole system is down, you need to run the log_download script with the --offline option on each instance. |
Default log locations
By default, each service stores its logs in its own directory at this path:
<install-directory>/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 on the services, see Service list.
| Default log directory name | Related service | Contains information about |
|---|---|---|
|
com.hds.ensemble.plugins.service.adminApp |
System-Management-application |
The System Management application. |
|
com.hds.ensemble.plugins.service.cassandra |
Database |
•System configuration data. •Document fields and values. |
|
com.hds.ensemble.plugins.service.chronos |
Scheduling |
Workflow task scheduling. |
|
com.hds.ensemble.plugins.service.elasticsearch |
Metrics |
The storage and indexing of: •System events •Performance and failure metrics for workflow tasks |
|
com.hds.ensemble.plugins.service.haproxy |
Network-Proxy | Network requests between instances. |
|
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.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.hds.ensemble.plugins.service.remoteAction |
Watchdog |
Internal system processes. |
|
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. |
| com.hitachi.aspen.foundry.service.mapi.gateway | MAPI-Gateway | Management of API requests. |
| com.hitachi.aspen.foundry.service.metadata.cache | Metadata-Cache API requests | Transmission of system metadata between instances. |
| com.hitachi.aspen.foundry.service.metadata.coordination | Metadata-Coordination | Transmission of system metadata between instances. |
| com.hitachi.aspen.foundry.service.metadata.gateway | Metadata-Gateway | Transmission of system metadata between instances. |
| com.hitachi.aspen.foundry.service.metadata.async.policy.engine | Metadata-Policy-Engine | Update operations. |
| com.hitachi.aspen.foundry.service.clientaccess.data | S3-Gateway | Transmission of S3 requests to endpoints. |
| com.hitachi.aspen.foundry.service.jaeger.agent | Tracing-Agent | Usage of tracing operations. |
| com.hitachi.aspen.foundry.service.jaeger.collector | Tracing-Collector | Usage of tracing collections. |
| com.hitachi.aspen.foundry.service.jaeger.query | Tracing-Query | Usage of tracing queries. |
Trademarks, Legal disclaimer, Third-party software in this documentation
© 2017 - 2019 Hitachi Vantara Corporation. All rights reserved.