Ops Center Analyzer REST API Reference Guide
Ops Center Analyzer REST API Reference Guide
Guide
10.8.x
MK-99ANA003-10
API architecture
The API functions enable you to use HTTP or HTTPS to collect various types of information such as information about devices
monitored by Ops Center Analyzer.
The API functions of Ops Center Analyzer conform to the REST (Representational State Transfer) architecture style.
Compliance with the REST architecture style has the following benefits:
Adheres to the standard HTTP interface. (The GET, PUT, POST, and DELETE methods are available.)
Uses a URI (Uniform Resource Identifier) for each resource, making it easy to access resources. The relationships between
resources are easy to understand.
The following specifications are common to the API functions provided by Ops Center Analyzer.
The following lists the communication protocols and port numbers that are used by APIs:
Communication protocol
The HTTP and HTTPS are supported by APIs. An API uses a protocol that is used by Ops Center Analyzer for
communicating with a Web browser. The supported version of HTTP or HTTPS is version 1.1. For details on
communication protocols, see the following standards:
RFC 2616
RFC 2818
Port number
The default setting of the port number depends on the communication protocol.
22015
If you want to change the port number, see the section describing how to change the port number between
Analyzer server and the web browser, in the Hitachi Ops Center Analyzer Installation and Configuration Guide.
Execution permission
User Management
Users with User Management permissions can do operations related to managing user information. You can use this type
of permission with other types of permissions.
Admin
Users with Administrator permissions can use all API functions in Ops Center Analyzer except functions for managing user
information and functions for modifying IO control settings.
StorageOps
Users with StorageOps permissions can do operations related to modifying resources of storage systems. You can use
this type of permission with other types of permissions.
Modify
Users with Modify permissions can do all API functions in Ops Center Analyzer except those related to managing user
information, setting up email server, and configuring the connection settings for the Analyzer detail view management
server.
User authentication is required in order to send an API request and receive the response. Ops Center Analyzer API functions use
Basic authentication (Basic Access Authentication) and authentication by using the HSSO token or the Bearer token. Note that
APIs that access RAID Agent can only use Basic authentication.
The HSSO token or the Bearer token is necessary for Single Sign-On. The HSSO token times out after 1,000 seconds. The Bearer
token times out after 300 seconds.
In the request header, specify the authentication information to be used for user authentication.
Basic authentication requires you to specify the authentication header indicating "Basic" (authentication method) followed by a
string consisting of the user name and password separated by a colon (ASCII: 0x3A), encoded with Base64 (referred to as "basic
token").
Authorization: Basic△c3lzdGVtOm1hbmFnZXI=
The HSSO token authentication requires you to specify the authorization header indicating "HSSO" (authentication method)
followed by an HSSO token.
Authorization:HSSO△32bd25936120d68dceabcb49493079f8ef82a4_V0300
The APIs use Bearer token with OpenID connect authentication when it works with the Hitachi Ops Center Common Services.
Authorization:Bearer△bearer_token
Note:
If you use Basic authentication or authentication using the HSSO token to connect to the Ops Center Analyzer server, WWW-
Authenticate: HSSO hsso token is returned in the response header. If you want to reconnect with the Ops Center Analyzer server by
using the same session to run an API function, specify the request header as follows:
Authorization:HSSO△hsso_token
Ops Center Analyzer servers return the status code "401" for unauthorized requests, and request user authentication.
The JSON format is available as the data format for API requests and responses. Specify a data format in the request header. Use
UTF-8 character encoding for the input and output format.
Example:
Accept:application/json
Content-Type:application/json
A request format contains a URI, method, request line, and request header. The request formats to use Ops Center Analyzer's
features through APIs are as follows:
URI format
Use URIs to specify resources for API functions. A URI contains a basic URI (from <schema> to <version>) and a relative URI
(<domain> and followings). Resources are identified with the relative URI (starting from <domain>).
Format of a URI:
<scheme>//<host>:<port>/<application>/<version>/<domain>/<object-type>[?<query-string>]
or
<scheme>//<host>:<port>/<application>/<version>/<domain>/<object-type>/actions/[<action-id
entifier>[/invoke]]
Item Description
<host> Host name or IP address of the Ops Center Analyzer host accessed from an API client.
<port> Port number of the Ops Center Analyzer host accessed from an API client. The default port
number is 22015 for HTTP, and 22016 for HTTPS.
<application> Name of the application that provides the API functions. Specify either "Analytics" or
"Analytics/RAIDAgent", depending on the API function you are using.
Item Description
<query-string> Query parameter that specifies a query parameter. This specifies a condition for reducing or
sorting <object-type>. The available query parameters depend on resources. The query
parameters can be in any order. For details, see HQL syntax relationships and operators.
The components and other details of URIs vary for each API function. For more information, see the descriptions of the applicable
API function.
You can execute the REST API functions of Analyzer detail view via Ops Center Analyzer. The table below shows the URLs
corresponding to the REST API functions of Analyzer detail view that can be executed via Ops Center Analyzer. For details,
including the parameters to be specified for the REST API functions, see the Hitachi Ops Center Analyzer Detail View REST API
Reference Guide.
URLs for REST API functions in Ops Center Analyzer URLs for the corresponding REST API functions in Analyzer
detail view
[Link] [Link]
<query-string> Analyzer-detail-view>/[Link]?<query-string>
[Link] [Link]
<query-string> Analyzer-detail-view>/[Link]?<query-string>
To execute a REST API function of Analyzer detail view via Ops Center Analyzer, specify Ops Center Analyzer authentication
information in the request header.
When executing a REST API function of Analyzer detail view, use the user shown in the following table according to the
permissions set for the Ops Center Analyzer authentication information specified in the request header:
Ops Center Analyzer permission set for the Ops Center Analyzer detail view user used when the REST API function of
Analyzer authentication information Analyzer detail view is executed
Admin HIAA_REST_Admin
Modify HIAA_REST_Normal
Related concepts
Security and authentication
The available methods depend on the resources. For details about the available methods, see the description for each API.
△: Single-byte space
A request line is limited to 8,190 or fewer bytes. For request lines larger than the maximum, the status code 414 (Request-URI Too
Long) is returned.
Note:
When a request is made, internal processing might rewrite the request path and the query, and the request line might exceed the
maximum length (8,190 bytes). In such a case, revise the request path and the query values, and then perform the request by
dividing it into multiple actions.
A request header includes a data format and the language code of the responses.
Port number: Port number API uses to connect with Ops Center
Analyzer
Accept Data format of the response data. For APIs that obtain Optional
metadata:
If the Accept header is omitted, the system assumes that */* is
specified, which allows data to be received in any format. Specify both applica
tion/json and appl
ication/schema+js
on.
some APIs:
application/json
Accept-Language Language of the response data. Note that you do not need to ja: Japanese Required
specify this for APIs that access RAID Agent.
en: English
Specify this if with the GET, POST, or PUT method.
Content-Type Format of the request bodies for the POST or PUT method. application/json Required
or multipart/form-
data
User information
HSSO token:
hsso token
Content-Length The request body size as a decimal number for the POST or PUT Request body size Required
method. (unit: bytes)
Specify this when you specify the POST or PUT method for an
API that accesses RAID Agent. In this case, you must specify
Content-Length or Transfer-Encoding.
Accept-Encoding Specify this if you compress and transfer responses by using an Depends on the user's Optional
API that accesses RAID Agent. For details, see the description of environments
transmission in compressed format.
A response for a request contains a status line, response header, and response body.
Status description
Status code Result of the request in a status code. See the status codes of each API. For details, see HTTP
status codes description.
Header Description
Cache-Control Controls the response information in the cache for the API where the GET method was specified.
Warning When the API completes successfully but there is a problem with the status of the server, details
display in U.S. English (only U.S. English is allowed in the HTTP standard specification).
The response body includes the response data returned when an API function is called. The data format of the response data is
defined in the request header. The format of the response data depends on the API function. See the description for each API
function.
204 No Content Returned instead of 200 when a request was successful but there is no response to
return
303 See Other Returned instead of 200 if another URI processes the request
400 Bad Request The request is invalid. This includes invalid values specified for the query parameter.
401 Unauthorized Notifies you that access to the resource requires authentication. The authentication
method is shown in the WWW-Authenticate header. If the request including the
authorization header is already applied, this code indicates that the authentication
for the user information or the HSSO token was rejected. Possible reasons include
incorrect user information (user ID or password) incorrect HSSO token, and a lack
of rights to use Ops Center Analyzer.
403 Forbidden The user does not have the permissions required to do the operation.
404 Not found The specified resource or operation was not found.
405 Method Not A valid method was not available for the specified resource. Always list the
Allowed available methods.
409 Conflict Conflicts with other data in the server prevent the request from completing.
412 Precondition Failed The request was not accepted because of a failure in the preconditions.
For the status codes of 4XX and 5XX, a response body might be returned in "text/html" or "text/plain" form. In this case, "Content-
Type: text/html" or "Content-Type: text/plain" is in a response header.
Responses provide more detailed contents of errors for which causes are hard to identify only with the status codes of 4XX and
5XX.
Whether to use these status codes depend on the APIs. See the description for each API.
messageID string Message ID of the error. If an error occurs in a request because of a reason
such as incorrect JSON syntax, the message ID is "generic error."
application string Information about the application that provides the API function for which the
error occurred (Analytics).
Related reference
Error object
If you add search conditions to a request by using query parameters, you can filter or sort the output results of the response. Note
that the information provided here is not supported for APIs that access RAID Agent.
The following table lists the parameters you can specify in the requests to obtain a list of resources (for example, monitored
profiles and virtual machines). The parameters depend on the APIs. See the description for each API.
$query Filters the output results by See HQL syntax relationships and Not applicable.
using the specified operators.
conditions.
$order-by Sorts the output results by attribute [{ASC| DESC}](, attribute ASC
the specified attribute. [{ASC| DESC}])
information collection.
Specify the maximum
number of objects in a
response with $count. page
is given priority over
$offset.
#: If you want to specify a character string that cannot be expressed as a URL, use UTF-8 encoding and encode the character
string.
pageSize refers to the maximum number of objects in one page. Page refers to the page number to display. If you set page and
pageSize, the pagination object receives the total number of resources and pages. This value enables you to see whether there
are any of the following pages:
As shown in the expression below, page and pageSize are converted the values of $offset.
$offset=pageSize*(page-1)
The status code 400 (Bad Request) is returned if page and pageSize are out of the range of $offset.
HQL is a query language that can filter collections of data by using various query parameters, including $query and supported
operators.
Use UTF-8 encoding and encode characters and symbols that cannot be expressed as a URL.
Syntax
value-expression displays a string expression, number expression, or Boolean expression. This value is different from the
actual data type of the attribute defined in a resource. The "ISO8601String" type, for example, is dealt with as a string in ISO
8601 format. As a result, it displays as a string-expression.
The following table describes the relationship between the data types and expression formats:
Type Expression
int/long/float number-expression
enum string-expression
String string-expression
ISO8601String string-expression
URLString string-expression
boolean boolean-expression
The following table lists and describes the operators supported by HQL in priority as indicated in the Priority column.
eq Equal number-expression, 1
boolean-expression
Operator Description Expression Priority (1-
3)
boolean-expression
in Included number-expression, 1
boolean-expression
boolean-expression
Example:
Before URL encoding:
...?$query=instanceID%20in%20%5b1000%2c1001%2c1002%5d%20and%20status%20eq%20%27Warning%27
A domain refers to the storage location supported by Ops Center Analyzer. A domain object refers to a resource.
Type Description
ISO8601String, URLString, and enum are extended expressions for the string type.
To specify the date and time, use ISO 8601 format. In this format, you can omit all information except year (yyyy). If the
date or time is omitted, the minimum value is automatically added. If the time zone is omitted, the time zone set for the
Ops Center Analyzer server is the default.
Note, however, that you cannot omit the date and time if you use $query to specify them. If you get time information in
JSON format, the time is output in a format where a colon is not used for time zone information (for example, 2014-12-
09T[Link].500+0900). To specify the time information in JSON format as an input for an API, add a colon in the time
zone (for example, 2014-12-09T[Link].500+09:00). If you do not add a colon, an error occurs.
If the data type of an attribute is "ISO8601String," the year, month, date, time, and time zone display in the response body in
the format shown in the following table:
Resource Domain
AutoAssignFilters objects
AutoAssignFilters services
ChangeHistorys objects
ChangeHistorys services
CustomAction services
DiscoveredResources objects
E2EView objects
E2EView services
EmailServerSettings objects
EmailServerSettings services
Events objects
Events services
Resource Domain
Grades objects
GroupsDefinition objects
GroupsDefinition services
Groups objects
HdcaSettings objects
HdcaSettings services
IoControlHistory objects
IoControlHistory services
IoControlSettings services
KeepAlive services
MailAddress objects
MailAddress services
NotificationProfile objects
NotificationProfile services
PerfComponents objects
PerfComponents services
PerformanceComponent objects
PerformanceData services
PerformanceNode objects
PerformanceVirtualMachine objects
Resource Domain
PerformanceVolume objects
PredictionHistory objects
PredictionHistory services
PredictionLicense objects
PredictionModule objects
PredictionTask objects
PredictionTask services
PredictiveProfile objects
PredictiveReport objects
RecoveryActionHistory objects
RecoveryAction objects
StorageSystemModels objects
StorageSystemPools objects
Suggestion services
SystemProperties objects
SystemSummary services
ThresholdProfileMargins objects
ThresholdProfiles objects
UserResource services
Users objects
Resource Domain
VirtualMachines objects
Volumes objects
The Ops Center Analyzer API supports the following requests and HTTP methods. (For details on the API requests that access
RAID Agent, see "API resources and requests for accessing RAID Agent".)
AutoAssignFilters(Domain : objects)
AutoAssignFilters(Domain : services)
ChangeHistorys(Domain : objects)
ChangeHistorys(Domain : services)
CustomAction(Domain : services)
about
emails that
can be sent
by the
execute
action
function
list of
actions
that can be
executed
by the
execute
action
function
action
function of
the target
resource
DiscoveredResources(Domain : objects)
E2EView(Domain : objects)
E2EView(Domain : services)
EmailServerSettings(Domain : objects)
EmailServerSettings(Domain : services)
Request Method URI Execution
permission
Events(Domain : objects)
Events(Domain : services)
Grades(Domain : objects)
GroupsDefinition(Domain : objects)
Request Method URI Execution
permission
GroupsDefinition(Domain : services)
Groups(Domain : objects)
HdcaSettings(Domain : objects)
IoControlHistory(Domain : objects)
IoControlHistory(Domain : services)
IoControlSettings(Domain : services)
Request Method URI Execution
permission
KeepAlive(Domain : services)
MailAddress(Domain : objects)
MailAddress(Domain : services)
NotificationProfile(Domain : objects)
NotificationProfile(Domain : services)
PerfComponents(Domain : objects)
Request Method URI Execution
permission
PerfComponents(Domain : services)
PerformanceComponent(Domain : objects)
PerformanceData(Domain : services)
PerformanceNode(Domain : objects)
PerformanceVirtualMachine(Domain : objects)
PerformanceVolume(Domain : objects)
PredictionHistory(Domain : objects)
PredictionHistory(Domain : services)
PredictionLicense(Domain : objects)
PredictionModule(Domain : objects)
PredictionTask(Domain : services)
PredictiveProfile(Domain : objects)
PredictiveReport(Domain : objects)
Request Method URI Execution
permission
RecoveryActionHistory(Domain : objects)
RecoveryAction(Domain : objects)
StorageSystemModels(Domain : objects)
Suggestion(Domain : services)
SystemProperties(Domain : objects)
SystemSummary(Domain : services)
ThresholdProfileMargins(Domain : objects)
Request Method URI Execution
permission
ThresholdProfiles(Domain : objects)
profiles and
resources
specified
UserResource(Domain : services)
Users(Domain : objects)
VirtualMachines(Domain : objects)
Volumes(Domain : objects)
Related reference
API resources and requests for accessing RAID Agent
List of enumerators
The following tables list the enumerators that can be specified for API functions.
NodeDisplayType
enumerator Description
Unknown Unknown
Server Server
Storage Storage
NetworkDevice Network
enumerator Description
Datastore Datastore
enumerator Description
NA Invalid value
UNKNOWN Unknown
ANY Any
SWITCH_FC FC switch
DATASTORE Datastore
enumerator Description
NA NA
enumerator Description
INFO Information
WARNING Warning
CRITICAL Critical
enumerator Description
enumerator Description
SSL SSL
TLS SMTPS
STARTTLS STARTTLS
enumerator Description
Preset Default(Preset)
Default Default
NA NA
enumerator Description
enumerator Description
CAPACITY Capacity
IP_ADDRESS IP address
MODEL Model
OS_NAME OS name
SIZE Size
TYPE Type
enumerator Description
enumerator Description
enumerator Description
TAG Consumer
NODE Device
COMPONENT Component
enumerator Description
CLUSTER Cluster
HYPERVISOR Hypervisor
CPU CPU
MEMORY Memory
NIC NIC
HBA HBA
DISK Disk
HOST Host
DATASTORE Datastore
FC_ZONE Zone
FC_SWITCH FC switch
STORAGE Storage
STORAGE_VOLUME Volume
STORAGE_PORT Port
STORAGE_MP Processor
STORAGE_CACHE Cache
STORAGE_POOL Pool
STORAGE_DRIVE Drive
enumerator Description
NORMAL Normal
WARNING Warning
CRITICAL Critical
UNKNOWN Unknown
enumerator Description
enumerator Description
NA No information
enumerator Description
BD BD
FC FC
FMD FMD
NA NA
SAS SAS
enumerator Description
SATA SATA
SSD SSD
FMC FMC
SCM SCM
enumerator Description
NA NA
enumerator Description
NA NA
enumerator Description
NA Not collected
enumerator Description
POWER_ON Power on
SUSPENDED Suspend
enumerator Description
PerformanceChartConnectionMaxIntervalTermBorder Value that determines whether to use the values set for
long-term charts or for short-term charts when a chart is
displayed, when controlling the extent to which lines in the
chart are connected over intervals that lack data
PerformanceChartConnectionMaxIntervalForLongTerm Value that controls the extent to which lines in the chart are
connected over intervals that lack data, when a long-term
chart is displayed
PerformanceChartConnectionMaxIntervalForShortTerm Value that controls the extent to which lines in the chart are
connected over intervals that lack data, when a short-term
chart is displayed
enumerator Description
enumerator Description
ADD Add
MODIFY Modify
REMOVE Remove
enumerator Description
enumerator Description
TO TO
CC CC
BCC BCC
enumerator Description
Group Group
enumerator Description
VM VM
Volume Volume
enumerator Description
Host Host
enumerator Description
VMName This item is set when rules for virtual machine and volume are set using
VM Name.
ClusterName This item is set when rules for volume are set using Cluster Name.
OSType This item is set when rules for host are set using OS Type.
HostName This item is set when rules for host and volume are set using Host
Name.
ConsumerName This item is set when rules are set using Consumer(Group) Name.
Label This item is set when rules for volume are set using Label.
Pools This item is set when rules for volume are set using Pools.
StorageSystems This item is set when rules for volume are set using Storage Systems.
Model This item is set when rules for volume are set using Model.
HostGroup This item is set when rules for volume are set using Host Group.
ConsumerNameOfRelatedResources This item is set when rules for volume are set using Consumer(Group)
Name of Related Resources.
LUNOwnerName This item is set when rules for volume are set using LUN Owner Name.
VolumeName This item is set when rules for volume are set using Volume Name.
DatastoreName This item is set when rules for datastore are set using Datastore Name.
NVMHostNickname This item is set when rules for volume are set using NVM Host
Nickname.
enumerator Description
Equals Equals
enumerator Description
Contains Contains
NotEquals NotEquals
In In
NotIn NotIn
enumerator Description
Linux Linux
Windows Windows
enumerator Description
COMMAND Command
MAIL Mail
enumerator Description
CRITICAL Critical
WARNING Warning
NORMAL Normal
INFORMATION Information
enumerator Description
enumerator Description
OFF Notmonitored
enumerator Description
enumerator Description
WINDOWS Windows
LINUX Linux
ESX ESX
HYPERV Hyper-V
enumerator Description
INTERNAL Internal
EXTERNAL External
enumerator Description
supported Supported
unSupported UnSupported
enumerator Description
Completed Completed
InProgress In Progress
Unknown Unknwon
Executed Executed
enumerator Description
TransferRate TransferRate
IOPS IOPS
enumerator Description
ON ON
OFF OFF
enumerator Description
enumerator Description
enumerator Description
enumerator Description
Modifying The profile is modifying. Resources which assinged to the profile are
not monitored.
ModificationFailed Modification failed. Resources which assinged to the profile are not
monitored.
enumerator Description
VMName vm name
enumerator Description
enumerator Description
New new
Existing existing
enumerator Description
(VMware)
enumerator Description
CPU CPU
MEMORY Memory
LAN_PORT NIC
FC_HBA_PORT HBA
DISK_DRIVE Disk
FILE_SYSTEM Filesystem
enumerator Description
STORAGE_CONTROLLER Processor
STORAGE_FC_PORT Port
STORAGE_POOL PG
STORAGE_VOLUME Volume
LUN LUN
STORAGE_CACHE Cache
VIRTUAL_MACHINE VM
HYPERVISOR_CLUSTER Cluster
DATASTORE Datastore
NA Invalid value
STORAGE_MPB MPB
enumerator Description
STORAGE_DP_POOL Pool
STORAGE_DKA_ESW DKA-ESW
STORAGE_CACHE_ESW Cache-ESW
STORAGE_MP Processor
enumerator Description
Low Low
Middle Middle
High High
enumerator Description
sec Sec
min Min
enumerator Description
hour Hour
day Day
week Week
month Month
enumerator Description
About About
enumerator Description
Possible Possible
Impossible Impossible
ConditionalImpossible ConditionalImpossible
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/AutoAssignFilters
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
AutoAssignFilter
{
"instanceID":"...",
"filterName":"...",
"filterType":"...",
"resourceType":"...",
"priority":"...",
"description":"...",
"groupID":"...",
"groupName":"...",
"userResourceThresholdID":"...",
"userResourceThresholdName":"...",
"profileResourceType":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
groupID string ID of the assignment-destination consumer. This item is set only if the rule type
is "Group".
groupName string Name of the assignment-destination consumer. This item is set only if the rule
type is "Group".
userResourceThresholdID string ID of the threshold profile to be assigned to the resource. This item is set only if
the rule type is "UserResourceThreshold".
userResourceThresholdName string Name of the threshold profile to be assigned to the resource. This item is set
only if the rule type is "UserResourceThreshold".
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/AutoAssignFilters
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 30f198fbc8b17b25ed2d623b761929ba5a56df2_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "autoAssignFilter#86f40c58-4000-429d-a50c-d1acf7be73e5",
"filterName" : "filterName-20160812201659091",
"filterType" : "Group",
"resourceType" : "VM",
"priority" : 1,
"description" : "Description 7 Consumer - Host",
"groupID" : "group#d4b70260-a0d0-4961-9765-6f06b437163a",
"groupName" : "GroupForAutoAssignFilterGetTest",
"profileResourceType" : "INVALID_MEMBER"
} ],
"count" : 1
Related reference
List of enumerators
Admin, Modify
Request line
POST baseURL/v1/objects/AutoAssignFilters
Request body
The structure of the request body and the object attributes are as follows:
AutoAssignFilter
{
"instanceID":"...",
"filterName":"...",
"filterType":"...",
"resourceType":"...",
"priority":"...",
"description":"...",
"groupID":"...",
"groupName":"...",
"userResourceThresholdID":"...",
"userResourceThresholdName":"...",
"profileResourceType":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
groupID string ID of the assignment-destination consumer. This item is set only if the rule type
is "Group".
groupName string Name of the assignment-destination consumer. This item is set only if the rule
type is "Group".
userResourceThresholdID string ID of the threshold profile to be assigned to the resource. This item is set only if
the rule type is "UserResourceThreshold".
userResourceThresholdName string Name of the threshold profile to be assigned to the resource. This item is set
only if the rule type is "UserResourceThreshold".
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
AutoAssignFilter
{
"instanceID":"...",
"filterName":"...",
"filterType":"...",
"resourceType":"...",
"priority":"...",
"description":"...",
"groupID":"...",
"groupName":"...",
"userResourceThresholdID":"...",
"userResourceThresholdName":"...",
"profileResourceType":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
Attribute Type Description
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
groupID string ID of the assignment-destination consumer. This item is set only if the rule type
is "Group".
groupName string Name of the assignment-destination consumer. This item is set only if the rule
type is "Group".
userResourceThresholdID string ID of the threshold profile to be assigned to the resource. This item is set only if
the rule type is "UserResourceThreshold".
userResourceThresholdName string Name of the threshold profile to be assigned to the resource. This item is set
only if the rule type is "UserResourceThreshold".
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
Example code
[Request Header]
POST /Analytics/v1/objects/AutoAssignFilters
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"filterName":"filterName-20160812201703052",
"filterType":"Group",
"resourceType":"VM",
"description":"Description 7 Consumer - Host",
"groupID":"group#a9942fa3-0567-48fd-a147-da1bbe77c0ff",
"groupName":"GroupAutoAssignFilterGetId"
}
[Response Header]
HTTP/1.1 201 Created
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 30f198fbc8b17b25ed2d623b761929ba5a56df2_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "autoAssignFilter#1e24a8b4-afb6-4afe-b657-349588e4248c",
"filterName" : "filterName-20160812201703052",
"filterType" : "Group",
"resourceType" : "VM",
"priority" : 1,
"description" : "Description 7 Consumer - Host",
"groupID" : "group#a9942fa3-0567-48fd-a147-da1bbe77c0ff",
"groupName" : "GroupAutoAssignFilterGetId",
"profileResourceType" : "INVALID_MEMBER"
}
Related reference
List of enumerators
You can obtain information about a specific automatic resource assignment rule.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/AutoAssignFilters/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
AutoAssignFilter
{
"instanceID":"...",
"filterName":"...",
"filterType":"...",
"resourceType":"...",
"priority":"...",
"description":"...",
"groupID":"...",
"groupName":"...",
"userResourceThresholdID":"...",
"userResourceThresholdName":"...",
"profileResourceType":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
groupID string ID of the assignment-destination consumer. This item is set only if the rule type
is "Group".
groupName string Name of the assignment-destination consumer. This item is set only if the rule
type is "Group".
userResourceThresholdID string ID of the threshold profile to be assigned to the resource. This item is set only if
the rule type is "UserResourceThreshold".
userResourceThresholdName string Name of the threshold profile to be assigned to the resource. This item is set
only if the rule type is "UserResourceThreshold".
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/AutoAssignFilters/autoAssignFilter%238b14d6a4-0802-4360-9164-2192324ae
657
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "autoAssignFilter#8b14d6a4-0802-4360-9164-2192324ae657",
"filterName" : "filterName-20160812025153377",
"filterType" : "Group",
"resourceType" : "VM",
"priority" : 1,
"description" : "Description 7 Consumer - Host",
"groupID" : "group#bd40cdaa-5b4f-49fb-83f6-6e5393150b06",
"groupName" : "GroupAutoAssignFilterGetId",
"profileResourceType" : "INVALID_MEMBER"
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
PUT baseURL/v1/objects/AutoAssignFilters/{id}
Request body
The structure of the request body and the object attributes are as follows:
AutoAssignFilter
{
"instanceID":"...",
"filterName":"...",
"filterType":"...",
"resourceType":"...",
"priority":"...",
"description":"...",
"groupID":"...",
"groupName":"...",
"userResourceThresholdID":"...",
"userResourceThresholdName":"...",
"profileResourceType":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
groupID string ID of the assignment-destination consumer. This item is set only if the rule type
is "Group".
groupName string Name of the assignment-destination consumer. This item is set only if the rule
type is "Group".
userResourceThresholdID string ID of the threshold profile to be assigned to the resource. This item is set only if
the rule type is "UserResourceThreshold".
userResourceThresholdName string Name of the threshold profile to be assigned to the resource. This item is set
only if the rule type is "UserResourceThreshold".
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
AutoAssignFilter
{
"instanceID":"...",
"filterName":"...",
"filterType":"...",
"resourceType":"...",
"priority":"...",
"description":"...",
"groupID":"...",
"groupName":"...",
"userResourceThresholdID":"...",
"userResourceThresholdName":"...",
"profileResourceType":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
groupID string ID of the assignment-destination consumer. This item is set only if the rule type
is "Group".
groupName string Name of the assignment-destination consumer. This item is set only if the rule
type is "Group".
userResourceThresholdID string ID of the threshold profile to be assigned to the resource. This item is set only if
the rule type is "UserResourceThreshold".
userResourceThresholdName string Name of the threshold profile to be assigned to the resource. This item is set
only if the rule type is "UserResourceThreshold".
Attribute Type Description
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
PUT /Analytics/v1/objects/AutoAssignFilters/autoAssignFilter%23575a9bc3-7f10-455b-a43b-c6b3346db
a54
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"instanceID":"autoAssignFilter#a9807e96-4110-466e-9f3e-2fbff9368100",
"filterName":"GroupFilterNameForAutoAssignFilterPutTest",
"filterType":"Group",
"resourceType":"VM",
"description":"Description 7 Consumer - Host",
"groupID":"group#766db34f-e63c-4e10-b038-bf383748c058",
"anyGroupFlag":false,
"groupName":"GroupForAutoAssignFilterPutTest"
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "autoAssignFilter#a9807e96-4110-466e-9f3e-2fbff9368100",
"filterName" : "GroupFilterNameForAutoAssignFilterPutTest",
"filterType" : "Group",
"resourceType" : "VM",
"priority" : 1,
"description" : "Description 7 Consumer - Host",
"groupID" : "group#766db34f-e63c-4e10-b038-bf383748c058",
"groupName" : "GroupForAutoAssignFilterPutTest",
"profileResourceType" : "INVALID_MEMBER"
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/AutoAssignFilters/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
Example code
[Request Header]
DELETE /Analytics/v1/objects/AutoAssignFilters/autoAssignFilter%23d4655d61-1073-408f-9316-1c8e3
b8fc684
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 204 No Content
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
Getting a list of operations for information about automatic resource assignment rules
You can obtain a list of operations that can be performed on a specific automatic resource assignment rule.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/AutoAssignFilters/{id}/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/AutoAssignFilters/111111/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8810cbc381adf14797b70f0c5a4de1bd9d09ad1_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getFilterCondition",
"href" : "[Link]
lterCondition/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "updateFilterCondition",
"href" : "[Link]
eFilterCondition/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 2
}
Preparing to obtain a list of condition information for automatic resource assignment rules
The following operation is the initial step to obtain a list of conditions of a specific automatic resource assignment rule.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/AutoAssignFilters/{id}/actions/getFilterCondition
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetFilterConditionParam
{
"filterType":"...",
"resourceType":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
Attribute Type Description
UserResourceThreshold
Group
resourceType enum Type of resource to which the assignment rule to be obtained is to be applied
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/AutoAssignFilters/autoAssignFilter%2318a8ad07-09c5-4d73-a7ad-aa797721a
5db/actions/getFilterCondition
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getFilterCondition",
"href" : "[Link]
8ad07%2d09c5%2d4d73%2da7ad%2daa797721a5db/actions/getFilterCondition/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"filterType" : "Group",
"resourceType" : "Host"
} ]
}
Related reference
List of enumerators
You can obtain a list of conditions of a specific automatic resource assignment rule.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/AutoAssignFilters/{id}/actions/getFilterCondition/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetFilterConditionParam
{
"filterType":"...",
"resourceType":"..."
}
GetFilterConditionParam (Type: GetFilterConditionParam)
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
resourceType enum Type of resource to which the assignment rule to be obtained is to be applied
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of FilterCondition objects. For details about FilterCondition, see the table
result anyType[]
below.
FilterCondition
{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"...",
"storageSystemModelName":"..."
}
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
LUNOwnerName
Attribute Type Description
(For details about the valid values, see the table ConditionType
in List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List
of enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of
the assignment rule is "StorageSystems" or "Pools".
filterString string Value of the assignment rule. This item is not set if the attribute
of the assignment rule is "OSType", "StorageSystems", or
"Pools".
storageSystemModelName string Name of the storage system. This item is set only if the attribute
of the assignment rule is "Model".
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/AutoAssignFilters/autoAssignFilter%2318a8ad07-09c5-4d73-a7ad-aa797721
a5db/actions/getFilterCondition/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getFilterCondition",
"href": "[Link]
ad07%2d09c5%2d4d73%2da7ad%2daa797721a5db/actions/getFilterCondition/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"filterType":"UserResourceThreshold",
"resourceType":"VM"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "464a3cf6-790f-496f-93f9-8c72a06ab581",
"created" : "2016-08-12T[Link].970+09:00",
"updated" : "2016-08-12T[Link].970+09:00",
"completed" : "2016-08-12T[Link].970+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Related reference
List of enumerators
The following operation is the initial step to modify a condition of a specific automatic resource assignment rule.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/AutoAssignFilters/{id}/actions/updateFilterCondition
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
{
"filterType":"...",
"resourceType":"...",
"filterConditions":[{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"...",
"storageSystemModelName":"..."
},
:
]
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
resourceType enum Type of resource to which the assignment rule to be updated is to be applied
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
LUNOwnerName
(For details about the valid values, see the table ConditionType
in List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List
of enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of
the assignment rule is "StorageSystems" or "Pools".
filterString string Value of the assignment rule. This item is not set if the attribute
of the assignment rule is "OSType", "StorageSystems", or
"Pools".
storageSystemModelName string Name of the storage system. This item is set only if the attribute
of the assignment rule is "Model".
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/AutoAssignFilters/autoAssignFilter%23ab2c3eba-cc85-4a2a-b16e-2d73da986
095/actions/updateFilterCondition
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "updateFilterCondition",
"href" : "[Link]
c3eba%2dcc85%2d4a2a%2db16e%2d2d73da986095/actions/updateFilterCondition/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"filterType" : "Group",
"resourceType" : "Host",
"filterConditions" : [ ]
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/AutoAssignFilters/{id}/actions/updateFilterCondition/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
UpdateFilterConditionParam
{
"filterType":"...",
"resourceType":"...",
"filterConditions":[{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"..."
},
:
]
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
resourceType enum Type of resource to which the assignment rule to be updated is to be applied
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
(For details about the valid values, see the table FilterAttributeType
in List of enumerators.)
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
Attribute Type Description
LUNOwnerName
(For details about the valid values, see the table ConditionType in
List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List of
enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of the
assignment rule is "StorageSystems" or "Pools".
filterString string Value of the assignment rule. This item is not set if the attribute of
the assignment rule is "OSType", "StorageSystems", or "Pools".
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/AutoAssignFilters/autoAssignFilter%23ab2c3eba-cc85-4a2a-b16e-2d73da98
6095/actions/updateFilterCondition/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "updateFilterCondition",
"href": "[Link]
3eba%2dcc85%2d4a2a%2db16e%2d2d73da986095/actions/updateFilterCondition/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"filterType":"UserResourceThreshold",
"resourceType":"VM",
"filterConditions": [{
"displayOrder":1,
"attributeType":"OSType",
"conditionType":"Equals",
"osType":"Windows"
}]
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "784fba13-8ce5-44c3-9a0e-0396ba1293b2",
"created" : "2016-08-12T[Link].728+09:00",
"updated" : "2016-08-12T[Link].728+09:00",
"completed" : "2016-08-12T[Link].728+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Related reference
List of enumerators
Getting a list of operations for automatic resource assignment rules
You can obtain a list of operations related to automatic resource assignment rules.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/AutoAssignFilters/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/AutoAssignFilters/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "changeFilterPriority",
"href" : "[Link]
rPriority/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "previewVolume",
"href" : "[Link]
me/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "assignmentResource",
"href" : "[Link]
esource/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "previewHost",
"href" : "[Link]
t/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "previewVirtualMachine",
"href" : "[Link]
ualMachine/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 5
}
The following operation is the initial step to change the priority of a specific automatic resource assignment rule.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/AutoAssignFilters/actions/changeFilterPriority
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ChangePriorityFilterParam
{
"filterType":"...",
"resourceType":"...",
"profileResourceType":["...", ...],
"filterIDList":["...", ...]
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
Attribute Type Description
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/AutoAssignFilters/actions/changeFilterPriority
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "changeFilterPriority",
"href" : "[Link]
riority/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"filterType" : "Group",
"resourceType" : "Host",
"filterIDList" : [ ]
} ]
}
Related reference
List of enumerators
You can change the priority of a specific automatic resource assignment rule.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/AutoAssignFilters/actions/changeFilterPriority/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
{
"filterType":"...",
"resourceType":"...",
"profileResourceType":["...", ...],
"filterIDList":["...", ...]
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
(For details about the valid values, see the table FilterResourceType in List of
enumerators.)
VM
Volume
Host
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/AutoAssignFilters/actions/changeFilterPriority/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "changeFilterPriority",
"href": "[Link]
Priority/invoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"filterType": "UserResourceThreshold",
"resourceType": "VM",
"profileResourceType": [
"ESX_VM"
],
"filterIDList": [
"autoAssignFilter#4372943b-d86f-4346-8054-b85c0d3659c4"
]
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO f0751c34edbce22432793e8c64f16c2ea125e88_Y2UOI2pkMXQ=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID": "338977ac-5a39-45ad-8e25-d2c554c5006d",
"created": "2016-08-22T[Link].444+09:00",
"updated": "2016-08-22T[Link].444+09:00",
"completed": "2016-08-22T[Link].444+09:00",
"state": "success",
"affectedResource": [
],
"result": [
]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/AutoAssignFilters/actions/assignmentResource
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
AssignmentResourceParam
{
"filterType":"...",
"resourceType":"...",
"profileResourceType":["...", ...],
"assignmentAllResource":"...",
"resourceIDList":["...", ...],
"filterIDList":["...", ...],
"includeAwaitingAssignmentResources":"...",
"disableDiscoveredTimeCheck":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Attribute Type Description
Group
(For details about the valid values, see the table FilterResourceType in
List of enumerators.)
VM
Volume
Host
assignmentAllResource boolean Whether or not to assign the consumer or threshold profile to all
unassigned resources. If "true" is specified, the consumer or threshold
profile is assigned to all unassigned resources. If "false" is specified, the
consumer or threshold profile is assigned to the resources with the IDs
specified in resourceIDList.
filterIDList string[] ID of the rule to be used for assignment. If an empty list is specified, all
rules will be used.
includeAwaitingAssignmentResources boolean Value that specifies whether resources waiting to be assigned are to be
included in the assignment target. If "True" is specified, the resources
will be included in the assignment target. If "False" is specified, the
resources will not be included in the assignment target.
disableDiscoveredTimeCheck boolean Value that specifies whether to check, during the assignment of
unassigned resources, whether data collection has finished. If "True" is
specified, resources will be assigned without performing this check. If
"False" is specified, this check will be performed. When the check is
performed, if a corresponding resource already exists, the assignment of
unassigned resources fails.
Status codes
200 OK Success.
Example code
[Request Header]
GET
[Link]
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "assignmentResource",
"href" : "[Link]
ource/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"filterType" : "Group",
"resourceType" : "Host",
"assignmentAllResource" : false,
"resourceIDList" : [ ]
} ]
}
Related reference
List of enumerators
Assigning resources
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/AutoAssignFilters/actions/assignmentResource/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
AssignmentResourceParam
{
"filterType":"...",
"resourceType":"...",
"profileResourceType":["...", ...],
"assignmentAllResource":"...",
"resourceIDList":["...", ...],
"filterIDList":["...", ...],
"includeAwaitingAssignmentResources":"...",
"disableDiscoveredTimeCheck":"..."
}
(For details about the valid values, see the table FilterType in List of
enumerators.)
UserResourceThreshold
Group
(For details about the valid values, see the table FilterResourceType in
List of enumerators.)
VM
Attribute Type Description
Volume
Host
assignmentAllResource boolean Whether or not to assign the consumer or threshold profile to all
unassigned resources. If "true" is specified, the consumer or threshold
profile is assigned to all unassigned resources. If "false" is specified, the
consumer or threshold profile is assigned to the resources with the IDs
specified in resourceIDList.
filterIDList string[] ID of the rule to be used for assignment. If an empty list is specified, all
rules will be used.
includeAwaitingAssignmentResources boolean Value that specifies whether resources waiting to be assigned are to be
included in the assignment target. If "True" is specified, the resources
will be included in the assignment target. If "False" is specified, the
resources will not be included in the assignment target.
disableDiscoveredTimeCheck boolean Value that specifies whether to check, during the assignment of
unassigned resources, whether data collection has finished. If "True" is
specified, resources will be assigned without performing this check. If
"False" is specified, this check will be performed. When the check is
performed, if a corresponding resource already exists, the assignment of
unassigned resources fails.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/AutoAssignFilters/actions/assignmentResource/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "assignmentResource",
"href": "[Link]
urce/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{"filterType": "UserResourceThreshold",
"resourceType":"Windows",
"profileResourceType":["WINDOWS"],
"assignmentAllResource":false,
"filterIDList":[],
"resourceIDList":["vm#ITPDLab_172.17.17.115_vm-143"]}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "bde82024-b5a9-45e7-b760-d5acec016215",
"created" : "2016-08-12T[Link].421+09:00",
"updated" : "2016-08-12T[Link].421+09:00",
"completed" : "2016-08-12T[Link].421+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Related reference
List of enumerators
The following operation is the initial step to obtain a preview of the results of assigning hosts according to automatic resource
assignment rules.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/AutoAssignFilters/actions/previewHost
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
AssignPreviewParam
{
"profileID":"...",
"type":"...",
"autoAssignFilterIDs":["...", ...],
"filterConditions":[{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"...",
"storageSystemModelName":"..."
},
:
],
"profileResourceType":["...", ...],
"hqlFilter":"...",
"hqlSort":"...",
"page":"...",
"pageSize":"...",
"includeAwaitingAssignmentResources":"..."
}
includeAwaitingAssignmentResources boolean Value that specifies whether resources waiting to be assigned are to
be included in the assignment target. If "True" is specified, the
resources will be included in the assignment target. If "False" is
specified, the resources will not be included in the assignment target.
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Attribute Type Description
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
LUNOwnerName
(For details about the valid values, see the table ConditionType
in List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List
of enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of
the assignment rule is "StorageSystems" or "Pools".
filterString string Value of the assignment rule. This item is not set if the attribute
of the assignment rule is "OSType", "StorageSystems", or
"Pools".
storageSystemModelName string Name of the storage system. This item is set only if the attribute
of the assignment rule is "Model".
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/AutoAssignFilters/actions/previewHost
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8810cbc381adf14797b70f0c5a4de1bd9d09ad1_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "previewHost",
"href" : "[Link]
nvoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"profileID" : [ ],
"type" : "in",
"autoAssignFilterIDs" : [ ],
"filterConditions" : [ ],
"hqlFilter" : "",
"hqlSort" : "",
"page" : 1,
"pageSize" : 30
} ]
}
Related reference
List of enumerators
Getting the results of automatic host distribution
You can obtain a preview of the results of assigning hosts according to automatic resource assignment rules.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/AutoAssignFilters/actions/previewHost/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
AssignPreviewParam
{
"profileID":"...",
"type":"...",
"autoAssignFilterIDs":["...", ...],
"filterConditions":[{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"..."
},
:
],
"profileResourceType":["...", ...],
"hqlFilter":"...",
"hqlSort":"...",
"page":"...",
"pageSize":"...",
"includeAwaitingAssignmentResources":"..."
}
includeAwaitingAssignmentResources boolean Value that specifies whether resources waiting to be assigned are to
be included in the assignment target. If "True" is specified, the
resources will be included in the assignment target. If "False" is
specified, the resources will not be included in the assignment target.
(For details about the valid values, see the table FilterAttributeType
in List of enumerators.)
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
LUNOwnerName
(For details about the valid values, see the table ConditionType in
List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List of
enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of the
assignment rule is "StorageSystems" or "Pools".
filterString string Value of the assignment rule. This item is not set if the attribute of
the assignment rule is "OSType", "StorageSystems", or "Pools".
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/AutoAssignFilters/actions/previewHost/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "previewHost",
"href": "[Link]
voke",
"method": "POST",
"type": "application/json",
"parameters":[{
"profileID":["thProfile#ESX_VM"],
"type":"in",
"autoAssignFilterIDs":["autoAssignFilter#aa4cac08-18e9-46be-9277-8f7156551762"],
"filterConditions":[]}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "5a1845c6-99c0-454c-998f-96d50f41433c",
"created" : "2016-08-12T[Link].943+09:00",
"updated" : "2016-08-12T[Link].943+09:00",
"completed" : "2016-08-12T[Link].943+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"data" : [ ],
"count" : 0
} ]
}
Related reference
List of enumerators
The following operation is the initial step to obtain a preview of the results of assigning virtual machines according to automatic
resource assignment rules.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/AutoAssignFilters/actions/previewVirtualMachine
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
AssignPreviewParam
{
"profileID":"...",
"type":"...",
"autoAssignFilterIDs":["...", ...],
"filterConditions":[{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"...",
"storageSystemModelName":"..."
},
:
],
"profileResourceType":["...", ...],
"hqlFilter":"...",
"hqlSort":"...",
"page":"...",
"pageSize":"...",
"includeAwaitingAssignmentResources":"..."
}
includeAwaitingAssignmentResources boolean Value that specifies whether resources waiting to be assigned are to
be included in the assignment target. If "True" is specified, the
resources will be included in the assignment target. If "False" is
specified, the resources will not be included in the assignment target.
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
LUNOwnerName
(For details about the valid values, see the table ConditionType
in List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List
of enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of
the assignment rule is "StorageSystems" or "Pools".
filterString string Value of the assignment rule. This item is not set if the attribute
of the assignment rule is "OSType", "StorageSystems", or
"Pools".
storageSystemModelName string Name of the storage system. This item is set only if the attribute
of the assignment rule is "Model".
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/AutoAssignFilters/actions/previewVirtualMachine
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "previewVirtualMachine",
"href" : "[Link]
lMachine/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"profileID" : [ ],
"type" : "in",
"autoAssignFilterIDs" : [ ],
"filterConditions" : [ ],
"hqlFilter" : "",
"hqlSort" : "",
"page" : 1,
"pageSize" : 30
} ]
}
Related reference
List of enumerators
You can obtain a preview of the results of assigning virtual machines according to automatic resource assignment rules.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/AutoAssignFilters/actions/previewVirtualMachine/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
AssignPreviewParam
{
"profileID":"...",
"type":"...",
"autoAssignFilterIDs":["...", ...],
"filterConditions":[{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"..."
},
:
],
"profileResourceType":["...", ...],
"hqlFilter":"...",
"hqlSort":"...",
"page":"...",
"pageSize":"...",
"includeAwaitingAssignmentResources":"..."
}
includeAwaitingAssignmentResources boolean Value that specifies whether resources waiting to be assigned are to
be included in the assignment target. If "True" is specified, the
resources will be included in the assignment target. If "False" is
specified, the resources will not be included in the assignment target.
(For details about the valid values, see the table FilterAttributeType
in List of enumerators.)
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
LUNOwnerName
Attribute Type Description
(For details about the valid values, see the table ConditionType in
List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List of
enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of the
assignment rule is "StorageSystems" or "Pools".
filterString string Value of the assignment rule. This item is not set if the attribute of
the assignment rule is "OSType", "StorageSystems", or "Pools".
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/AutoAssignFilters/actions/previewVirtualMachine/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "previewVirtualMachine",
"href": "[Link]
Machine/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"profileID":["thProfile#ESX_VM"],
"type":"in",
"autoAssignFilterIDs":["autoAssignFilter#24fa3245-f476-4011-9184-da2cae1c39ab"],
"filterConditions":[]
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "e9db1581-ad72-4d72-b434-e48748f58494",
"created" : "2016-08-12T[Link].159+09:00",
"updated" : "2016-08-12T[Link].159+09:00",
"completed" : "2016-08-12T[Link].159+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"data" : [ ],
"count" : 0
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/AutoAssignFilters/actions/previewVolume
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
AssignPreviewParam
{
"profileID":"...",
"type":"...",
"autoAssignFilterIDs":["...", ...],
"filterConditions":[{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"...",
"storageSystemModelName":"..."
},
:
],
"profileResourceType":["...", ...],
"hqlFilter":"...",
"hqlSort":"...",
"page":"...",
"pageSize":"...",
"includeAwaitingAssignmentResources":"..."
}
includeAwaitingAssignmentResources boolean Value that specifies whether resources waiting to be assigned are to
be included in the assignment target. If "True" is specified, the
resources will be included in the assignment target. If "False" is
specified, the resources will not be included in the assignment target.
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
LUNOwnerName
(For details about the valid values, see the table ConditionType
in List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List
of enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of
the assignment rule is "StorageSystems" or "Pools".
filterString string Value of the assignment rule. This item is not set if the attribute
of the assignment rule is "OSType", "StorageSystems", or
"Pools".
storageSystemModelName string Name of the storage system. This item is set only if the attribute
of the assignment rule is "Model".
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/AutoAssignFilters/actions/previewVolume
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "previewVolume",
"href" : "[Link]
e/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"profileID" : [ ],
"type" : "in",
"autoAssignFilterIDs" : [ ],
"filterConditions" : [ ],
"hqlFilter" : "",
"hqlSort" : "",
"page" : 1,
"pageSize" : 30
} ]
}
Related reference
List of enumerators
You can obtain a preview of the results of assigning volumes according to automatic resource assignment rules.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/AutoAssignFilters/actions/previewVolume/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
AssignPreviewParam
{
"profileID":"...",
"type":"...",
"autoAssignFilterIDs":["...", ...],
"filterConditions":[{
"displayOrder":"...",
"attributeType":"...",
"conditionType":"...",
"osType":"...",
"storageSystems":[{
"storageSystemID":"...",
"storageSystemName":"...",
"poolID":"...",
"poolName":"..."
},
:
],
"filterString":"..."
},
:
],
"profileResourceType":["...", ...],
"hqlFilter":"...",
"hqlSort":"...",
"page":"...",
"pageSize":"...",
"includeAwaitingAssignmentResources":"..."
}
includeAwaitingAssignmentResources boolean Value that specifies whether resources waiting to be assigned are to
be included in the assignment target. If "True" is specified, the
resources will be included in the assignment target. If "False" is
specified, the resources will not be included in the assignment target.
(For details about the valid values, see the table FilterAttributeType
in List of enumerators.)
VMName
ClusterName
OSType
HostName
ConsumerName
Label
Pools
StorageSystems
Model
HostGroup
ConsumerNameOfRelatedResources
LUNOwnerName
(For details about the valid values, see the table ConditionType in
List of enumerators.)
Equals
Start_With
End_With
Contains
NotEquals
In
NotIn
(For details about the valid values, see the table OsType in List of
enumerators.)
Linux
Windows
storageSystems FilterConditionStorageSystem[] Storage assignment rule. This item is set only if the attribute of the
assignment rule is "StorageSystems" or "Pools".
Attribute Type Description
filterString string Value of the assignment rule. This item is not set if the attribute of
the assignment rule is "OSType", "StorageSystems", or "Pools".
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST
[Link]
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "previewVolume",
"href": "[Link]
invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"profileID":["thProfile#ESX_VM"],
"type":"in",
"autoAssignFilterIDs":["autoAssignFilter#39384310-874b-4a1e-aa1b-8454d345b26f"],
"filterConditions":[]
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "e077d15a-3c02-491e-9bb9-bc0373a13eea",
"created" : "2016-08-12T[Link].914+09:00",
"updated" : "2016-08-12T[Link].914+09:00",
"completed" : "2016-08-12T[Link].914+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"data" : [ ],
"count" : 0
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ChangeHistorys?$query={HQL}&page={page}&pageSize={size}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of ChangeHistory objects. For details about ChangeHistory, see the table
data anyType[]
below.
Attribute Type Description
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
ChangeHistory
{
"instanceID":"...",
"message":"...",
"dateTime":"...",
"nodeId":"...",
"deviceName":"...",
"deviceType":"...",
"componentId":"...",
"componentName":"...",
"componentType":"...",
"attributeType":"...",
"previousValue":"...",
"newValue":"...",
"componentChangeType":"...",
"nodeChangeType":"..."
}
nodeId string ID of the device for which the configuration change occurred
Attribute Type Description
deviceName string Name of the device for which the configuration change occurred
deviceType enum Type of device for which the configuration change occurred
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Server
Storage
NetworkDevice
Datastore
componentId string ID of the component for which the configuration change occurred
componentName string Name of the component for which the configuration change occurred
componentType enum Type of component for which the configuration change occurred
(For details about the valid values, see the table ComponentType in List of
enumerators.)
attributeType enum Attribute type of component for which the configuration change occurred
(For details about the valid values, see the table ComponentAttributeType in
List of enumerators.)
componentChangeType enum Modification type of component for which the configuration change occurred
(For details about the valid values, see the table ChangeEventType in List of
enumerators.)
ADD
MODIFY
REMOVE
nodeChangeType enum Modification type of device for which the configuration change occurred
(For details about the valid values, see the table ChangeEventType in List of
enumerators.)
ADD
MODIFY
REMOVE
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/ChangeHistorys/?HQL::filter=componentId+eq+'vm%23ITPDLab_172.17.17.115
_vm-149' HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 359359188f9afdee4c32c10c6c8bf8567ada4_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"data":
[
{
"instanceID": "16$1201$vm#ITPDLab_172.17.17.115_vm-149$vm#ITPDLab_172.17.17.115_
vm-149$null$1471252355000$MODIFY",
"message": "The number of CPU cores was changed from 2 to 1.
Device name: [Link]
Name of VM: CT003hoshi",
"dateTime": "2016-08-15T[Link].000+09:00",
"nodeId": "h#ITPDLab_172.17.17.115_host-143",
"deviceName": "[Link]",
"deviceType": "Server",
"componentId": "vm#ITPDLab_172.17.17.115_vm-149",
"componentName": "CT003hoshi",
"componentType": "VIRTUAL_MACHINE",
"attributeType": "NUM_OF_CPU_CORES",
"previousValue": "2",
"newValue": "1",
"componentChangeType": "MODIFY",
"nodeChangeType": "MODIFY"
},
{
"instanceID": "16$1202$vm#ITPDLab_172.17.17.115_vm-149$vm#ITPDLab_172.17.17.115_
vm-149$null$1471252355000$MODIFY",
"message": "Memory size was changed from 2.0 GB to 4.0 GB.
Device name: [Link]
Name of VM: CT003hoshi",
"dateTime": "2016-08-15T[Link].000+09:00",
"nodeId": "h#ITPDLab_172.17.17.115_host-143",
"deviceName": "[Link]",
"deviceType": "Server",
"componentId": "vm#ITPDLab_172.17.17.115_vm-149",
"componentName": "CT003hoshi",
"componentType": "VIRTUAL_MACHINE",
"attributeType": "TOTAL_MEMORY",
"previousValue": "2.0 GB",
"newValue": "4.0 GB",
"componentChangeType": "MODIFY",
"nodeChangeType": "MODIFY"
}
],
"count": 2
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ChangeHistorys/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
ChangeHistory
{
"instanceID":"...",
"message":"...",
"dateTime":"...",
"nodeId":"...",
"deviceName":"...",
"deviceType":"...",
"componentId":"...",
"componentName":"...",
"componentType":"...",
"attributeType":"...",
"previousValue":"...",
"newValue":"...",
"componentChangeType":"...",
"nodeChangeType":"..."
}
nodeId string ID of the device for which the configuration change occurred
deviceName string Name of the device for which the configuration change occurred
deviceType enum Type of device for which the configuration change occurred
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Server
Storage
NetworkDevice
Datastore
componentId string ID of the component for which the configuration change occurred
componentName string Name of the component for which the configuration change occurred
componentType enum Type of component for which the configuration change occurred
(For details about the valid values, see the table ComponentType in List of
enumerators.)
attributeType enum Attribute type of component for which the configuration change occurred
(For details about the valid values, see the table ComponentAttributeType in
List of enumerators.)
componentChangeType enum Modification type of component for which the configuration change occurred
(For details about the valid values, see the table ChangeEventType in List of
enumerators.)
Attribute Type Description
ADD
MODIFY
REMOVE
nodeChangeType enum Modification type of device for which the configuration change occurred
(For details about the valid values, see the table ChangeEventType in List of
enumerators.)
ADD
MODIFY
REMOVE
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/ChangeHistorys/16$1201$vm%23ITPDLab_172.17.17.115_vm-149$vm%23ITPDLab_
172.17.17.115_vm-149$null$1471252355000$MODIFY HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 2e48b94f47d976ece069226313cacf394cf613f3_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"instanceID" : "16$1201$vm#ITPDLab_172.17.17.115_vm-149$vm#ITPDLab_172.17.17.115_vm-149$null$1
471252355000$MODIFY",
"message" : "The number of CPU cores was changed from 2 to 1.\nDevice name: [Link]\nNam
e of VM: CT003hoshi",
"dateTime" : "2016-08-15T[Link].000+09:00",
"nodeId" : "h#ITPDLab_172.17.17.115_host-143",
"deviceName" : "[Link]",
"deviceType" : "Server",
"componentId" : "vm#ITPDLab_172.17.17.115_vm-149",
"componentName" : "CT003hoshi",
"componentType" : "VIRTUAL_MACHINE",
"attributeType" : "NUM_OF_CPU_CORES",
"previousValue" : "2",
"newValue" : "1",
"componentChangeType" : "MODIFY",
"nodeChangeType" : "MODIFY"
}
Related reference
List of enumerators
You can obtain a list of operations related to configuration changes, such as the operation to obtain the number of configuration
changes.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/ChangeHistorys/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
Attribute Type Description
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/ChangeHistorys/actions HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 9037e7cbddbbe472bd66ecc5496554253a4e0_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getTrend",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "getCount",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 2
}
The following operation is the initial step to obtain the number of configuration changes.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/ChangeHistorys/actions/getCount
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetChangeCountParam
{
"nodeIDs":["...", ...],
"deviceTypes":["...", ...],
"countFrom":"...",
"countTo":"...",
"interval":"..."
}
nodeIDs long[] ID of the device for which the configuration change occurred
deviceTypes enum[] Type of device for which the configuration change occurred
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Attribute Type Description
Server
Storage
NetworkDevice
Datastore
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/ChangeHistorys/actions/getCount HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Tue, 23 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO be34d9f31129bb09cf2b1a132b6d5c28e81be1_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"name" : "getCount",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"nodeIDs" : [ ],
"deviceTypes" : [ "Server", "NetworkDevice", "Storage" ],
"countFrom" : "2016-08-22T[Link].236+09:00",
"countTo" : "2016-08-23T[Link].236+09:00",
"interval" : 3600000
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/ChangeHistorys/actions/getCount/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetChangeCountParam
{
"nodeIDs":["...", ...],
"deviceTypes":["...", ...],
"countFrom":"...",
"countTo":"...",
"interval":"..."
}
nodeIDs long[] ID of the device for which the configuration change occurred
deviceTypes enum[] Type of device for which the configuration change occurred
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Server
Storage
NetworkDevice
Datastore
Response body
The structure of the response body and the object attributes is as follows:
ChangeCount
{
"deviceType":"...",
"periodFrom":"...",
"count":"..."
}
deviceType enum Type of device for which the configuration change occurred
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Server
Storage
NetworkDevice
Datastore
periodFrom dateTime Start time for the aggregation of the configuration change history
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/ChangeHistorys/actions/getCount/invoke HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "getCount",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"nodeIDs" : [ ],
"deviceTypes" : [ "Server" ],
"countFrom" : "2016-08-22T[Link].236+09:00",
"countTo" : "2016-08-23T[Link].236+09:00",
"interval" : 3600000
} ]
}
[Response Header]
HTTP/1.1 200 OK
Date: Tue, 23 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO d5edd16e4304d187c184cff39dc443fae882c0_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"instanceID" : "d0d9f541-62e6-450d-8a8e-abbbdf04586a",
"created" : "2016-08-23T[Link].408+09:00",
"updated" : "2016-08-23T[Link].408+09:00",
"completed" : "2016-08-23T[Link].408+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"deviceType" : "Server",
"periodFrom" : "2016-08-22T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-22T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-22T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 7
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 11
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 6
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 1
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 0
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 2
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 5
}, {
"deviceType" : "Server",
"periodFrom" : "2016-08-23T[Link].236+09:00",
"count" : 8
} ]
}
Related reference
List of enumerators
The following operation is the initial step to obtain the trend in the number of configuration changes.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/ChangeHistorys/actions/getTrend
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetChangeCountParam
{
"nodeIDs":["...", ...],
"deviceTypes":["...", ...],
"countFrom":"...",
"countTo":"...",
"interval":"..."
}
nodeIDs long[] ID of the device for which the configuration change occurred
deviceTypes enum[] Type of device for which the configuration change occurred
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Server
Storage
NetworkDevice
Datastore
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/ChangeHistorys/actions/getTrend HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8f67a6685c3ef67d7b35a2b23a597504984a5_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"name" : "getTrend",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"countFrom" : "2016-08-21T[Link].931+09:00",
"countTo" : "2016-08-22T[Link].931+09:00",
"interval" : 3600000
} ]
}
Related reference
List of enumerators
Getting trend in the number of configuration changes
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/ChangeHistorys/actions/getTrend/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetChangeCountParam
{
"nodeIDs":["...", ...],
"deviceTypes":["...", ...],
"countFrom":"...",
"countTo":"...",
"interval":"..."
}
nodeIDs long[] ID of the device for which the configuration change occurred
Attribute Type Description
deviceTypes enum[] Type of device for which the configuration change occurred
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Server
Storage
NetworkDevice
Datastore
Response body
The structure of the response body and the object attributes is as follows:
ChangeCount
{
"deviceType":"...",
"periodFrom":"...",
"count":"..."
}
deviceType enum Type of device for which the configuration change occurred
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Server
Storage
NetworkDevice
Datastore
periodFrom dateTime Start time for the aggregation of the configuration change history
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/ChangeHistorys/actions/getTrend/invoke HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "getTrend",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters":
[
{
"countFrom": "2016-08-21T[Link].931+09:00",
"countTo": "2016-08-22T[Link].931+09:00",
"interval": 3600000
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO d7cc224d2febee6f4345b8c1913f46150f9a8_YXZvNFILd2IcDAIaWXcFMFR3FVc=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"instanceID" : "d7a87b6b-ddd8-49c9-b890-16a27ae95727",
"created" : "2016-08-22T[Link].243+09:00",
"updated" : "2016-08-22T[Link].243+09:00",
"completed" : "2016-08-22T[Link].243+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"periodFrom" : "2016-08-21T[Link].931+09:00",
"count" : 110
}, {
"periodFrom" : "2016-08-21T[Link].931+09:00",
"count" : 13
}, {
"periodFrom" : "2016-08-21T[Link].931+09:00",
"count" : 5
}, {
"periodFrom" : "2016-08-21T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-21T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-21T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-21T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-21T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 2
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 3
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 0
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 15
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 30
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 80
}, {
"periodFrom" : "2016-08-22T[Link].931+09:00",
"count" : 55
} ]
}
Related reference
List of enumerators
You can obtain a list of operations that the execute action function can perform.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data": [
{
"name": "getActionTemplateList",
"href": "[Link]
teList/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
},
{
"name": "getMailActionTemplateDetail",
"href": "[Link]
mplateDetail/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
},
{
"name": "getCommandActionTemplateDetail",
"href": "[Link]
nTemplateDetail/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
},
{
"name": "invokeCommandAction",
"href": "[Link]
tion/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
},
{
"name": "invokeReload",
"href": "[Link]
voke",
"method": "POST",
"type": "application/json",
"parameters": []
},
{
"name": "getResourcesCommandActionTemplateDetail",
"href": "[Link]
mandActionTemplateDetail/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
},
{
"name": "getResourcesAutomationDirectorServiceActionTemplateDetail",
"href": "[Link]
omationDirectorServiceActionTemplateDetail/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
},
{
"name": "invokeResourcesCommandAction",
"href": "[Link]
CommandAction/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
},
{
"name": "getResourcesActionTemplateList",
"href": "[Link]
ionTemplateList/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
}
],
"count": 9
}
Preparing to obtain a list of actions that can be executed by the execute action function
The following operation is the initial step to obtain a list of actions that the execute action function can perform.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/getActionTemplateList
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetActionTemplateListParam
{
"componentID":"...",
"nodeID":"...",
"targetTypes":["...", ...]
}
componentID string ID of the component specified as the action execution target. The ID of the
device that the component belongs to must also be specified. To execute an
action for a device, omit this parameter.
(For details about the valid values, see the table TemplateType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/getActionTemplateList
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getActionTemplateList",
"href" : "[Link]
ist/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"componentID" : "0",
"nodeID" : "0"
} ]
}
Getting a list of actions that can be executed by the execute action function
You can obtain a list of actions that the execute action function can perform.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/getActionTemplateList/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetActionTemplateListParam
{
"componentID":"...",
"nodeID":"...",
"targetTypes":["...", ...]
}
componentID string ID of the component specified as the action execution target. The ID of the
device that the component belongs to must also be specified. To execute an
Attribute Type Description
(For details about the valid values, see the table TemplateType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
ActionTemplate
{
"instanceID":"...",
"name":"...",
"description":"...",
"templateFileName":"...",
"templateType":"...",
"multipleResources":"...",
"automationDirectorServiceGroupName":"...",
"automationDirectorServiceName":"..."
}
templateFileName string Name of the template file in which the action is registered
(For details about the valid values, see the table TemplateType in List of
enumerators.)
COMMAND
MAIL
multipleResources boolean Whether the template supports the use of multiple resource IDs
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/CustomAction/actions/getActionTemplateList/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getActionTemplateList",
"href": "[Link]
st/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"nodeID":"h#ITPDLab_172.17.17.115_host-258"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "4bc7ea0e-284a-4fab-a4fe-ba8a8ace40fe",
"created" : "2016-08-12T[Link].855+09:00",
"updated" : "2016-08-12T[Link].711+09:00",
"completed" : "2016-08-12T[Link].711+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"instanceID" : 0,
"name" : "MailActionTemplate",
"description" : "mail template description",
"templateFileName" : "/opt/hitachi/Analytics/conf/template/mail/[Link]",
"templateType" : "MAIL"
}, {
"instanceID" : 1,
"name" : "CommandActionTemplate",
"description" : "command template description",
"templateFileName" : "/opt/hitachi/Analytics/conf/template/command/[Link]",
"templateType" : "COMMAND"
} ]
}
Related reference
List of enumerators
Preparing to obtain a detailed information about emails that can be sent by the execute action
function
The following operation is the initial step to obtain details about emails that the execute action function can send.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/getMailActionTemplateDetail
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
{
"componentID":"...",
"nodeID":"...",
"templateFileName":"..."
}
componentID string ID of the component specified as the action execution target. The ID of the
device that the component belongs to must also be specified. To execute an
action for a device, omit this parameter.
templateFileName string Name of the template file in which the action is registered
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/getMailActionTemplateDetail
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getMailActionTemplateDetail",
"href" : "[Link]
ateDetail/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"componentID" : "0",
"nodeID" : "0",
"templateFileName" : ""
} ]
}
Getting detailed information about emails that can be sent by the execute action function
You can obtain details about emails that the execute action function can send.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/getMailActionTemplateDetail/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
{
"componentID":"...",
"nodeID":"...",
"templateFileName":"..."
}
componentID string ID of the component specified as the action execution target. The ID of the
device that the component belongs to must also be specified. To execute an
action for a device, omit this parameter.
templateFileName string Name of the template file in which the action is registered
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
MailActionTemplateDetail
{
"destAddress":"...",
"subject":"...",
"textBody":"..."
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/CustomAction/actions/getMailActionTemplateDetail/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getMailActionTemplateDetail",
"href": "[Link]
teDetail/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"nodeID":"h#ITPDLab_172.17.17.115_host-258",
"templateFileName":"/opt/hitachi/Analytics/conf/template/mail/[Link]"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "17d6136c-ffae-48fb-bf70-57f481954a0f",
"created" : "2016-08-12T[Link].200+09:00",
"updated" : "2016-08-12T[Link].379+09:00",
"completed" : "2016-08-12T[Link].379+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"destAddress" : "admin@[Link]",
"subject" : "mail subject",
"textBody" : "mail text"
} ]
}
Preparing to obtain a detailed information about commands that can be sent by the execute
action function
The following operation is the initial step to obtain details about commands that the execute action function can run.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/getCommandActionTemplateDetail
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetCommandActionTemplateDetailParam
{
"componentID":"...",
"nodeID":"...",
"templateFileName":"..."
}
componentID string ID of the component specified as the action execution target. The ID of the
device that the component belongs to must also be specified. To execute an
action for a device, omit this parameter.
templateFileName string Name of the template file in which the action is registered
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/getCommandActionTemplateDetail
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getCommandActionTemplateDetail",
"href" : "[Link]
mplateDetail/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"componentID" : "0",
"nodeID" : "0",
"templateFileName" : ""
} ]
}
Getting detailed information about commands that can be executed by the execute action
function
You can obtain details about commands that the execute action function can run.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/getCommandActionTemplateDetail/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetCommandActionTemplateDetailParam
{
"componentID":"...",
"nodeID":"...",
"templateFileName":"..."
}
componentID string ID of the component specified as the action execution target. The ID of the
device that the component belongs to must also be specified. To execute an
action for a device, omit this parameter.
templateFileName string Name of the template file in which the action is registered
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
CommandActionTemplateDetail
{
"actionName":"...",
"description":"...",
"commandName":"...",
"commandParameter":"...",
"usage":"..."
}
CommandActionTemplateDetail (Type: CommandActionTemplateDetail)
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/CustomAction/actions/getCommandActionTemplateDetail/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getCommandActionTemplateDetail",
"href": "[Link]
plateDetail/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"nodeID":"h#ITPDLab_172.17.17.115_host-258",
"templateFileName":"/opt/hitachi/Analytics/conf/template/command/[Link]"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "a8e900fa-087e-4a24-a023-1d8f0a5aeebb",
"created" : "2016-08-12T[Link].468+09:00",
"updated" : "2016-08-12T[Link].636+09:00",
"completed" : "2016-08-12T[Link].636+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"actionName" : "CommandActionTemplate",
"description" : "command template description",
"commandName" : "/opt/hitachi/Analytics/bin/command/[Link]",
"commandParameter" : "-param CommandParam"
} ]
}
Preparing to execute commands that can be executed by the execute action function
The following operation is the initial step to invoke commands that the execute action function can run.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/invokeCommandAction
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
InvokeCommandActionParam
{
"componentID":"...",
"nodeID":"...",
"templateFileName":"...",
"commandParameter":"..."
}
componentID string ID of the component specified as the action execution target. The ID of the
device that the component belongs to must also be specified. To execute an
action for a device, omit this parameter.
templateFileName string Name of the template file in which the action is registered
commandParameter string Parameter for the command to be executed. Set a string encoded in Base64.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/invokeCommandAction
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "invokeCommandAction",
"href" : "[Link]
n/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"componentID" : "0",
"nodeID" : "0",
"templateFileName" : "",
"commandParameter" : ""
} ]
}
You can invoke commands that the execute action function can run.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/invokeCommandAction/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
InvokeCommandActionParam
{
"componentID":"...",
"nodeID":"...",
"templateFileName":"...",
"commandParameter":"..."
}
componentID string ID of the component specified as the action execution target. The ID of the
device that the component belongs to must also be specified. To execute an
action for a device, omit this parameter.
templateFileName string Name of the template file in which the action is registered
commandParameter string Parameter for the command to be executed. Set a string encoded in Base64.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/CustomAction/actions/invokeCommandAction/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "invokeCommandAction",
"href": "[Link]
n/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"nodeID":"h#ITPDLab_172.17.17.115_host-258",
"templateFileName":"/opt/hitachi/Analytics/conf/template/command/[Link]",
"commandParameter":""
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "b3fe1e36-1737-426c-bdd2-c5706472e2bc",
"created" : "2016-08-12T[Link].366+09:00",
"updated" : "2016-08-12T[Link].409+09:00",
"completed" : "2016-08-12T[Link].409+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Preparing to reload a list of actions that can be executed by the execute action function
The following operation is the initial step to reload a list of actions that the execute action function can perform.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/invokeReload
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/invokeReload
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "invokeReload",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
Reloading a list of actions that can be executed by the execute action function
You can reload a list of actions that the execute action function can perform.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/invokeReload/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
CommandActionReloadResult
{
"instanceID":"...",
"readFileCount":"...",
"readFileSuccessCount":"..."
}
Status codes
200 OK Success.
Example code
[Request Header]
POST
[Link]
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "invokeReload",
"href": "[Link]
e",
"method": "POST",
"type": "application/json",
"parameters":[]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "5a160d64-43fd-4390-b7ed-abdff6bf642a",
"created" : "2016-08-12T[Link].914+09:00",
"updated" : "2016-08-12T[Link].928+09:00",
"completed" : "2016-08-12T[Link].928+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"readFileCount" : 2,
"readFileSuccessCount" : 2
} ]
}
Preparing to get a list of the actions that can be executed by using the execute action function of
the target resources
The following operation is the initial step to obtain a list of actions that the execute action function can perform on multiple
resources.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/getResourcesActionTemplateList
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetResourcesActionTemplateListParam
{
"resourceIDs":["...", ...]
}
resourceIDs string[] List of the IDs of the components and devices for which the action is to be
executed
Status codes
200 OK Success.
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/getResourcesActionTemplateList
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name": "getResourcesActionTemplateList",
"href": "[Link]
emplateList/invoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"instanceID": 0,
"resourceIDs": [
"ResourceID 0",
"ResourceID 1"
]
}
]
}
Getting a list of the actions that can be executed by using the execute action function of the
target resources
You can obtain a list of actions that the execute action function can perform on multiple resources.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/getResourcesActionTemplateList/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetResourcesActionTemplateListParam
{
"resourceIDs":["...", ...]
}
resourceIDs string[] List of the IDs of the components and devices for which the action is to be
executed
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
ActionTemplate
{
"instanceID":"...",
"name":"...",
"description":"...",
"templateFileName":"...",
"templateType":"...",
"multipleResources":"...",
"automationDirectorServiceGroupName":"...",
"automationDirectorServiceName":"..."
}
templateFileName string Name of the template file in which the action is registered
(For details about the valid values, see the table TemplateType in List of
enumerators.)
COMMAND
Attribute Type Description
multipleResources boolean Whether the template supports the use of multiple resource IDs
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/CustomAction/actions/getResourcesActionTemplateList/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "getResourcesActionTemplateList",
"href" : "[Link]
TemplateList/invoke",
"method" : "POST",
"type" : "application/json",
"parameters": [
{
"resourceIDs": [
"raidLdev#12345-00^01^11",
"raidLdev#12345-00^2F^AC"
]
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "4bc7ea0e-284a-4fab-a4fe-ba8a8ace40fe",
"created" : "2016-08-12T[Link].855+09:00",
"updated" : "2016-08-12T[Link].711+09:00",
"completed" : "2016-08-12T[Link].711+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"instanceID" : 0,
"name" : "MailActionTemplate",
"description" : "mail template description",
"templateFileName" : "/opt/hitachi/Analytics/conf/template/mail/[Link]",
"templateType" : "MAIL",
"multipleResources": false
}, {
"instanceID" : 1,
"name" : "CommandActionTemplate",
"description" : "command template description",
"templateFileName" : "/opt/hitachi/Analytics/conf/template/command/[Link]",
"templateType" : "COMMAND",
"multipleResources": false
} ]
}
Related reference
List of enumerators
Preparing to get detailed information about the commands that can be executed by using the
execute action function of the target resource
The following operation is the initial step to obtaining details about commands that the execute action function can run on
multiple resources.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/getResourcesCommandActionTemplateDetail
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetResourcesCommandActionTemplateDetailParam
{
"resourceIDs":["...", ...],
"templateFileName":"..."
}
resourceIDs string[] List of the IDs of the components and devices for which the action is to be
executed
templateFileName string Name of the template file in which the action is registered
Status codes
200 OK Success.
Status code Reason phrase Description
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/getResourcesCommandActionTemplateDetail
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name": "getResourcesCommandActionTemplateDetail",
"href": "[Link]
ActionTemplateDetail/invoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"instanceID": 0,
"resourceIDs": [
"ResourceID 0",
"ResourceID 1"
],
"templateFileName": "Template File Name"
}
]
}
Getting detailed information about the commands that can be executed by using the execute
action function of the target resource
You can obtain details about commands that the execute action function can run on multiple resources.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/getResourcesCommandActionTemplateDetail/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetResourcesCommandActionTemplateDetailParam
{
"resourceIDs":["...", ...],
"templateFileName":"..."
}
resourceIDs string[] List of the IDs of the components and devices for which the action is to be
executed
templateFileName string Name of the template file in which the action is registered
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
CommandActionTemplateDetail
{
"actionName":"...",
"description":"...",
"commandName":"...",
"commandParameter":"...",
"usage":"..."
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/CustomAction/actions/getResourcesCommandActionTemplateDetail/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "getResourcesCommandActionTemplateDetail",
"href" : "[Link]
dActionTemplateDetail/invoke",
"method" : "POST",
"type" : "application/json",
"parameters": [
{
"resourceIDs": [
"raidLdev#12345-00^01^11",
"raidLdev#12345-00^2F^AC"
],
"templateFileName": "/opt/hitachi/Analytics/conf/template/command/[Link]"
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "a8e900fa-087e-4a24-a023-1d8f0a5aeebb",
"created" : "2016-08-12T[Link].468+09:00",
"updated" : "2016-08-12T[Link].636+09:00",
"completed" : "2016-08-12T[Link].636+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"actionName" : "CommandActionTemplate",
"description" : "command template description",
"commandName" : "/opt/hitachi/Analytics/bin/command/[Link]",
"commandParameter" : "-param CommandParam"
} ]
}
Preparing to execute a command using the execute action function of the target resource
The following operation is the initial step to invoke commands that the execute action function can run on multiple resources.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/invokeResourcesCommandAction
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
InvokeResourcesCommandActionParam
{
"resourceIDs":["...", ...],
"templateFileName":"...",
"commandParameter":"..."
}
resourceIDs string[] List of the IDs of the components and devices for which the action is to be
executed
templateFileName string Name of the template file in which the action is registered
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/invokeResourcesCommandAction
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name": "invokeResourcesCommandAction",
"href": "[Link]
andAction/invoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"instanceID": 0,
"resourceIDs": [
"ResourceID 0",
"ResourceID 1"
],
"templateFileName": "Template File Name",
"commandParameter": "Command Parameter"
}
]
}
Executing a command using the execute action function of the target resource
You can invoke commands that the execute action function can run on multiple resources.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/invokeResourcesCommandAction/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
InvokeResourcesCommandActionParam
{
"resourceIDs":["...", ...],
"templateFileName":"...",
"commandParameter":"..."
}
resourceIDs string[] List of the IDs of the components and devices for which the action is to be
executed
templateFileName string Name of the template file in which the action is registered
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/CustomAction/actions/invokeResourcesCommandAction/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "invokeResourcesCommandAction",
"href" : "[Link]
mandAction/invoke",
"method" : "POST",
"type" : "application/json",
"parameters": [
{
"resourceIDs": [
"raidLdev#12345-00^01^11",
"raidLdev#12345-00^2F^AC"
],
"templateFileName": "/opt/hitachi/Analytics/conf/template/command/[Link]",
"commandParameter": ""
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "b3fe1e36-1737-426c-bdd2-c5706472e2bc",
"created" : "2016-08-12T[Link].366+09:00",
"updated" : "2016-08-12T[Link].409+09:00",
"completed" : "2016-08-12T[Link].409+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Getting information needed to get details about an Ops Center Automator service that is
executable by the execute action function
You can get information that needs to be specified in a request to get details about an Ops Center Automator service that is
executable by the execute action function.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/CustomAction/actions/getResourcesAutomationDirectorServiceActionTemplate
Detail
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
A list of GetResourcesAutomationDirectorServiceActionTemplateDetailParam
parameters anyType[]
objects necessary to execute an operation. For details about
GetResourcesAutomationDirectorServiceActionTemplateDetailParam, see the
table below.
GetResourcesAutomationDirectorServiceActionTemplateDetailParam
{
"resourceIDs":["...", ...],
"serviceGroupName":"...",
"serviceName":"..."
}
GetResourcesAutomationDirectorServiceActionTemplateDetailParam (Type:
GetResourcesAutomationDirectorServiceActionTemplateDetailParam)
resourceIDs string[] A list of IDs for the components and devices for which an action is to be
executed
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/CustomAction/actions/getResourcesAutomationDirectorServiceActionTempl
ateDetail
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 25 Aug 2017 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 384d86cd8397edfd44e093e28ff2dcf1b563e471_UQV8dA9cIGw=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name": "getResourcesAutomationDirectorServiceActionTemplateDetail",
"href": "[Link]
ionDirectorServiceActionTemplateDetail/invoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"instanceID": 0,
"resourceIDs": [
"ResourceID 0",
"ResourceID 1"
],
"serviceGroupName": "A Service Group Name",
"serviceName": "A Service Name"
}
]
}
Getting details about an Ops Center Automator service that is executable by the execute action
function
You can get details about an Ops Center Automator service that is executable by the execute action function.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/CustomAction/actions/getResourcesAutomationDirectorServiceActionTemplat
eDetail/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
A list of GetResourcesAutomationDirectorServiceActionTemplateDetailParam
parameters anyType[]
objects necessary to execute an operation. For details about
GetResourcesAutomationDirectorServiceActionTemplateDetailParam, see the
table below.
GetResourcesAutomationDirectorServiceActionTemplateDetailParam
{
"resourceIDs":["...", ...],
"serviceGroupName":"...",
"serviceName":"..."
}
GetResourcesAutomationDirectorServiceActionTemplateDetailParam (Type:
GetResourcesAutomationDirectorServiceActionTemplateDetailParam)
resourceIDs string[] A list of IDs for the components and devices for which an action is to be
executed
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/CustomAction/actions/getResourcesAutomationDirectorServiceActionTemp
lateDetail/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getResourcesAutomationDirectorServiceActionTemplateDetail",
"href": "[Link]
ionDirectorServiceActionTemplateDetail/invoke",
"method": "POST",
"parameters": [
{
"resourceIDs": [
"vm#0",
"vm#1"
],
"serviceGroupName": "Default Service Group",
"serviceName": "Stop Virtual Machine"
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 25 Aug 2017 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 42e4c1b3a553126bd3fabc3bebd4ceaa67719af_ZAlDR1YdfRJUBwFo_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID": "262a79a0-3e17-4483-9fa4-73075ee7369a",
"created": "2017-08-25T[Link].741+09:00",
"updated": "2017-08-25T[Link].742+09:00",
"completed": "2017-08-25T[Link].742+09:00",
"state": "success",
"affectedResource": [],
"result": [
{
"serviceGroupName": "Default Service Group",
"serviceName": "Stop Virtual Machine",
"description": "Stops multiple virtual servers in a VMware vSphere environment.",
"automationDirectorServiceWindowUrl": "[Link]
"automationDirectorLaunchParams": [
{
"key": "sg",
"value": "Default Service Group"
},
{
"key": "sn",
"value": "Stop Virtual Machine"
}
],
"automationDirectorMainWindowUrl": "[Link]
}
]
}
You can obtain a list of resources and resource-related information, such as information about hypervisors, storages, switches,
and hosts.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/DiscoveredResources?page={page}&pageSize={size}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
DiscoveredResource
{
"instanceID":"...",
"name":"...",
"ipAddress":"...",
"status":"...",
"monitorStatus":"...",
"description":"...",
"clusterName":"...",
"vmName":"...",
"modelID":"...",
"modelName":"...",
"wwn":"...",
"resourceType":"...",
"thresholdProfileID":"...",
"thresholdProfileName":"...",
"groupIDs":["...", ...],
"groupNames":["...", ...],
"gradeNames":["...", ...],
"gradeOrders":["...", ...],
"profileResourceType":"...",
"ipAddressIDs":["...", ...],
"ipAddresses":["...", ...],
"componentCriticalCount":"...",
"componentWarningCount":"...",
"componentTotalCount":"...",
"assignmentSchedule":"..."
}
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
(For details about the valid values, see the table ManagementLevelType in List
of enumerators.)
Manage
(For details about the valid values, see the table ArgusNodeType in List of
enumerators.)
SERVER_WINDOWS
SERVER_LINUX
SERVER_ESX
SWITCH_FC
STORAGE_HITACHI
STORAGE_OTHER
Attribute Type Description
SERVER_HYPERV
SERVER_VCENTER
gradeNames string[] Name of the grade of the consumer assigned to the device.
gradeOrders integer[] Priority of the grade of the consumer assigned to the device.
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/DiscoveredResources
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 1d8dd66aa77a72e2843aef7e599e12dc8a1bbdf3_Y2UOI2pkMXQ=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data": [
{
"instanceID": "h#ITPDLab_172.17.17.115_host-158",
"name": "[Link]",
"status": "Normal",
"monitorStatus": "Manage",
"description": "HITACHI BladeSymphony F51 VMware ESXi N/A",
"resourceType": "SERVER_ESX",
"thresholdProfileID": "thProfile#ESX",
"thresholdProfileName": "Default Profile for Hypervisor (VMware)",
"groupIDs": [
],
"groupNames": [
],
"gradeNames": [
],
"gradeOrders": [
],
"profileResourceType": "ESX",
"ipAddressIDs": [
"pn#ITPDLab_172.17.17.115_host-158^vmnic0",
"pn#ITPDLab_172.17.17.115_host-158^vmnic1"
],
"ipAddresses": [
],
"componentCriticalCount": 0,
"componentWarningCount": 0
},
{
..........
},
..........
],
"count": 5
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/E2EView?basePointNodeType={E2ENodeType}&basePointNodeID={nodeID}&targetNo
deType={E2ENodeType}&parentNodeID={nodeID}&page={page}&pageSize={size}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
Filtering conditions:
Checks whether the value is included in the comparison target. Multiple values
separated by a comma (,) can be specified.
Filtering conditions:
Filtering conditions:
Checks whether the value is included in the comparison target. Multiple values
separated by a comma (,) can be specified.
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of E2ENode objects. For details about E2ENode, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
E2ENode
{
"instanceID":"...",
"name":"...",
"type":"...",
"status":"...",
"consumerName":"...",
"gradeName":"...",
"gradeOrder":"...",
"additional":"...",
"parentID":"...",
"parentType":"...",
"description":"...",
"label":"...",
"nvmHostNicknames":["...", ...],
"hostGroupIDs":["...", ...],
"hostGroupNames":["...", ...],
"lunOwnerIDs":["...", ...],
"lunOwnerNames":["...", ...],
"poolSavingRatio":"...",
"datastoreType":"...",
"datastoreCapacity":"..."
}
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Attribute Type Description
Warning
Critical
Unknown
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
lunOwnerNames string[] Name of the LUN owner that a volume is associated with.
poolSavingRatio float The capacity savings ratio with the controller-based capacity saving and
accelerated compression features in a pool.
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/E2EView/?basePointNodeID[]=h%23ABC_172.17.17.115_host-195&basePointNod
eType=HYPERVISOR&targetNodeType=CPU&parentNodeID=h%23ABC_172.17.17.115_host-195
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "cpu#ABC_172.17.17.115_host-195^0",
"name" : "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz#0",
"type" : "CPU",
"status" : "Unknown",
"additional" : "[Link]",
"parentID" : "h#ABC_172.17.17.115_host-195",
"parentType" : "HYPERVISOR"
}, {
........
} ],
"count" : 8
}
Related reference
List of enumerators
Preparing to obtain topology data for resources that are displayed in the E2E view
The following operation is the initial step to obtain the topology data of resources displayed in the E2E view.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/E2EView/actions/getTopologyData
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2EViewParam
{
"basePointNodeID":["...", ...],
"basePointNodeType":"..."
}
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/E2EView/actions/getTopologyData
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getTopologyData",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"basePointNodeID" : [ ],
"basePointNodeType" : "HYPERVISOR"
} ]
}
Related reference
List of enumerators
Getting topology data for resources that are displayed in the E2E view
You can obtain the topology data of resources displayed in the E2E view.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/E2EView/actions/getTopologyData/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2EViewParam
{
"basePointNodeID":["...", ...],
"basePointNodeType":"..."
}
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
E2ETopologyData
{
"basePointNodeName":"...",
"hasHighlightData":"...",
"customer":{
"count":"...",
"customerGradeList":[{
"name":"...",
"order":"...",
"customers":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
]
},
:
]
},
"server":{
"count":"...",
"clusterList":[{
"instanceID":"...",
"name":"...",
"hypervisors":[{
"instanceID":"...",
"name":"...",
"status":"...",
"hosts":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
],
"components":[{
"name":"...",
"type":"...",
"items":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
]
},
:
],
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"profileResourceType":"..."
},
:
],
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
]
},
:
],
"nonclusteredHypervisorList":[{
"instanceID":"...",
"name":"...",
"status":"...",
"hosts":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
],
"components":[{
"name":"...",
"type":"...",
"items":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
]
},
:
],
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"profileResourceType":"..."
},
:
],
"otherserverHostList":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
]
},
"datastore":{
"count":"...",
"datastoreGroupList":[{
"instanceID":"...",
"name":"...",
"datastores":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
]
},
:
]
},
"network":{
"count":"...",
"sanList":[{
"instanceID":"...",
"name":"...",
"switches":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
]
},
:
]
},
"storage":{
"count":"...",
"storageList":[{
"instanceID":"...",
"name":"...",
"status":"...",
"volumes":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
],
"components":[{
"name":"...",
"type":"...",
"items":[{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
},
:
]
},
:
],
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"profileResourceType":"..."
},
:
]
}
}
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Attribute Type Description
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
Attribute Type Description
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
Attribute Type Description
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
200 OK Success.
[Request Header]
POST /Analytics/v1/services/E2EView/actions/getTopologyData/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getTopologyData",
"href": "[Link]
"method": "POST",
"type": "application/json",
"parameters":[{
"basePointNodeID":["h#ABC_172.17.17.115_host-195"],
"basePointNodeType":"HYPERVISOR"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "dba6253d-0514-43e3-b63b-8260b37b3cef",
"created" : "2016-07-20T[Link].022+09:00",
"updated" : "2016-07-20T[Link].023+09:00",
"completed" : "2016-07-20T[Link].023+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"basePointNodeName" : "[Link]",
"hasHighlightData" : true,
"customer" : {
"count" : 0,
"customerGradeList" : [ ]
},
"server" : {
"count" : 11,
"clusterList" : [ ],
"nonclusteredHypervisorList" : [ {
"instanceID" : "h#ABC_172.17.17.115_host-195",
"name" : "[Link]",
"status" : "UNKNOWN",
"hosts" : [ {
"instanceID" : "vm#ABC_172.17.17.115_vm-350",
"name" : "CT5_DT005_e",
"status" : "UNKNOWN",
"relatedNodeList" : [ {
"instanceID" : "cpu#ABC_172.17.17.115_host-195^2",
"type" : "CPU",
"componentType" : "CPU",
"profileResourceType" : "ESX"
}, {
........
} ],
"shareRate" : 100,
"profileResourceType" : "ESX_VM"
}, {
............
} ],
"components" : [ {
"name" : "CPU",
"type" : "CPU",
"items" : [ {
"instanceID" : "cpu#ABC_172.17.17.115_host-195^0",
"name" : "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz#0",
"status" : "UNKNOWN",
"relatedNodeList" : [ {
"instanceID" : "vm#ABC_172.17.17.115_vm-488",
"type" : "VIRTUAL_MACHINE",
"componentType" : "VIRTUAL_MACHINE",
"profileResourceType" : "ESX_VM"
}, {
..........
} ],
"shareRate" : 100,
"profileResourceType" : "ESX"
} ]
}, {
........
} ],
},
.............
"externalStorage" : {
"count" : 0,
"storageList" : [ ]
}
} ]
}
Related reference
List of enumerators
Preparing to obtain details about resources that are displayed in the E2E view
The following operation is the initial step to obtain details about resources displayed in the E2E view.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/E2EView/actions/getNodeDetail
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2ENodeDetailParam
{
"targetNodeID":"...",
"targetNodeType":"..."
}
targetNodeType enum Type of the resources for which details are to be obtained
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/E2EView/actions/getNodeDetail
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getNodeDetail",
"href" : "[Link]
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"targetNodeID" : "0",
"targetNodeType" : "HYPERVISOR"
} ]
}
Related reference
List of enumerators
Getting details about resources that are displayed in the E2E view
You can obtain details about resources displayed in the E2E view.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/E2EView/actions/getNodeDetail/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2ENodeDetailParam
{
"targetNodeID":"...",
"targetNodeType":"..."
}
targetNodeType enum Type of the resources for which details are to be obtained
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
E2ENodeDetailData
{
"nodeInformation":{
"name":"...",
"status":"...",
"description":"...",
"powerstatus":"...",
"vendor":"...",
"operatingSystem":"...",
"processor":"...",
"memory":"...",
"hypervisorName":"...",
"hypervisorType":"...",
"model":"...",
"serialNumber":"...",
"firmware":"...",
"managementIPAddress":"...",
"numberOfPorts":"...",
"subnet":"...",
"fabric":"...",
"capacity":"...",
"cluster":"...",
"hostName":"...",
"uuid":"...",
"totalCache":"...",
"storage":"...",
"label":"...",
"copyType":"...",
"storageTotalEfficiencyRatio":"...",
"storageDataReductionRatio":"...",
"storageSoftwareSavingRatio":"...",
"storageAcSavingRatio":"...",
"storageSnapshotEfficiencyRatio":"...",
"storageProvisioningEfficiency":"...",
"storageCalculationTimeRange":{
"calculationStartTime":,
"calculationEndTime":
},
"poolName":"...",
"poolType":"...",
"poolID":"...",
"poolTouchedCapacity":"...",
"poolUsageRate":"...",
"poolPhysicalCapacity":"...",
"poolPhysicalCapacityUsed":"...",
"poolPhysicalCapacityUsageRate":"...",
"poolDataSaving":"...",
"poolUserDataCapacity":"...",
"poolSavingRatio":"...",
"poolSavingCapacity":"...",
"dkcSavingRatio":"...",
"dkcCompressionRatio":"...",
"dkcDedupRatio":"...",
"dkcSavingCapacity":"...",
"dkcCompressionCapacity":"...",
"dkcDedupCapacity":"...",
"dkcReclaimCapacity":"...",
"dkcSystemCapacity":"...",
"dkcPreProcCapacity":"...",
"fmcSavingCapacity":"...",
"fmcCompressionRatio":"...",
"fmcCompressionCapacity":"...",
"fmcReclaimCapacity":"...",
"fmcPhysicalCapacity":"...",
"fmcPhysicalCapacityUsed":"...",
"fmcLogicalCapacity":"...",
"fmcLogicalCapacityUsed":"...",
"poolAutoExpansion":"...",
"poolTotalEfficiencyRatio":"...",
"poolDataReductionRatio":"...",
"poolSoftwareSavingRatio":"...",
"poolAcSavingRatio":"...",
"poolSnapshotEfficiencyRatio":"...",
"poolProvisioningEfficiency":"...",
"poolCalculationTimeRange":{
"calculationStartTime":,
"calculationEndTime":
},
"driveType":"...",
"displayDriveType":"...",
"driveSpeed":"...",
"raidLevel":"...",
"driveStatus":"...",
"usedSpareDriveCount":"...",
"usedEnduranceIndicator":"...",
"batteryLifeIndicator":"...",
"chipType":"...",
"consumerName":"...",
"gradeName":"...",
"userResourceThresholdProfile":"...",
"systemResourceThresholdProfile":"...",
"hostGroupIDs":["...", ...],
"hostGroupNames":["...", ...],
"lunOwnerIDs":["...", ...],
"lunOwnerNames":["...", ...],
"assignmentSchedule":"...",
"datastoreType":"...",
"datastoreCapacity":"...",
"datastoreCapacityUsed":"...",
"datastoreUsageRate":"...",
"datastoreFreeSpace":"...",
"portType":"...",
"attribute":"...",
"speedInGB":"...",
"loopId":"...",
"topology":"...",
"lunSecurity":"...",
"wwn":"...",
"negotiatedPortSpeed":"...",
"portMode":"...",
"nvmSubsystemID":"...",
"nvmSubsystemNQN":"...",
"nvmSubsystemNickname":"...",
"nvmNamespaceSecurity":"...",
"nvmNamespaceID":"...",
"nvmNamespaceNickname":"...",
"nvmHostNQNs":["...", ...],
"nvmHostNicknames":["...", ...],
"portId":"...",
"portStatus":"...",
"protocol":"...",
"wwnIscsiName":"...",
"storageNode":"...",
"driveId":"...",
"vssbDriveStatus":"...",
"driveWwid":"...",
"driveCapacity":"...",
"storageNodes":["...", ...],
"volumeId":"...",
"volumeTotalCapacity":"...",
"volumeUsedCapacity":"...",
"nickname":"...",
"volumeNumber":"...",
"computeNodes":["...", ...],
"volumeStatus":"...",
"storageId":"...",
"storageServiceId":"...",
"storageInternalId":"...",
"storageTotalCapacity":"...",
"storageFreeCapacity":"...",
"storageClusterStatus":"..."
},
"vsmInformation":{
"volumeName":"...",
"storage":"..."
},
"pairInformation":{
"copyType":"...",
"physicalVolumeName":"...",
"physicalStorage":"...",
"virtualVolumeName":"...",
"virtualStorage":"..."
},
"poolInformation":{
"name":"...",
"status":"...",
"capacity":"...",
"poolName":"...",
"poolType":"...",
"poolID":"...",
"tierNumber":"...",
"driveType":"...",
"driveSpeed":"...",
"raidLevel":"...",
"chipType":"...",
"userResourceThresholdProfile":"...",
"systemResourceThresholdProfile":"...",
"touchedCapacity":"...",
"usageRate":"...",
"physicalCapacity":"...",
"physicalCapacityUsed":"...",
"physicalCapacityUsageRate":"...",
"dataSaving":"...",
"userDataCapacity":"...",
"savingRatio":"...",
"savingCapacity":"...",
"dkcSavingRatio":"...",
"dkcCompressionRatio":"...",
"dkcDedupRatio":"...",
"dkcSavingCapacity":"...",
"dkcCompressionCapacity":"...",
"dkcDedupCapacity":"...",
"dkcReclaimCapacity":"...",
"dkcSystemCapacity":"...",
"dkcPreProcCapacity":"...",
"fmcSavingCapacity":"...",
"fmcCompressionRatio":"...",
"fmcCompressionCapacity":"...",
"fmcReclaimCapacity":"...",
"fmcPhysicalCapacity":"...",
"fmcPhysicalCapacityUsed":"...",
"fmcLogicalCapacity":"...",
"fmcLogicalCapacityUsed":"...",
"autoExpansion":"...",
"totalEfficiencyRatio":"...",
"dataReductionRatio":"...",
"softwareSavingRatio":"...",
"acSavingRatio":"...",
"snapshotEfficiencyRatio":"...",
"provisioningEfficiency":"...",
"calculationTimeRange":{
"calculationStartTime":,
"calculationEndTime":
}
},
"pgInformation":{
"name":"...",
"status":"...",
"capacity":"...",
"driveType":"...",
"driveSpeed":"...",
"raidLevel":"...",
"chipType":"...",
"userResourceThresholdProfile":"...",
"systemResourceThresholdProfile":"..."
},
"tierInformation":[{
"instanceID":"...",
"tierNumber":"...",
"driveType":"...",
"driveSpeed":"...",
"raidLevel":"...",
"chipType":"..."
},
:
],
"ipNetworkInformation":[{
"instanceID":"...",
"adapter":"...",
"mac":"...",
"ipAddress":"..."
},
:
],
"fcNetworkInformation":[{
"instanceID":"...",
"adapter":"...",
"wwn":"..."
},
:
],
"diskInformation":[{
"instanceID":"...",
"name":"...",
"capacity":"...",
"adapterNumber":"...",
"busID":"...",
"targetID":"...",
"lunID":"..."
},
:
],
"driveCapacity":[{
"instanceID":"...",
"category":"...",
"driveName":"...",
"totalCapacity":"...",
"fileSystem":"...",
"driveType":"..."
},
:
],
"virtualDisk":[{
"instanceID":"...",
"diskName":"...",
"totalCapacity":"..."
},
:
]
}
vsmInformation E2EVSMInformation VSM information. This item is set only if the resource is a volume.
pairInformation E2EPairInformation Pair information. This item is set only if the resource is a volume.
poolInformation E2EPoolInformation Pool information. This item is set only if the resource is a volume.
pgInformation E2EPGInformation Parity group information. This item is set only if the resource is a volume.
tierInformation E2ETierInformation[] Pool tier information. This item is set only if the resource is a volume.
ipNetworkInformation E2EIPNerwork[] IP network information. This item is set only if the resource is a
hyoervisor or host.
fcNetworkInformation E2EFCNetwork[] FC network information. This item is set only if the resource is a
hypervisor or host.
diskInformation E2EDisk[] Disk information. This item is set only if the resource is a hypervisor or
host.
driveCapacity E2EDriveCapacity[] File system information. This item is set only if the resource is a
hypervisor or host.
virtualDisk E2EVirtualDisk[] Information about the virtual disks that a virtual machine has. This item is
set only if the resource is a virtual machine.
(For details about the valid values, see the table NodeStatusType in
List of enumerators.)
Normal
Warning
Critical
Unknown
(For details about the valid values, see the table PowerStatusType in
List of enumerators.)
(For details about the valid values, see the table ArgusNodeType in
List of enumerators.)
storageTotalEfficiencyRatio float The ratio of the total saving effect achieved by accelerated
compression, capacity saving (compression and deduplication),
snapshot, and Dynamic Provisioning of the storage.
storageDataReductionRatio float The data reduction ratio before and after accelerated compression
and capacity saving (compression and deduplication) of the storage.
storageSoftwareSavingRatio float The capacity reduction ratio before and after capacity saving.
storageAcSavingRatio float The data reduction efficiency ratio of the total storage by accelerated
compression.
storageProvisioningEfficiency float The efficiency ratio achieved by Dynamic Provisioning of the storage.
storageCalculationTimeRange CalculationTimeRange The start and end times for the calculation. The time based on the
system date and time (date, time, and timezone) of the storage
system is displayed.
(For details about the valid values, see the table E2EPoolType in List
of enumerators.)
poolSavingRatio float The storage capacity savings ratio with the controller-based capacity
saving and accelerated compression functions in a pool.
poolSavingCapacity float The storage capacity savings with the controller-based capacity
saving and accelerated compression functions in a pool.
dkcSavingRatio float The saving ratio with the capacity saving function (deduplication and
compression) in a pool.
dkcCompressionRatio float The saving ratio with the capacity saving function (compression) in a
pool.
dkcDedupRatio float The saving ratio with the capacity saving function (deduplication) in
a pool.
dkcSavingCapacity float The saved capacity with the capacity saving function (deduplication
and compression) in a pool.
dkcCompressionCapacity float The saved capacity with the capacity saving function (compression)
in a pool.
dkcDedupCapacity float The saved capacity with the capacity saving function (deduplication)
in a pool.
Attribute Type Description
dkcReclaimCapacity float The reclaimed capacity with the capacity saving function.
dkcSystemCapacity float The system data capacity (=Meta data capacity + Garbage data
capacity) saved with the capacity saving function.
dkcPreProcCapacity float The preprocessed data capacity with the capacity saving function.
fmcSavingCapacity float The saved capacity with the accelerated compression function.
fmcCompressionRatio float The saved capacity ratio with the accelerated compression function.
fmcReclaimCapacity float The reclaimed capacity with the accelerated compression function.
fmcPhysicalCapacity float The total physical capacity with the accelerated compression
function.
fmcPhysicalCapacityUsed float The used physical capacity with the accelerated compression
function.
fmcLogicalCapacity float The total capacity with the accelerated compression function.
fmcLogicalCapacityUsed float The total used capacity with the accelerated compression function.
poolTotalEfficiencyRatio float The ratio of the total saving effect achieved by accelerated
compression, capacity saving (compression and deduplication),
snapshot, and Dynamic Provisioning for the pool.
poolDataReductionRatio float The data reduction ratio of the pool before and after accelerated
compression and capacity saving (compression and deduplication).
poolSoftwareSavingRatio float The capacity reduction ratio in the pool before and after capacity
saving.
poolAcSavingRatio float The reduction efficiency ratio of the pool using accelerated
compression.
poolCalculationTimeRange CalculationTimeRange The start and end times for the calculation. The time based on the
system date and time (date, time, and timezone) of the storage
system is displayed.
driveType enum Type of disk drive such as SAS, SATA and SSD.
(For details about the valid values, see the table E2EDriveType in List
of enumerators.)
displayDriveType string Type of disk drive such as SAS, SATA and SSD.
driveStatus string Summary drive status of all data drives that compose the parity
group.
usedSpareDriveCount integer The number of spare drives among the data drives that compose the
parity group.
usedEnduranceIndicator integer The greatest SSD endurance indicator (%) among all of the data
drives that compose the parity group.
batteryLifeIndicator integer The greatest FMD battery life indicator (%) among all of the batteries
for the data drives that compose the parity group.
(For details about the valid values, see the table E2EChipType in List
of enumerators.)
hostGroupNames string[] Name of the host group that a volume belongs to.
lunOwnerNames string[] Name of the LUN Owner that a volume is associated with.
nvmNamespaceSecurity string Setting whether to use the namespace security. If enabled, "Enabled"
is set. If disabled, "Disabled" is set.
(For details about the valid values, see the table NodeStatusType in
List of enumerators.)
Normal
Warning
Critical
Unknown
(For details about the valid values, see the table E2EPoolType in List
of enumerators.)
driveType enum Type of disk drive such as SAS, SATA and SSD.
(For details about the valid values, see the table E2EDriveType in List
of enumerators.)
Attribute Type Description
(For details about the valid values, see the table E2EChipType in List
of enumerators.)
savingRatio float The storage capacity savings ratio with the controller-based capacity
saving and accelerated compression in a pool.
savingCapacity float The storage capacity savings with the controller-based capacity
saving and accelerated compression in a pool.
dkcSavingRatio float The saving ratio with the capacity saving feature (deduplication and
compression) in a pool.
dkcCompressionRatio float The saving ratio with the capacity saving feature (compression) in a
pool.
dkcDedupRatio float The saving ratio with the capacity saving feature (deduplication) in a
pool.
Attribute Type Description
dkcSavingCapacity float The saved capacity with the capacity saving feature (deduplication
and compression) in a pool.
dkcCompressionCapacity float The saved capacity with the capacity saving feature (compression)
in a pool.
dkcDedupCapacity float The saved capacity with the capacity saving feature (deduplication)
in a pool.
dkcReclaimCapacity float The reclaimed capacity with the capacity saving feature.
dkcSystemCapacity float The system data capacity (metadata capacity + garbage data
capacity) saved with the capacity saving feature.
dkcPreProcCapacity float The preprocessed data capacity with the capacity saving feature.
totalEfficiencyRatio float The ratio of the total saving effect achieved by accelerated
compression, capacity saving (compression and deduplication),
snapshot, and Dynamic Provisioning of the pool.
dataReductionRatio float The data reduction ratio of the pool before and after accelerated
compression and capacity saving (compression and deduplication).
softwareSavingRatio float The capacity reduction ratio of the pool before and after capacity
saving.
Attribute Type Description
acSavingRatio float The reduction efficiency ratio of the pool using accelerated
compression.
snapshotEfficiencyRatio float The efficiency ratio achieved by snapshot for the pool.
provisioningEfficiency float The efficiency ratio achieved by Dynamic Provisioning for the pool.
calculationTimeRange CalculationTimeRange The start and end times for the calculation. The time based on the
system date and time (date, time, and timezone) of the storage
system is displayed.
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
(For details about the valid values, see the table E2EDriveType in List of
enumerators.)
(For details about the valid values, see the table E2EChipType in List of
enumerators.)
adapterNumber int Adapter number. This item is set only if ScsiDiskDrive is set.
busID int Bus ID. This item is set only if ScsiDiskDrive is set.
lunID int LUN ID. This item is set only if ScsiDiskDrive is set.
(For details about the valid values, see the table E2ENodeDriveType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/E2EView/actions/getNodeDetail/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getNodeDetail",
"href": "[Link]
"method": "POST",
"type": "application/json",
"parameters":[{
"targetNodeID":"h#ABC_172.17.17.115_host-195",
"targetNodeType":"HYPERVISOR"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "9432e298-818c-40cd-bbb3-7be5f3cece91",
"created" : "2016-07-20T[Link].945+09:00",
"updated" : "2016-07-20T[Link].769+09:00",
"completed" : "2016-07-20T[Link].769+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"nodeInformation" : {
"name" : "[Link]",
"status" : "Unknown",
"vendor" : "VMware, Inc.",
"operatingSystem" : {
"osName" : "VMware ESXi",
"osVersion" : "5.5.0"
},
"processor" : {
"cpuName" : "Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz",
"clockSpeed" : "2600",
"processors" : "8"
},
"memory" : 16776692,
"hypervisorType" : "SERVER_ESX",
"model" : "VMware Virtual Platform",
"systemResourceThresholdProfile" : [ "Default Profile for Hypervisor (VMware)" ]
},
"ipNetworkInformation" : [ {
"adapter" : "vmnic0 : e1000"
} ],
"diskInformation" : [ {
"name" : "[Link][Link]T0:L0",
"capacity" : 167772160
} ],
"driveCapacity" : [ {
"driveName" : "datastore1 : ds:///vmfs/volumes/54f014c4-a73a50dd-ed19-005056a34b21/",
"totalCapacity" : 159907840,
"fileSystem" : "VMFS"
} ]
} ]
}
Related reference
List of enumerators
The following operation is the initial step to check if a resource can obtain topology data for display in the E2E view.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/E2EView/actions/checkBasePointParam
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2ECheckParam
{
"basePointNodeID":["...", ...]
}
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/E2EView/actions/checkBasePointParam
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "checkBasePointParam",
"href" : "[Link]
oke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"basePointNodeID" : [ ],
"basePointTableType" : "NODE"
} ]
}
You can check if a resource can obtain topology data for display in the E2E view.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/E2EView/actions/checkBasePointParam/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2ECheckParam
{
"basePointNodeID":["...", ...]
}
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
Response body
The structure of the response body and the object attributes is as follows:
E2EViewParam
{
"basePointNodeID":["...", ...],
"basePointNodeType":"..."
}
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
Attribute Type Description
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/E2EView/actions/checkBasePointParam/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "checkBasePointParam",
"href": "[Link]
ke",
"method": "POST",
"type": "application/json",
"parameters":[{
"basePointNodeID":["h#ABC_172.17.17.115_host-195"],
"basePointTableType":"NODE"
} ]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "acceeea6-48aa-480d-b4fa-ad4726e00218",
"created" : "2016-07-20T[Link].272+09:00",
"updated" : "2016-07-20T[Link].273+09:00",
"completed" : "2016-07-20T[Link].273+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"basePointNodeID" : [ "h#ABC_172.17.17.115_host-195" ],
"basePointNodeType" : "HYPERVISOR"
} ]
}
Related reference
List of enumerators
The following operation is the initial step to obtain a list of resources related to a specific resource displayed in the Analyze
Bottleneck view.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/E2EView/actions/getRelatedNodeList
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2EViewParam
{
"basePointNodeID":["...", ...],
"basePointNodeType":"..."
}
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/E2EView/actions/getRelatedNodeList
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getRelatedNodeList",
"href" : "[Link]
ke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"basePointNodeID" : [ ],
"basePointNodeType" : "HYPERVISOR"
} ]
}
Related reference
List of enumerators
You can obtain a list of resources related to a specific resource displayed in the Analyze Bottleneck view.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/E2EView/actions/getRelatedNodeList/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2EViewParam
{
"basePointNodeID":["...", ...],
"basePointNodeType":"..."
}
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of Collections objects. For details about Collections, see the table below.
result anyType[]
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
data anyType[] Collections resource list containing the following Collections resources that
have the following structure:
"<E2ENodeType>": Collections
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
E2ETopologyNode
{
"instanceID":"...",
"name":"...",
"status":"...",
"relatedNodeList":[{
"instanceID":"...",
"type":"...",
"componentType":"...",
"profileResourceType":"..."
},
:
],
"shareRate":"...",
"profileResourceType":"...",
"driveStatus":"..."
}
(For details about the valid values, see the table E2ENodeStatus in
List of enumerators.)
shareRate int Percentage of related base point resources out of all the base point
resources. (Note: The Share Rate value is not available when you set
a Hypervisor or Storage System as the base point of analysis.)
driveStatus string Aggregated drive status of all data drives that configure the parity
group
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/E2EView/actions/getRelatedNodeList/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getRelatedNodeList",
"href": "[Link]
e",
"method": "POST",
"type": "application/json",
"parameters":[{
"basePointNodeID":["h#ABC_172.17.17.115_host-195"],
"basePointNodeType":"HYPERVISOR"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "ef8ef038-cca2-41f1-9a8b-d5cadedb8e37",
"created" : "2016-07-20T[Link].740+09:00",
"updated" : "2016-07-20T[Link].740+09:00",
"completed" : "2016-07-20T[Link].740+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"DISK" : [ {
"instanceID" : "disk#ABC_172.17.17.115_host-195^mpx.vmhba1^C0^T0^L0",
"name" : "[Link][Link]T0:L0",
"status" : "UNKNOWN",
"relatedNodeList" : [ {
"instanceID" : "vdisk#ABC_172.17.17.115_vm-198^2000",
"type" : "VIRTUAL_MACHINE",
"componentType" : "VIRTUAL_DISK",
"profileResourceType" : "ESX_VM"
}, {
...........
} ],
"shareRate" : 100,
"profileResourceType" : "ESX"
} ],
"VIRTUAL_MACHINE" : [ {
"instanceID" : "vm#ABC_172.17.17.115_vm-350",
"name" : "CT5_DT005_e",
"status" : "UNKNOWN",
"relatedNodeList" : [ {
"instanceID" : "cpu#ABC_172.17.17.115_host-195^2",
"type" : "CPU",
"componentType" : "CPU",
"profileResourceType" : "ESX"
}, {
..........
} ],
"shareRate" : 100,
"profileResourceType" : "ESX_VM"
}, {
..........
} ]
}
Related reference
List of enumerators
Preparing to obtain a query parameters used to display resources in the E2E view
The following operation is the initial step to obtain information about a specific resource, such as the resource name.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/E2EView/actions/getNodeName
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2ENodeDetailParam
{
"targetNodeID":"...",
"targetNodeType":"..."
}
targetNodeType enum Type of the resources for which details are to be obtained
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/E2EView/actions/getNodeName
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getNodeName",
"href" : "[Link]
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"targetNodeID" : "0",
"targetNodeType" : "VIRTUAL_MACHINE"
} ]
}
Related reference
List of enumerators
You can obtain information about a specific resource displayed in the E2E view, such as the resource name.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/E2EView/actions/getNodeName/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2ENodeDetailParam
{
"targetNodeID":"...",
"targetNodeType":"..."
}
targetNodeType enum Type of the resources for which details are to be obtained
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
E2ENodeName
{
"nodeName":"...",
"nodeType":"...",
"componentID":"...",
"componentName":"...",
"componentType":"..."
}
nodeName string Name of the resources that are managed by Ops Center Analyzer
nodeType enum Type of the resources that are managed by Ops Center Analyzer
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Unknown
Server
Storage
NetworkDevice
Datastore
(For details about the valid values, see the table ComponentType in List of
enumerators.)
CPU
MEMORY
LAN_PORT
FC_HBA_PORT
DISK_DRIVE
FILE_SYSTEM
STORAGE_CONTROLLER
Attribute Type Description
STORAGE_FC_PORT
STORAGE_POOL
STORAGE_VOLUME
STORAGE_CACHE
VIRTUAL_MACHINE
HYPERVISOR_CLUSTER
STORAGE_MPB
STORAGE_DP_POOL
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/E2EView/actions/getNodeName/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getNodeName",
"href": "[Link]
"method": "POST",
"type": "application/json",
"parameters":[{
"targetNodeID":"h#ABC_172.17.17.115_host-195",
"targetNodeType":"HYPERVISOR"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "5a485cb6-19b8-42e8-9064-417026f98a83",
"created" : "2016-07-20T[Link].620+09:00",
"updated" : "2016-07-20T[Link].759+09:00",
"completed" : "2016-07-20T[Link].759+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"instanceID" : "h#ABC_172.17.17.115_host-195",
"nodeName" : "[Link]",
"nodeType" : "Server"
} ]
}
Related reference
List of enumerators
The following operation is the initial step to obtain information about a specific resource, such as the resource name.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/E2EView/actions/getNodeList
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetNodeListParam
{
"resourceIDs":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/E2EView/actions/getNodeList HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Tue, 31 Jan 2017 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO d799177dd86fc4661512e0ace8c07e52248d76b2_ZAlDR1YdfRBWBxNW_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getNodeList",
"href" : "[Link]
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"resourceIDs" : [ "ResourceID 0", "ResourceID 1" ]
} ]
}
You can obtain information about a specific resource, such as the resource name.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/E2EView/actions/getNodeList/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetNodeListParam
{
"resourceIDs":["...", ...]
}
Response body
The structure of the response body and the object attributes is as follows:
E2ENodeList
{
"resources":[{
"nodeName":"...",
"nodeType":"...",
"componentID":"...",
"componentName":"...",
"componentType":"..."
},
:
]
}
nodeName string Name of the resources that are managed by Ops Center Analyzer
nodeType enum Type of the resources that are managed by Ops Center Analyzer
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Unknown
Server
Storage
NetworkDevice
Datastore
(For details about the valid values, see the table ComponentType in List of
enumerators.)
CPU
MEMORY
LAN_PORT
FC_HBA_PORT
DISK_DRIVE
FILE_SYSTEM
STORAGE_CONTROLLER
STORAGE_FC_PORT
STORAGE_POOL
STORAGE_VOLUME
STORAGE_CACHE
VIRTUAL_MACHINE
HYPERVISOR_CLUSTER
STORAGE_MPB
STORAGE_DP_POOL
Status codes
200 OK Success.
Example code
[Request Header]
POST Analytics/v1/services/E2EView/actions/getNodeList/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "getNodeList",
"href" : "[Link]
"method" : "POST",
"type" : "application/json",
"parameters": [
{
"resourceIDs": [
"raidLdev#51547-00^00^00", "raidLdev#410438-00^00^00", "raidLdev#51306-00^00^00"
]
}
]
}
[Response Header]
HTTP/1.1 200 OK
Cache-Control: no-cache
Connection: Keep-Alive
Content-Type: application/json
Date: Tue, 24 Jan 2017 [Link] GMT
Server: Cosminexus HTTP Server
Transfer-Encoding: chunked
WWW-Authenticate: HSSO c450462eec01893d4c1ebcba7e7876538bd94_VwBvNGpyDgxyCUY3eXZdCQ==_V0810
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection : 1; mode=block
[Response Body]
{
"instanceID": "9a277dd5-5016-4a03-ba87-ac6ccc9de566",
"created": "2017-01-24T[Link].820+09:00",
"updated": "2017-01-24T[Link].820+09:00",
"completed": "2017-01-24T[Link].820+09:00",
"state": "success",
"affectedResource": [],
"result": [
{
"resources": [
{
"instanceID": "raidStorage#410438",
"nodeName": "VSP G400/G600 (410438)",
"nodeType": "Storage",
"componentID": "raidLdev#410438-00^00^00",
"componentName": "[Link]"
},
{
"instanceID": "raidStorage#51306",
"nodeName": "XP7 (51306)",
"nodeType": "Storage",
"componentID": "raidLdev#51306-00^00^00",
"componentName": "[Link]"
},
{
"instanceID": "raidStorage#51547",
"nodeName": "VSP G1500 (51547)",
"nodeType": "Storage",
"componentID": "raidLdev#51547-00^00^00",
"componentName": "[Link]"
}
]
}
]
}
Related reference
List of enumerators
Setting up a mail server
You can update mail server settings and send test emails.
You can display a list of SMTP server settings, such as the host name and port number.
Execution permission
Admin
Request line
GET baseURL/v1/objects/EmailServerSettings
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of EmailSetting objects. For details about EmailSetting, see the table
data anyType[]
below.
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
EmailSetting
{
"instanceID":"...",
"hostname":"...",
"authenticationEnabled":"...",
"userId":"...",
"senderAddress":"...",
"secureConnection":"...",
"portNumber":"..."
}
authenticationEnabled boolean Whether or not to enable authentication of the user who sends emails. If
enabled, "true" is set. If disabled, "false" is set.
userId string User ID used for authentication of the user who sends emails. This item is set
only if authenticationEnabled is "true".
(For details about the valid values, see the table SecureConnectionType in List
of enumerators.)
TLS
Plain
STARTTLS
portNumber int Port number used for connection to the SMTP server
Status codes
200 OK Success.
Status code Reason phrase Description
Example code
[Request Header]
GET /Analytics/v1/objects/EmailServerSettings
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "mailServerSetting#0",
"hostname" : "smtp server",
"authenticationEnabled" : false,
"secureConnection" : "Plain",
"portNumber" : 25
} ],
"count" : 1
}
Related reference
List of enumerators
You can update information about the configuration of a specific email server, such as the host name and port number.
Execution permission
Admin
Request line
PUT baseURL/v1/objects/EmailServerSettings/{id}
Request body
The structure of the request body and the object attributes are as follows:
EmailSetting
{
"instanceID":"...",
"hostname":"...",
"authenticationEnabled":"...",
"userId":"...",
"updatePassword":"...",
"password":"...",
"senderAddress":"...",
"secureConnection":"...",
"portNumber":"..."
}
authenticationEnabled boolean Whether or not to enable authentication of the user who sends emails. If
enabled, "true" is set. If disabled, "false" is set.
userId string User ID used for authentication of the user who sends emails. This item is set
only if authenticationEnabled is "true".
updatePassword boolean Whether or not to change the password that is used to authenticate the email
sender. Specify this item if the password needs to be changed when the mail
server settings are changed. To change the password, specify "true". To not
change the password, specify "false".
password string Password used for authentication of the user who sends emails. Specify a
string encoded in Base64.
(For details about the valid values, see the table SecureConnectionType in List
of enumerators.)
TLS
Plain
STARTTLS
portNumber int Port number used for connection to the SMTP server
Response body
The structure of the response body and the object attributes is as follows:
EmailSetting
{
"instanceID":"...",
"hostname":"...",
"authenticationEnabled":"...",
"userId":"...",
"senderAddress":"...",
"secureConnection":"...",
"portNumber":"..."
}
authenticationEnabled boolean Whether or not to enable authentication of the user who sends emails. If
enabled, "true" is set. If disabled, "false" is set.
userId string User ID used for authentication of the user who sends emails. This item is set
only if authenticationEnabled is "true".
(For details about the valid values, see the table SecureConnectionType in List
of enumerators.)
TLS
Plain
STARTTLS
portNumber int Port number used for connection to the SMTP server
Status codes
200 OK Success.
Example code
[Request Header]
PUT /Analytics/v1/objects/EmailServerSettings/mailServerSetting%230
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"instanceID":1234568790,
"hostname":"[Link]",
"authenticationEnabled":true,
"userId":"user1",
"updatePassword":true,
"password":"a2FzaGltYTE=",
"senderAddress":"user@[Link]",
"secureConnection":"Plain",
"portNumber":25
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "mailServerSetting#0",
"hostname" : "[Link]",
"authenticationEnabled" : false,
"userId" : "user1",
"senderAddress" : "user@[Link]",
"secureConnection" : "Plain",
"portNumber" : 25
}
Related reference
List of enumerators
You can display a list of operations related to email server settings, such as the operation to obtain a list of email server settings.
Execution permission
Admin
Request line
GET baseURL/v1/services/EmailServerSettings/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/EmailServerSettings/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "sendTestMail",
"href" : "[Link]
ail/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
Execution permission
Admin
Request line
GET baseURL/v1/services/EmailServerSettings/actions/sendTestMail
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
TestMail
{
"destinationAddresses":["...", ...],
"emailSetting":{
"instanceID":"...",
"hostname":"...",
"authenticationEnabled":"...",
"userId":"...",
"senderAddress":"...",
"secureConnection":"...",
"portNumber":"..."
}
}
destinationAddresses string[] Email address specified as the destination of the test email
authenticationEnabled boolean Whether or not to enable authentication of the user who sends emails. If
enabled, "true" is set. If disabled, "false" is set.
userId string User ID used for authentication of the user who sends emails. This item is set
only if authenticationEnabled is "true".
(For details about the valid values, see the table SecureConnectionType in List
of enumerators.)
TLS
Attribute Type Description
Plain
STARTTLS
portNumber int Port number used for connection to the SMTP server
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/EmailServerSettings/actions/sendTestMail
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "sendTestMail",
"href" : "[Link]
l/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"emailSetting" : {
"instanceID" : "mailServerSetting#0",
"hostname" : "[Link]",
"authenticationEnabled" : false,
"userId" : "user1",
"senderAddress" : "user@[Link]",
"secureConnection" : "Plain",
"portNumber" : 25
}
} ]
}
Related reference
List of enumerators
You can send a test email from the mail server by specifying information such as the host name and delivery address.
Execution permission
Admin
Request line
POST baseURL/v1/services/EmailServerSettings/actions/sendTestMail/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
TestMail
{
"destinationAddresses":["...", ...],
"emailSetting":{
"instanceID":"...",
"hostname":"...",
"authenticationEnabled":"...",
"userId":"...",
"updatePassword":"...",
"password":"...",
"senderAddress":"...",
"secureConnection":"...",
"portNumber":"..."
}
}
destinationAddresses string[] Email address specified as the destination of the test email
authenticationEnabled boolean Whether or not to enable authentication of the user who sends emails. If
enabled, "true" is set. If disabled, "false" is set.
userId string User ID used for authentication of the user who sends emails. This item is set
only if authenticationEnabled is "true".
updatePassword boolean Whether or not to change the password that is used to authenticate the email
sender. Specify this item if the password needs to be changed when the mail
server settings are changed. To change the password, specify "true". To not
change the password, specify "false".
password string Password used for authentication of the user who sends emails. Specify a
string encoded in Base64.
(For details about the valid values, see the table SecureConnectionType in List
of enumerators.)
TLS
Plain
STARTTLS
portNumber int Port number used for connection to the SMTP server
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/EmailServerSettings/actions/sendTestMail/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "sendTestMail",
"href": "[Link]
l/invoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"emailSetting": {
"instanceID": "mailServerSetting#0",
"hostname": "[Link]",
"authenticationEnabled": true,
"userId": "user1",
"updatePassword": true,
"password": "a2FzaGltYTE=",
"senderAddress": "user@[Link]",
"secureConnection": "Plain",
"portNumber": 25
},
"destinationAddresses": [
"user2@[Link]",
"user3@[Link]"
]
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO f0f3ee9e20f6ce82bf67a24e862b7b86e7ef8bb0_Y2UOI2pkMXQ=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID": "33f2e181-4f13-408a-91c1-d13c858519d9",
"created": "2016-08-22T[Link].097+09:00",
"updated": "2016-08-22T[Link].097+09:00",
"completed": "2016-08-22T[Link].097+09:00",
"state": "success",
"affectedResource": [
],
"result": [
]
}
Related reference
List of enumerators
You can obtain a list of events and event-related information, such as messages, dates, and times.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/Events?page={page}&pageSize={size}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Event objects. For details about Event, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Event
{
"instanceID":"...",
"level":"...",
"message":"...",
"dateTime":"...",
"category":"...",
"nodeId":"...",
"deviceName":"...",
"deviceType":"...",
"componentId":"...",
"componentName":"...",
"componentType":"...",
"targetMetric":"...",
"targetMetricName":"...",
"profileName":"...",
"planName":"...",
"thresholdValue":"...",
"thresholdUnit":"..."
}
(For details about the valid values, see the table EventSeverityType in List of
enumerators.)
INFO
WARNING
CRITICAL
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
PERFORMANCE
EVENT
SETTING
nodeId string ID of the device for which the event was issued
deviceName string Name of the device for which the event was issued
deviceType enum Type of the device for which the event was issued
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Unknown
Server
Storage
NetworkDevice
Datastore
componentId string ID of the component for which the event was issued
componentName string Name of the component for which the event was issued
componentType enum Type of the component for which the event was issued
Attribute Type Description
(For details about the valid values, see the table ComponentType in List of
enumerators.)
targetMetric enum ID of the metric for which the event was issued. This item is displayed only if
the category is "Performance".
(For details about the valid values, see the table MetricType in List of
enumerators.)
targetMetricName string Name of the metric for which the event was issued. This item is displayed only
if the category is "Performance".
profileName string Name of the threshold profile for which the event was issued. This item is
displayed only if the category is "Performance".
planName string Name of the plan set for the threshold profile for which the event was issued.
This item is displayed only if the category is "Performance".
thresholdValue string Threshold for which the event was issued. This item is displayed only if the
category is "Performance".
thresholdUnit string Unit of the threshold for which the event was issued. This item is displayed only
if the category is "Performance".
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/Events
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "Setting##1468980297687##0##INFO##null####null##",
"status" : "NOTACK",
"level" : "INFO",
"message" : "The service started. (host:localhost)",
"dateTime" : "2016-07-20T[Link].687+09:00",
"category" : "SETTING",
"thresholdValue" : 0.0
}, {
"instanceID" : "Setting##1468971056202##0##INFO##null####null##",
"status" : "NOTACK",
"level" : "INFO",
"message" : "The service started. (host:localhost)",
"dateTime" : "2016-07-20T[Link].202+09:00",
"category" : "SETTING",
"thresholdValue" : 0.0
} ],
"count" : 2
}
Related reference
List of enumerators
You can obtain information about a specific event, such as the message, date, and time.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/Events/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Event
{
"instanceID":"...",
"level":"...",
"message":"...",
"dateTime":"...",
"category":"...",
"nodeId":"...",
"deviceName":"...",
"deviceType":"...",
"componentId":"...",
"componentName":"...",
"componentType":"...",
"targetMetric":"...",
"targetMetricName":"...",
"profileName":"...",
"planName":"...",
"thresholdValue":"...",
"thresholdUnit":"..."
}
(For details about the valid values, see the table EventSeverityType in List of
enumerators.)
INFO
WARNING
CRITICAL
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
PERFORMANCE
EVENT
SETTING
nodeId string ID of the device for which the event was issued
deviceName string Name of the device for which the event was issued
deviceType enum Type of the device for which the event was issued
(For details about the valid values, see the table NodeDisplayType in List of
enumerators.)
Unknown
Server
Storage
NetworkDevice
Datastore
Attribute Type Description
componentId string ID of the component for which the event was issued
componentName string Name of the component for which the event was issued
componentType enum Type of the component for which the event was issued
(For details about the valid values, see the table ComponentType in List of
enumerators.)
targetMetric enum ID of the metric for which the event was issued. This item is displayed only if
the category is "Performance".
(For details about the valid values, see the table MetricType in List of
enumerators.)
targetMetricName string Name of the metric for which the event was issued. This item is displayed only
if the category is "Performance".
profileName string Name of the threshold profile for which the event was issued. This item is
displayed only if the category is "Performance".
planName string Name of the plan set for the threshold profile for which the event was issued.
This item is displayed only if the category is "Performance".
thresholdValue string Threshold for which the event was issued. This item is displayed only if the
category is "Performance".
thresholdUnit string Unit of the threshold for which the event was issued. This item is displayed only
if the category is "Performance".
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/Events/Setting%23%231491153559830%23%230%23%23INFO%23%23null%23%23%23%
23null%23%23
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "Setting##1468980297687##0##INFO##null####null##",
"status" : "NOTACK",
"level" : "INFO",
"message" : "The service started. (host:localhost)",
"dateTime" : "2016-07-20T[Link].687+09:00",
"category" : "SETTING",
"thresholdValue" : 0.0
}
Related reference
List of enumerators
You can obtain a list of operations related to events, such as the operation to obtain the number of events.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/Events/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/Events/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getEventCount",
"href" : "[Link]
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to obtain the number of events within a specific time period.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/Events/actions/getEventCount
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetEventCountParam
{
"categories":["...", ...],
"countFrom":"...",
"countTo":"...",
"interval":"..."
}
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
Attribute Type Description
PERFORMANCE
EVENT
SETTING
countFrom dateTime Start time of the period for which the events is to be obtained
countTo dateTime End time of the period for which the events is to be obtained
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/Events/actions/getEventCount
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getEventCount",
"href" : "[Link]
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"categories" : [ "CHANGE" ],
"countFrom" : "2016-07-19T[Link].476+09:00",
"countTo" : "2016-07-20T[Link].476+09:00",
"interval" : 3600000
} ]
}
Related reference
List of enumerators
You can obtain the number of events that occurred within a specific time period.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/Events/actions/getEventCount/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetEventCountParam
{
"categories":["...", ...],
"countFrom":"...",
"countTo":"...",
"interval":"..."
}
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
PERFORMANCE
EVENT
SETTING
countFrom dateTime Start time of the period for which the events is to be obtained
countTo dateTime End time of the period for which the events is to be obtained
Response body
The structure of the response body and the object attributes is as follows:
EventCount
{
"periodFrom":"...",
"info":"...",
"warning":"...",
"critical":"...",
"total":"..."
}
info long Number of information events that occurred during the aggregation interval
warning long Number of warning events that occurred during the aggregation interval
critical long Number of critical events that occurred during the aggregation interval
total long Total number of events that occurred during the aggregation interval
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/Events/actions/getEventCount/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getEventCount",
"href": "[Link]
"method": "POST",
"type": "application/json",
"parameters":[{
"countFrom":"2016-07-19T[Link].476+09:00",
"countTo":"2016-07-20T[Link].476+09:00",
"interval":"3600000"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "79e6e2e0-a800-4b22-bb5d-25424ca65a51",
"created" : "2016-07-20T[Link].966+09:00",
"updated" : "2016-07-20T[Link].047+09:00",
"completed" : "2016-07-20T[Link].047+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"periodFrom" : "2016-07-19T[Link].476+09:00",
"info" : 0,
"warning" : 0,
"critical" : 0,
"total" : 0
}, {
........
}, {
"periodFrom" : "2016-07-20T[Link].476+09:00",
"info" : 2,
"warning" : 0,
"critical" : 0,
"total" : 2
} ]
}
Related reference
List of enumerators
You can obtain a list of grade information, such as grade names and grade priorities.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/Grades
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
Collections (Type: Collections)
A list of Grade objects. For details about Grade, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Grade
{
"gradeKey":"...",
"name":"...",
"displayOrder":"..."
}
Status codes
200 OK Success.
Status code Reason phrase Description
Example code
[Request Header]
GET /Analytics/v1/objects/Grades
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "grade#Platinum",
"gradeKey" : "10",
"name" : "Platinum",
"displayOrder" : 10
}, {
"instanceID" : "grade#Bronze",
"gradeKey" : "40",
"name" : "Bronze",
"displayOrder" : 40
}, {
"instanceID" : "grade#Gold",
"gradeKey" : "20",
"name" : "Gold",
"displayOrder" : 20
}, {
"instanceID" : "grade#Silver",
"gradeKey" : "30",
"name" : "Silver",
"displayOrder" : 30
} ],
"count" : 4
}
You can obtain a list of consumer information, such as the consumer name and grade.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/Groups
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Group objects. For details about Group, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Group
{
"instanceID":"...",
"name":"...",
"status":"...",
"gradeKey":"...",
"gradeName":"...",
"gradeDisplayOrder":"...",
"description":"...",
"templateCreatorType":"...",
"numOfVolumes":"...",
"numOfVMs":"...",
"numOfHosts":"...",
"volumeAutoAssignFilters":["...", ...],
"vmAutoAssignFilters":["...", ...],
"hostAutoAssignFilters":["...", ...]
}
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
templateCreatorType enum Type indicating whether the consumer can perform editing. The consumer can
perform editing only if the type is "User".
(For details about the valid values, see the table TemplateCreatorType in List of
enumerators.)
User
Default
volumeAutoAssignFilters string[] Assignment rules of volumes that can be assigned to this consumer.
vmAutoAssignFilters string[] Assignment rules of virtual machines that can be assigned to this consumer.
hostAutoAssignFilters string[] Assignment rules of hosts that can be assigned to this consumer.
Status codes
200 OK Success.
[Request Header]
GET /Analytics/v1/objects/Groups
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "group#aea4c579-af9d-4a01-b786-e05740ea687a",
"name" : "Group-20160720111044502",
"status" : "Unknown",
"gradeKey" : "10",
"gradeName" : "Platinum",
"gradeDisplayOrder" : 10,
"description" : "groupxxxxxxxxx",
"templateCreatorType" : "User",
"numOfVolumes" : 0,
"numOfVMs" : 0,
"numOfHosts" : 0,
"volumeAutoAssignFilters" : [ ],
"vmAutoAssignFilters" : [ ],
"hostAutoAssignFilters" : [ ]
}, {
.........
} ],
"count" : 4
}
Related reference
List of enumerators
Creating consumer
You can create a new consumer by specifying information such as the consumer name and grade.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/Groups
Request body
The structure of the request body and the object attributes are as follows:
Group
{
"instanceID":"...",
"name":"...",
"status":"...",
"gradeKey":"...",
"gradeName":"...",
"gradeDisplayOrder":"...",
"description":"...",
"templateCreatorType":"...",
"numOfVolumes":"...",
"numOfVMs":"...",
"numOfHosts":"...",
"volumeAutoAssignFilters":["...", ...],
"vmAutoAssignFilters":["...", ...],
"hostAutoAssignFilters":["...", ...]
}
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
templateCreatorType enum Type indicating whether the consumer can perform editing. The consumer can
perform editing only if the type is "User".
(For details about the valid values, see the table TemplateCreatorType in List of
enumerators.)
User
Default
Attribute Type Description
volumeAutoAssignFilters string[] Assignment rules of volumes that can be assigned to this consumer.
vmAutoAssignFilters string[] Assignment rules of virtual machines that can be assigned to this consumer.
hostAutoAssignFilters string[] Assignment rules of hosts that can be assigned to this consumer.
Response body
The structure of the response body and the object attributes is as follows:
Group
{
"instanceID":"...",
"name":"...",
"status":"...",
"gradeKey":"...",
"gradeName":"...",
"gradeDisplayOrder":"...",
"description":"...",
"templateCreatorType":"...",
"numOfVolumes":"...",
"numOfVMs":"...",
"numOfHosts":"...",
"volumeAutoAssignFilters":["...", ...],
"vmAutoAssignFilters":["...", ...],
"hostAutoAssignFilters":["...", ...]
}
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Attribute Type Description
Unknown
templateCreatorType enum Type indicating whether the consumer can perform editing. The consumer can
perform editing only if the type is "User".
(For details about the valid values, see the table TemplateCreatorType in List of
enumerators.)
User
Default
volumeAutoAssignFilters string[] Assignment rules of volumes that can be assigned to this consumer.
vmAutoAssignFilters string[] Assignment rules of virtual machines that can be assigned to this consumer.
hostAutoAssignFilters string[] Assignment rules of hosts that can be assigned to this consumer.
Status codes
Example code
[Request Header]
POST /Analytics/v1/objects/Groups
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name":"Group-20160720111044502",
"gradeKey":"10",
"description":"groupxxxxxxxxx"
}
[Response Header]
HTTP/1.1 201 Created
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "group#aea4c579-af9d-4a01-b786-e05740ea687a",
"name" : "Group-20160720111044502",
"status" : "Unknown",
"gradeKey" : "10",
"gradeName" : "Platinum",
"gradeDisplayOrder" : 10,
"description" : "groupxxxxxxxxx",
"templateCreatorType" : "User",
"numOfVolumes" : 0,
"numOfVMs" : 0,
"numOfHosts" : 0,
"volumeAutoAssignFilters" : [ ],
"vmAutoAssignFilters" : [ ],
"hostAutoAssignFilters" : [ ]
}
Related reference
List of enumerators
You can obtain information about a specific consumer, such as the consumer name and grade.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/Groups/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Group
{
"instanceID":"...",
"name":"...",
"status":"...",
"gradeKey":"...",
"gradeName":"...",
"gradeDisplayOrder":"...",
"description":"...",
"templateCreatorType":"...",
"numOfVolumes":"...",
"numOfVMs":"...",
"numOfHosts":"...",
"volumeAutoAssignFilters":["...", ...],
"vmAutoAssignFilters":["...", ...],
"hostAutoAssignFilters":["...", ...]
}
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
templateCreatorType enum Type indicating whether the consumer can perform editing. The consumer can
perform editing only if the type is "User".
(For details about the valid values, see the table TemplateCreatorType in List of
enumerators.)
User
Default
volumeAutoAssignFilters string[] Assignment rules of volumes that can be assigned to this consumer.
vmAutoAssignFilters string[] Assignment rules of virtual machines that can be assigned to this consumer.
hostAutoAssignFilters string[] Assignment rules of hosts that can be assigned to this consumer.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/Groups/group%2380d3b2fd-3199-429b-803e-9c7d4c20fe78
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "group#80d3b2fd-3199-429b-803e-9c7d4c20fe78",
"name" : "Group-20160720111049086",
"status" : "Unknown",
"gradeKey" : "10",
"gradeName" : "Platinum",
"gradeDisplayOrder" : 10,
"description" : "groupxxxxxxxxx",
"templateCreatorType" : "User",
"numOfVolumes" : 0,
"numOfVMs" : 0,
"numOfHosts" : 0,
"volumeAutoAssignFilters" : [ ],
"vmAutoAssignFilters" : [ ],
"hostAutoAssignFilters" : [ ]
}
Related reference
List of enumerators
Updating consumer
You can update information about a specific consumer, such as the consumer name and grade.
Execution permission
Admin, Modify
Request line
PUT baseURL/v1/objects/Groups/{id}
Request body
The structure of the request body and the object attributes are as follows:
Group
{
"instanceID":"...",
"name":"...",
"status":"...",
"gradeKey":"...",
"gradeName":"...",
"gradeDisplayOrder":"...",
"description":"...",
"templateCreatorType":"...",
"numOfVolumes":"...",
"numOfVMs":"...",
"numOfHosts":"...",
"volumeAutoAssignFilters":["...", ...],
"vmAutoAssignFilters":["...", ...],
"hostAutoAssignFilters":["...", ...]
}
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
templateCreatorType enum Type indicating whether the consumer can perform editing. The consumer can
perform editing only if the type is "User".
(For details about the valid values, see the table TemplateCreatorType in List of
enumerators.)
User
Default
volumeAutoAssignFilters string[] Assignment rules of volumes that can be assigned to this consumer.
vmAutoAssignFilters string[] Assignment rules of virtual machines that can be assigned to this consumer.
hostAutoAssignFilters string[] Assignment rules of hosts that can be assigned to this consumer.
Response body
The structure of the response body and the object attributes is as follows:
Group
{
"instanceID":"...",
"name":"...",
"status":"...",
"gradeKey":"...",
"gradeName":"...",
"gradeDisplayOrder":"...",
"description":"...",
"templateCreatorType":"...",
"numOfVolumes":"...",
"numOfVMs":"...",
"numOfHosts":"...",
"volumeAutoAssignFilters":["...", ...],
"vmAutoAssignFilters":["...", ...],
"hostAutoAssignFilters":["...", ...]
}
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
templateCreatorType enum Type indicating whether the consumer can perform editing. The consumer can
perform editing only if the type is "User".
(For details about the valid values, see the table TemplateCreatorType in List of
enumerators.)
User
Default
volumeAutoAssignFilters string[] Assignment rules of volumes that can be assigned to this consumer.
vmAutoAssignFilters string[] Assignment rules of virtual machines that can be assigned to this consumer.
hostAutoAssignFilters string[] Assignment rules of hosts that can be assigned to this consumer.
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
PUT /Analytics/v1/objects/Groups/group%2331cf9a64-c9b8-4abf-a5b8-1f11c8d982ac
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name":"Group-20160720111053343",
"gradeKey":"0",
"description":"groupzzzzzz"
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "group#31cf9a64-c9b8-4abf-a5b8-1f11c8d982ac",
"name" : "Group-20160720111053343",
"status" : "Unknown",
"gradeKey" : "0",
"gradeName" : "-",
"gradeDisplayOrder" : 2147483647,
"description" : "groupzzzzzz",
"templateCreatorType" : "User",
"numOfVolumes" : 0,
"numOfVMs" : 0,
"numOfHosts" : 0,
"volumeAutoAssignFilters" : [ ],
"vmAutoAssignFilters" : [ ],
"hostAutoAssignFilters" : [ ]
}
Related reference
List of enumerators
You can delete a specific consumer. Resources assigned to the deleted consumer are set as unassigned (#Unassigned
Resources).
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/Groups/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
[Request Header]
DELETE /Analytics/v1/objects/Groups/group%2331cf9a64-c9b8-4abf-a5b8-1f11c8d982ac
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 204 No Content
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
You can obtain a list of operations that can be performed on a specific consumer.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/Groups/{id}/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
Attribute Type Description
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/Groups/100000/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "updateTargetResource",
"href" : "[Link]
urce/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to assign a specific consumer to resources to be monitored.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/Groups/{id}/actions/updateTargetResource
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
UpdateTargetResourceParam
{
"volumeIDs":["...", ...],
"vmIDs":["...", ...],
"resourceIDs":["...", ...]
}
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/Groups/group%23a6c24393-07c9-4465-ba3f-dc33b9583d74/actions/updateTarg
etResource
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "updateTargetResource",
"href" : "[Link]
ba3f%2ddc33b9583d74/actions/updateTargetResource/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"volumeIDs" : [ ],
"vmIDs" : [ ],
"resourceIDs" : [ ]
} ]
}
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/Groups/{id}/actions/updateTargetResource/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
UpdateTargetResourceParam
{
"volumeIDs":["...", ...],
"vmIDs":["...", ...],
"resourceIDs":["...", ...]
}
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/Groups/group%23fd830c03-a08a-4a96-aed9-55024c4f678a/actions/updateTar
getResource/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "updateTargetResource",
"href" : "[Link]
ba3f%2ddc33b9583d74/actions/updateTargetResource/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"volumeIDs":["raidLdev#410025-00^03^3F"],
"vmIDs" : [],
"resourceIDs" : []
} ]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "b194ea16-2cce-4dee-bf0b-d77b57160620",
"created" : "2016-08-03T[Link].143+09:00",
"updated" : "2016-08-03T[Link].143+09:00",
"completed" : "2016-08-03T[Link].143+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Execution permission
Admin
Request line
GET baseURL/v1/services/GroupsDefinition/actions/generate
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ConsumerDefinitionGenerateParam
{
"baseParameter":"...",
"generationPolicy":"...",
"generationPolicySubParam":"...",
"gradeKey":"..."
}
(For details about the valid values, see the table BaseParameter in List of
enumerators.)
(For details about the valid values, see the table GenerationPolicy in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET Analytics/v1/services/GroupsDefinition/actions/generate
authorization:
Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
www-authenticate: HSSO 18616ecdaa33afda9e179c113bb286e7ebd3a67b_Wm0HGnlmckFqXXwA_V0810
content-type: application/json
content-length: 389
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
{
"name" : "generate",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"baseParameter" : "HostGroup",
"generationPolicy" : "LeadingAlphabets",
"generationPolicySubParam" : "",
"grade" : "",
"autoAssignRelatedResource" : false
} ]
}
Execution permission
Admin
Request line
POST baseURL/v1/services/GroupsDefinition/actions/generate/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ConsumerDefinitionGenerateParam
{
"baseParameter":"...",
"generationPolicy":"...",
"generationPolicySubParam":"...",
"gradeKey":"..."
}
(For details about the valid values, see the table BaseParameter in List of
enumerators.)
(For details about the valid values, see the table GenerationPolicy in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
ConsumerDefinitionGenerateResponse
{
"informationMessage":"..."
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
POST Analytics/v1/services/GroupsDefinition/actions/generate/invoke
authorization:Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "generate",
"href": "[Link]
e",
"method": "POST",
"type": "application/json",
"parameters": [
{
"baseParameter": "HostGroup",
"generationPolicy": "PrecedeSeparator",
"generationPolicySubParam": "-",
"grade": "Bronze",
"autoAssignRelatedResource": false
}
]
}
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
www-authenticate: HSSO dae9a6422f35b2e6a379db33118dd745ca5228_Wm0HGnlmckFqXXwA_V0810
content-type: application/json
content-length: 348
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
{
"instanceID": "c11a5532-649b-40d0-acc2-4653b5d70de7",
"created": "2022-03-31T[Link].670-07:00",
"updated": "2022-03-31T[Link].670-07:00",
"completed": "2022-03-31T[Link].670-07:00",
"state": "success",
"affectedResource": [],
"result": [
{
"instanceID": "consumerDefinition#786722c0-24c0-44ac-b436-cb4d4e52c564"
}
],
}
You can get request information to preview a result of consumer auto creation for a consumer definition.
Execution permission
Admin
Request line
GET baseURL/v1/objects/GroupsDefinition/{id}/actions/preview
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
200 OK Success.
Example code
[Request Header]
GET Analytics/v1/objects/GroupsDefinition/consumerDefinition%23786722c0-24c0-44ac-b436-cb4d4e52c
564/actions/preview
authorization:
Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
www-authenticate: HSSO 2e5791f57e4474325f13e1d36ab6c7f5409519_Wm0HGnlmckFqXXwA_V0810
content-type: application/json
content-length: 265
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
{
"name" : "preview",
"href" : "[Link]
6722c0%2d24c0%2d44ac%2db436%2dcb4d4e52c564/actions/preview/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
You can preview a result of consumer auto creation for a consumer definition.
Execution permission
Admin
Request line
POST baseURL/v1/objects/GroupsDefinition/{id}/actions/preview/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
ConsumerDefinitionPreviewResponse
{
"totalConsumer":"...",
"existingConsumer":"...",
"largestResource":"...",
"previewConsumerList":[{
"consumerName":"...",
"baseSample":"...",
"count":"...",
"type":"...",
"grade":"..."
},
:
],
"isSubmittable":"...",
"errorMessage":"..."
}
baseSample string Sample base parameters of resources that are assigned to.
(For details about the valid values, see the table ConsumerExistenceType in List
of enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
POST Analytics/v1/objects/GroupsDefinition/consumerDefinition%23786722c0-24c0-44ac-b436-cb4d4e52
c564/actions/preview/invoke
authorization:
Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "preview",
"href": "[Link]
722c0%2d24c0%2d44ac%2db436%2dcb4d4e52c564/actions/preview/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
}
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
www-authenticate: HSSO 27fe10c5c21c92b222d62ab1f9b9fb4640758da2_Wm0HGnlmckFqXXwA_V0810
content-type: application/json
content-length: 544
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
{
"instanceID" : "1479050e-5198-4185-925f-5eaf5d543ce4",
"created" : "2022-03-31T[Link].899-07:00",
"updated" : "2022-03-31T[Link].899-07:00",
"completed" : "2022-03-31T[Link].899-07:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"totalConsumer" : 1,
"existingConsumer" : 0,
"largestResource" : 40,
"previewConsumerList" : [ {
"consumerName" : "_A_HostGroup",
"baseSample" : "HostGroup-1A001",
"count" : 40,
"type" : "New",
"grade" : "Bronze"
} ]
} ]
}
You can get request information to submit a consumer auto creation task.
Execution permission
Admin
Request line
GET baseURL/v1/objects/GroupsDefinition/{id}/actions/submit
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET Analytics/v1/objects/GroupsDefinition/consumerDefinition%23786722c0-24c0-44ac-b436-cb4d4e52c
564/actions/submit
authorization:
Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
www-authenticate: HSSO e91797cce0d9a1b674ff523966a56398ba92ea_Wm0HGnlmckFqXXwA_V0810
content-type: application/json
content-length: 263
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
{
"name" : "submit",
"href" : "[Link]
6722c0%2d24c0%2d44ac%2db436%2dcb4d4e52c564/actions/submit/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
Execution permission
Admin
Request line
POST baseURL/v1/objects/GroupsDefinition/{id}/actions/submit/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
ConsumerDefinitionSubmitResponse
{
"message":"...",
"createdConsumers":"...",
"createdRules":"...",
"modifiedRules":"..."
}
Status codes
200 OK Success.
Example code
[Request Header]
POST Analytics/v1/objects/GroupsDefinition/consumerDefinition%23786722c0-24c0-44ac-b436-cb4d4e52
c564/actions/submit/invoke
authorization:Basic c3lzdGVtOm1hbmFnZXI=
content-type:application/json
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "submit",
"href" : "[Link]
6722c0%2d24c0%2d44ac%2db436%2dcb4d4e52c564/actions/submit/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
www-authenticate: HSSO dc9c674d68f9ce230f4e199e1e6fd3f96c3db0_Wm0HGnlmckFqXXwA_V0810
content-type: application/json
content-length: 275
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
{
"instanceID" : "b01a367f-e950-4bd7-9f2f-44659407d5f9",
"created" : "2022-04-01T[Link].809-07:00",
"updated" : "2022-04-01T[Link].809-07:00",
"completed" : "2022-04-01T[Link].809-07:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ { } ]
}
You can get request information to export a consumer definition as a csv file.
Execution permission
Admin
Request line
GET baseURL/v1/objects/GroupsDefinition/{id}/actions/export
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET Analytics/v1/objects/GroupsDefinition/consumerDefinition%23786722c0-24c0-44ac-b436-cb4d4e52c
564/actions/export
authorization:
Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
www-authenticate: HSSO 6fb71fd328b81cc33f47c76dd2a4ee2c9cb6fee7_Wm0HGnlmckFqXXwA_V0810
content-type: application/json
content-length: 255
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
{
"name" : "export",
"href" : "[Link]
6722c0-24c0-44ac-b436-cb4d4e52c564/actions/export/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
Execution permission
Admin
Request line
POST baseURL/v1/objects/GroupsDefinition/{id}/actions/export/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Response body
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
POST Analytics/v1/objects/GroupsDefinition/consumerDefinition%23786722c0-24c0-44ac-b436-cb4d4e52
c564/actions/export/invoke
authorization:Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json,text/csv
Content-Type: application/json
[Request Body]
{
"name": "export",
"href": "[Link]
24c0-44ac-b436-cb4d4e52c564/actions/export/invoke",
"method": "POST",
"type": "application/json",
"parameters": []
}
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
content-disposition: attachment; filename="VOLUME_Host_Group_Name_PrecedeSeparator_Bronze_202203
[Link]"; creation-date="Fri, 01 Apr 2022 [Link] GMT"
x-consumer-creation-plan-csv-filename: VOLUME_Host_Group_Name_PrecedeSeparator_Bronze_2022033119
[Link]
access-control-expose-headers: X-Consumer-Creation-Plan-Csv-Filename, Content-Disposition
www-authenticate: HSSO 767c4dcc631df853945e2272f695555997d6804a_Wm0HGnlmckFqXXwA_V0810
content-type: text/csv
content-length: 288
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
"CONSUMER","GRADE","RESOURCE TYPE","ATTRIBUTE","CONDITION","VALUE","RULE NAME","RULE DESCRIPTIO
N"
"_A_HostGroup","Bronze","Volume","Host Group Name","Starts with","HostGroup","_A_HostGroup_Host
Group Name_Starts with","_A_Volume_Host Group Name_PrecedeSeparator_Bronze_System_2022033119074
3"
You can get request information to register a consumer definition csv file.
Execution permission
Admin
Request line
GET baseURL/v1/services/GroupsDefinition/actions/register
Request body
Not applicable.
Response body
Status codes
200 OK Success.
Example code
[Request Header]
GET Analytics/V1/services/GroupsDefinition/actions/register
authorization:Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
date: Fri, 01 Apr 2022 [Link] GMT
server: CosminexusComponentContainer
cache-control: no-cache, must-revalidate, private, max-age=0
www-authenticate: HSSO 2e255eb2de6aef161353a4e3ca421813012f322_Wm0HGnlmckFqXXwA_V0810
content-type: text/html
content-length: 274
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors 'self'
[Response Body]
<html>
<body>
<form method="POST" action="[Link]
ons/register/invoke" enctype="multipart/form-data">
<input type="file" name="csv"/>
<input type="submit" value="Submit"/>
</form>
</body>
</html>
Execution permission
Admin
Request line
POST baseURL/v1/services/GroupsDefinition/actions/register/invoke
Request body
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST Analytics/V1/services/GroupsDefinition/actions/register/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: multipart/form-data;
[Response Header]
HTTP/1.1 200
Date: Fri, 01 Apr 2022 [Link] GMT
Server: CosminexusComponentContainer
Cache-Control: no-cache, must-revalidate, private, max-age=0
WWW-Authenticate: HSSO eaab59c82e6b46e139979fab8b8431dd2e8c671a_Wm0HGnlmckFqXXwA_V0810
Content-Type: application/json
Content-Length: 480
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Security-Policy: frame-ancestors 'self'
[Response Body]
{ [480 bytes data]
100 1183 100 480 100 703 1660 2432 --:--:-- --:--:-- --:--:-- 4107{
"instanceID" : "fece0b00-ba69-4e34-8d33-3cd19950e394",
"created" : "2022-04-01T[Link].558-07:00",
"updated" : "2022-04-01T[Link].558-07:00",
"completed" : "2022-04-01T[Link].558-07:00",
"state" : "success",
"affectedResource" : [ "[Link]
efinition%2364c0f284%2db22f%2d41ae%2db493%2dee8a47041d35" ],
"result" : [ {
"instanceID" : "consumerDefinition#64c0f284-b22f-41ae-b493-ee8a47041d35"
} ]
}
You can obtain a list of connection settings for the Analyzer detail view server, such as the host name and user name.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/HdcaSettings
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of HdcaSetting objects. For details about HdcaSetting, see the table
data anyType[]
below.
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
HdcaSetting
{
"instanceID":"...",
"host":"...",
"protocol":"...",
"port":"...",
"userName":"...",
"connectionResult":"...",
"url":"...",
"message":"...",
"messageID":"..."
}
host string Host name used for connecting to the Analyzer detail view server.
protocol string Protocol used for connecting to the Analyzer detail view server.
port int Port number used for connecting to the Analyzer detail view server.
connectionResult boolean Whether or not connection to the Analyzer detail view server was successful.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/HdcaSettings
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "997104105",
"host" : "[Link]",
"protocol" : "https",
"port" : 8443,
"userName" : "admin",
"connectionResult" : false
} ],
"count" : 1
}
You can update information about a specific connection setting for the Analyzer detail view server, such as the host name and
user name.
Execution permission
Admin
Request line
PUT baseURL/v1/objects/HdcaSettings/{id}
Request body
The structure of the request body and the object attributes are as follows:
HdcaSetting
{
"instanceID":"...",
"host":"...",
"protocol":"...",
"port":"...",
"userName":"...",
"password":"...",
"connectionResult":"...",
"url":"...",
"message":"...",
"messageID":"..."
}
host string Host name used for connecting to the Analyzer detail view server.
protocol string Protocol used for connecting to the Analyzer detail view server.
port int Port number used for connecting to the Analyzer detail view server.
password string Password used for executing the user API. Set a string encoded in Base64.
connectionResult boolean Whether or not connection to the Analyzer detail view server was successful.
Attribute Type Description
Response body
The structure of the response body and the object attributes is as follows:
HdcaSetting
{
"instanceID":"...",
"host":"...",
"protocol":"...",
"port":"...",
"userName":"...",
"connectionResult":"...",
"url":"...",
"message":"...",
"messageID":"..."
}
host string Host name used for connecting to the Analyzer detail view server.
protocol string Protocol used for connecting to the Analyzer detail view server.
port int Port number used for connecting to the Analyzer detail view server.
connectionResult boolean Whether or not connection to the Analyzer detail view server was successful.
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
PUT /Analytics/v1/objects/HdcaSettings/997104105
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"host":"[Link]",
"protocol":"https",
"port":"8443",
"userName":"admin",
"password":"aWFzMTIz"
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "997104105",
"host" : "[Link]",
"protocol" : "https",
"port" : 8443,
"userName" : "admin",
"connectionResult" : false
}
You can obtain information about a specific connection setting for the Analyzer detail view server, such as the host name and user
name.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/HdcaSettings/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
HdcaSetting
{
"instanceID":"...",
"host":"...",
"protocol":"...",
"port":"...",
"userName":"...",
"connectionResult":"...",
"url":"...",
"message":"...",
"messageID":"..."
}
host string Host name used for connecting to the Analyzer detail view server.
protocol string Protocol used for connecting to the Analyzer detail view server.
port int Port number used for connecting to the Analyzer detail view server.
connectionResult boolean Whether or not connection to the Analyzer detail view server was successful.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/HdcaSettings/997104105
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "997104105",
"host" : "[Link]",
"protocol" : "https",
"port" : 8443,
"userName" : "admin",
"connectionResult" : false,
"url" : "[Link]
1"
}
Getting a list of operations for configuring the connection settings of the Analyzer detail view
server
You can obtain a list of operations that can be performed on a specific connection setting for the Analyzer detail view server.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/HdcaSettings/{id}/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
[Request Header]
GET /Analytics/v1/objects/HdcaSettings/997104105/actions HTTP/1.1
Host: localhost:22015
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: curl/7.49.1
Accept: application/json
Content-Type:application/json
[Response Header]
HTTP/1.1 200 OK
Date: Tue, 31 Jan 2017 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8a2e74abf3032bec56e82d2f424d7874b77e2_ZAlDR1YdfRBWBxNW_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getInContextLaunchUrl",
"href" : "[Link]
ntextLaunchUrl/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to obtain the URL for connecting to the Analyzer detail view server, with a resource
selected.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/HdcaSettings/{id}/actions/getInContextLaunchUrl
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
HdcaInContextLaunchParam
{
"resourceId":"..."
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/HdcaSettings/997104105/actions/getInContextLaunchUrl HTTP/1.1
Host: localhost:22015
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: curl/7.49.1
Accept: application/json
Content-Type:application/json
[Response Header]
HTTP/1.1 200 OK
Date: Tue, 31 Jan 2017 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 49b4df80c683e1e0abcdceeeaeec1a24559ba0fd_ZAlDR1YdfRBWBxNW_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getInContextLaunchUrl",
"href" : "[Link]
extLaunchUrl/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"resourceId" : "resourceId"
} ]
}
You can obtain the URL for connecting to the Analyzer detail view server, with a resource selected.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/HdcaSettings/{id}/actions/getInContextLaunchUrl/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
HdcaInContextLaunchParam
{
"resourceId":"..."
}
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
HdcaInContextLaunchUrl
{
"inContextLaunchUrl":"..."
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/HdcaSettings/997104105/actions/getInContextLaunchUrl/invoke
Host: localhost:22015
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: curl/7.49.1
Accept: application/json
Content-Type:application/json
[Request Body]
{
"name" : "getInContextLaunchUrl",
"href" : "[Link]
textLaunchUrl/invoke",
"method" : "POST",
"type" : "application/json",
"parameters": [
{
"resourceId": "raidLdev#51547-00^00^00"
}
]
}
[Response Header]
HTTP/1.1 200 OK
Cache-Control: no-cache
Connection: Keep-Alive
Content-Type: application/json
Date: Tue, 24 Jan 2017 [Link] GMT
Server: Cosminexus HTTP Server
Transfer-Encoding: chunked
WWW-Authenticate: HSSO c450462eec01893d4c1ebcba7e7876538bd94_VwBvNGpyDgxyCUY3eXZdCQ==_V0810
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection : 1; mode=block
[Response Body]
{
"instanceID": "685ca5af-1ee3-4168-8873-f9ed5bebc431",
"created": "2017-01-24T[Link].364+09:00",
"updated": "2017-01-24T[Link].364+09:00",
"completed": "2017-01-24T[Link].364+09:00",
"state": "success",
"affectedResource": [],
"result": [
{
"inContextLaunchUrl": "[Link]
d-9212-17bb173123e7&resSig=cmFpZExkZXYjNTE1NDctMDBeMDBeMDA="
}
]
}
Getting a list of operations for configuring Analyzer detail view server connection settings
You can obtain a list of operations related to connection settings for the Analyzer detail view server.
Execution permission
Admin
Request line
GET baseURL/v1/services/HdcaSettings/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/HdcaSettings/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "checkConnection",
"href" : "[Link]
invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to check the connection to the Analyzer detail view server.
Execution permission
Admin
Request line
GET baseURL/v1/services/HdcaSettings/actions/checkConnection
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
HdcaSetting
{
"instanceID":"...",
"host":"...",
"protocol":"...",
"port":"...",
"userName":"...",
"connectionResult":"...",
"url":"...",
"message":"...",
"messageID":"..."
}
host string Host name used for connecting to the Analyzer detail view server.
protocol string Protocol used for connecting to the Analyzer detail view server.
port int Port number used for connecting to the Analyzer detail view server.
connectionResult boolean Whether or not connection to the Analyzer detail view server was successful.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/HdcaSettings/actions/checkConnection
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 891f1a62fea230bee798f496e1189ce2ead3fca_Y2UOI2pkMXQ=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name": "checkConnection",
"href": "[Link]
nvoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"instanceID": "997104105",
"host": "hdca server",
"protocol": "https",
"port": 8443,
"userName": "admin",
"connectionResult": false
}
]
}
You can check the connection to the Analyzer detail view server.
Execution permission
Admin
Request line
POST baseURL/v1/services/HdcaSettings/actions/checkConnection/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
HdcaSetting
{
"instanceID":"...",
"host":"...",
"protocol":"...",
"port":"...",
"userName":"...",
"password":"...",
"connectionResult":"...",
"url":"...",
"message":"...",
"messageID":"..."
}
host string Host name used for connecting to the Analyzer detail view server.
protocol string Protocol used for connecting to the Analyzer detail view server.
port int Port number used for connecting to the Analyzer detail view server.
password string Password used for executing the user API. Set a string encoded in Base64.
connectionResult boolean Whether or not connection to the Analyzer detail view server was successful.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of HdcaSetting objects. For details about HdcaSetting, see the table
result anyType[]
below.
HdcaSetting
{
"instanceID":"...",
"host":"...",
"protocol":"...",
"port":"...",
"userName":"...",
"connectionResult":"...",
"url":"...",
"message":"...",
"messageID":"..."
}
host string Host name used for connecting to the Analyzer detail view server.
protocol string Protocol used for connecting to the Analyzer detail view server.
port int Port number used for connecting to the Analyzer detail view server.
connectionResult boolean Whether or not connection to the Analyzer detail view server was successful.
Status codes
200 OK Success.
[Request Header]
POST /Analytics/v1/services/HdcaSettings/actions/checkConnection/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "checkConnection",
"href": "[Link]
oke",
"method": "POST",
"type": "application/json",
"parameters":[{
"instanceID":997104105,
"host":"[Link]",
"protocol":"https",
"port":"8443",
"userName":"admin",
"password":"aWFzMTIz"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "24aa67f4-26cb-4b89-8b22-acf9cecdc50b",
"created" : "2016-08-12T[Link].372+09:00",
"updated" : "2016-08-12T[Link].372+09:00",
"completed" : "2016-08-12T[Link].372+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"port" : 0,
"connectionResult" : true
} ]
}
You can obtain a list of Storage I/O control configuration tasks and task-related information, such as names, descriptions, and
statuses.
Execution permission
Request line
GET baseURL/v1/objects/IoControlHistory
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
IoControlHistory
{
"instanceID":"...",
"taskName":"...",
"description":"...",
"targetMetric":"...",
"targetVolumes":["...", ...],
"limitationMode":"...",
"limitValue":"...",
"status":"...",
"statusLastUpdateDateTime":,
"registeredDatetime":,
"registeredUserName":"...",
"executionType":"...",
"automationDirectorTaskIDs":["...", ...]
}
(For details about the valid values, see the table IoControlMetricType in List of
enumerators.)
(For details about the valid values, see the table LimitationMode in List of
enumerators.)
limitValue long Upper limit. Not used if limitationMode is "OFF". When targetMetric is
"TransferRate", the unit is MBps.
(For details about the valid values, see the table TaskStatus in List of
enumerators.)
Attribute Type Description
statusLastUpdateDateTime datetime Date and time when the task status was last obtained.
registeredDatetime datetime Date and time when the task was registered.
(For details about the valid values, see the table ExecutionType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET [Link] HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 05 Sep 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 5d3b478672e01d126f372d5f0fcd6b2d6e2227_Vlo8Y30Idn8EY0BdB3IEfwgabiA=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "TaskID",
"taskName" : "TaskName0010",
"description" : "TaskDescription",
"targetMetric" : "IOPS",
"targetVolumes" : [ "raidLdev#00^00^01", "raidLdev#00^00^02" ],
"limitationMode" : "ON",
"limitValue" : 2147483647,
"status" : "Success",
"statusLastUpdateDateTime" : "2016-09-05T[Link].002+09:00",
"registeredDatetime" : "2016-09-05T[Link].994+09:00",
"registeredUserName" : "User",
"executionType" : "AutomationDirector",
"automationDirectorTaskIDs" : [ "AutoTask1", "AutoTask2" ]
} ],
"count" : 1
}
Related reference
List of enumerators
You can obtain information about a specific Storage I/O control configuration task, such as name, description, and status.
Execution permission
Request line
GET baseURL/v1/objects/IoControlHistory/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
IoControlHistory
{
"instanceID":"...",
"taskName":"...",
"description":"...",
"targetMetric":"...",
"targetVolumes":["...", ...],
"limitationMode":"...",
"limitValue":"...",
"status":"...",
"statusLastUpdateDateTime":,
"registeredDatetime":,
"registeredUserName":"...",
"executionType":"...",
"automationDirectorTaskIDs":["...", ...]
}
(For details about the valid values, see the table IoControlMetricType in List of
enumerators.)
(For details about the valid values, see the table LimitationMode in List of
enumerators.)
limitValue long Upper limit. Not used if limitationMode is "OFF". When targetMetric is
"TransferRate", the unit is MBps.
(For details about the valid values, see the table TaskStatus in List of
enumerators.)
statusLastUpdateDateTime datetime Date and time when the task status was last obtained.
registeredDatetime datetime Date and time when the task was registered.
(For details about the valid values, see the table ExecutionType in List of
enumerators.)
Status codes
200 OK Success.
Status code Reason phrase Description
Example code
[Request Header]
GET [Link] HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 05 Sep 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 7891f7d443804d8e3f5ac1159687edd1d4fbbbec_Vlo8Y30Idn8EY0BdB3IEfwgabiA=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"instanceID" : "dummyTaskId",
"taskName" : "dummyTask",
"description" : "dummyDescription",
"targetMetric" : "IOPS",
"targetVolumes" : [ "raidLdev#dummy1", "raidLdev#dummy2" ],
"limitationMode" : "ON",
"limitValue" : 2147483647,
"status" : "Success",
"statusLastUpdateDateTime" : "2016-09-05T[Link].862+09:00",
"registeredDatetime" : "2016-09-05T[Link].862+09:00",
"registeredUserName" : "dummyUser",
"executionType" : "AutomationDirector",
"automationDirectorTaskIDs" : [ "hadtask1", "hadtask2" ]
}
Related reference
List of enumerators
Getting a list of actions related to Storage I/O control configuration task history
You can obtain a list of operations related to Storage I/O control configuration task history.
Execution permission
GET baseURL/v1/services/IoControlHistory/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET [Link] HTTP/1.1
Host: localhost:22015
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Accept: application/json, text/javascript, */*; q=0.01
Accept-Language: null
Accept-Encoding: gzip, deflate
Content-Type: application/json
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Cookie: JSESSIONID=00A8DFD2B38317A0C74369F0866CF67C
Proxy-Authorization: Basic NzA2MzMwOTI6aGl0YWNoaW5va2kyMTE=
Connection: keep-alive
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 05 Sep 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 31988d251331f5c8535f3214d24d9bb3d744fd6_Vlo8Y30Idn8EY0BdB3IEfwgabiA=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"instanceID" : "actions",
"taskName" : "dummyTask",
"description" : "dummyDescription",
"targetMetric" : "IOPS",
"targetVolumes" : [ "raidLdev#dummy1", "raidLdev#dummy2" ],
"limitationMode" : "ON",
"limitValue" : 2147483647,
"status" : "Success",
"statusLastUpdateDateTime" : "2016-09-05T[Link].674+09:00",
"registeredDatetime" : "2016-09-05T[Link].674+09:00",
"registeredUserName" : "dummyUser",
"executionType" : "AutomationDirector",
"automationDirectorTaskIDs" : [ "hadtask1", "hadtask2" ]
}
Getting the parameter used to update the status of a Storage I/O control settings task
The following operation is the initial step to modify the status of a Storage I/O control configuration task.
Execution permission
Request line
GET baseURL/v1/services/IoControlHistory/actions/updateStatus
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
IoControlHistoryUpdateStatusParam
{
"ioControlTaskIDs":["...", ...]
}
ioControlTaskIDs string[] IDs of the I/O control settings tasks whose statuses are to be updated. If no IDs
are specified, the statuses of all tasks will be updated.
Status codes
200 OK Success.
Example code
[Request Header]
GET [Link] HTTP/1.1
Host: localhost:22015
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Accept: application/json, text/javascript, */*; q=0.01
Accept-Language: null
Accept-Encoding: gzip, deflate
Content-Type: application/json
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Cookie: JSESSIONID=00A8DFD2B38317A0C74369F0866CF67C
Proxy-Authorization: Basic NzA2MzMwOTI6aGl0YWNoaW5va2kyMTE=
Connection: keep-alive
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 05 Sep 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO f789a859ef16ba7f58d80f03318163682136b2f_Vlo8Y30Idn8EY0BdB3IEfwgabiA=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"name" : "updateStatus",
"href" : "[Link]
nvoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"ioControlTaskIDs" : [ "0" ]
} ]
}
You can modify the status of a Storage I/O control configuration task.
Execution permission
Request line
POST baseURL/v1/services/IoControlHistory/actions/updateStatus/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
IoControlHistoryUpdateStatusParam
{
"ioControlTaskIDs":["...", ...]
}
ioControlTaskIDs string[] IDs of the I/O control settings tasks whose statuses are to be updated. If no IDs
are specified, the statuses of all tasks will be updated.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST [Link] H
TTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "updateStatus",
"href" : "[Link]
nvoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"ioControlTaskIDs" : [ "0" ]
} ]
}
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 05 Sep 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 6f4d0a7a621771443e4c67ae3c32751aa6c3ad_Vlo8Y30Idn8EY0BdB3IEfwgabiA=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"instanceID" : "0a06360c-ea4c-4fa4-aef8-ae458d53d809",
"created" : "2016-09-05T[Link].323+09:00",
"updated" : "2016-09-05T[Link].323+09:00",
"completed" : "2016-09-05T[Link].323+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
You can obtain a list of operations related to configuring Storage I/O control settings.
Execution permission
StorageOps
Request line
GET baseURL/v1/services/IoControlSettings/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET [Link] HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 05 Sep 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 726e2e9a29a516a8cc284a24e753d4c6ac75a28_Vlo8Y30Idn8EY0BdB3IEfwgabiA=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "submit",
"href" : "[Link]
ke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to configure Storage I/O control settings.
Execution permission
StorageOps
Request line
GET baseURL/v1/services/IoControlSettings/actions/submit
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
IoControlSettingParam
{
"taskName":"...",
"description":"...",
"targetMetric":"...",
"targetVolumes":["...", ...],
"limitationMode":"...",
"limitValue":"..."
}
(For details about the valid values, see the table IoControlMetricType in List of
enumerators.)
(For details about the valid values, see the table LimitationMode in List of
enumerators.)
limitValue integer Upper limit. Not used if limitationMode is "OFF". When targetMetric is
"TransferRate", the unit is MBps.
Status codes
200 OK Success.
Example code
[Request Header]
GET [Link] HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 05 Sep 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO ed36ffc15b137a3d5a97dec11e134bc73b8fb4b_Vlo8Y30Idn8EY0BdB3IEfwgabiA=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"name" : "submit",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"taskName" : "taskName",
"description" : "taskDescription",
"targetMetric" : "IOPS",
"targetVolumes" : [ "0" ],
"limitationMode" : "ON",
"limitValue" : 1
} ]
}
Related reference
List of enumerators
You can configure Storage I/O control settings. Task IDs generated during the configuration task are returned as response data.
Execution permission
StorageOps
Request line
POST baseURL/v1/services/IoControlSettings/actions/submit/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
IoControlSettingParam
{
"taskName":"...",
"description":"...",
"targetMetric":"...",
"targetVolumes":["...", ...],
"limitationMode":"...",
"limitValue":"..."
}
(For details about the valid values, see the table IoControlMetricType in List of
enumerators.)
(For details about the valid values, see the table LimitationMode in List of
enumerators.)
limitValue integer Upper limit. Not used if limitationMode is "OFF". When targetMetric is
"TransferRate", the unit is MBps.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of InstanceID objects. For details about InstanceID, see the table below.
result anyType[]
InstanceID
{
"instanceID":"..."
}
Status codes
200 OK Success.
Example code
[Request Header]
POST [Link] HTTP/
1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "submit",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters": [
{
"taskName": "taskName001122",
"description": "taskDescription",
"targetMetric": "IOPS",
"targetVolumes": [
"raidLdev#10182-00^FE^F5"
],
"limitationMode": "ON",
"limitValue": 1
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 05 Sep 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO c1fec785ac4156f812e3753a676080908c5c98d0_Vlo8Y30Idn8EY0BdB3IEfwgabiA=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
[Response Body]
{
"instanceID" : "8a25cc50-b220-4285-bf6a-6fc71a3b3c78",
"created" : "2016-09-05T[Link].625+09:00",
"updated" : "2016-09-05T[Link].626+09:00",
"completed" : "2016-09-05T[Link].626+09:00",
"state" : "success",
"affectedResource" : [ "[Link]
rolTask%23eda080ec%2dd675%2d4af6%2d95f6%2dabd5bf557ecb" ],
"result" : [ {
"instanceID" : "iaaIoControlTask#eda080ec-d675-4af6-95f6-abd5bf557ecb"
} ]
}
Related reference
List of enumerators
You can obtain a list of operations that can be performed on sessions that use HSSO tokens.
Execution permission
Request line
GET baseURL/v1/services/KeepAlive/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
Attribute Type Description
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Status code Reason phrase Description
Example code
[Request Header]
GET /Analytics/v1/services/KeepAlive/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 50a6ea7230762530879b2914c3ac12144074638c_Y2UOI2pkMXQ=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data": [
{
"name": "submit",
"href": "[Link]
e",
"method": "POST",
"type": "application/json",
"parameters": [
]
}
],
"count": 1
}
The following operation is the initial step to extend the valid time period of a session that uses HSSO tokens.
Execution permission
Request line
GET baseURL/v1/services/KeepAlive/actions/submit
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/KeepAlive/actions/submit
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "submit",
"href" : "[Link]
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
You can extend the valid time period of a session that uses HSSO tokens.
Execution permission
Request line
POST baseURL/v1/services/KeepAlive/actions/submit/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of KeepAlive objects. For details about KeepAlive, see the table below.
result anyType[]
KeepAlive
{
"timeToLive":"..."
}
KeepAlive (Type: KeepAlive)
timeToLive long Period during which the session is available by the HSSO token (sec.)
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/KeepAlive/actions/submit/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "submit",
"href" : "[Link]
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "43f90f1e-c0c3-41d1-a5dd-4666b2ba7c90",
"created" : "2016-08-12T[Link].371+09:00",
"updated" : "2016-08-12T[Link].400+09:00",
"completed" : "2016-08-12T[Link].400+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"timeToLive" : 1000
} ]
}
You can obtain a list of information about email addresses, such as the email addresses and assigned notification profiles.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/MailAddress
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of MailAddress objects. For details about MailAddress, see the table
data anyType[]
below.
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
MailAddress
{
"instanceID":"...",
"email":"...",
"isActive":"...",
"description":"...",
"assignedConditionProfilesIDs":["...", ...],
"assignedConditionProfiles":["...", ...]
}
isActive boolean Whether or not the email addresses are enabled as notification destinations.
For enabled addresses, "true" is set. For disabled addresses, "false" is set.
assignedConditionProfilesIDs string[] ID of the condition profile for the notification condition in which this email
address is specified as the destination address
Attribute Type Description
assignedConditionProfiles string[] Name of the condition profile for the notification condition in which this email
address is specified as the destination address
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/MailAddress
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "mailAddress#ff6bb9a9-cb64-4f6d-8041-5908744738eb",
"email" : "admin@[Link]",
"isActive" : true,
"description" : "description",
"assignedConditionProfilesIDs" : [ ],
"assignedConditionProfiles" : [ ]
} ],
"count" : 1
}
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/MailAddress
Request body
The structure of the request body and the object attributes are as follows:
MailAddress
{
"instanceID":"...",
"email":"...",
"isActive":"...",
"description":"...",
"assignedConditionProfilesIDs":["...", ...],
"assignedConditionProfiles":["...", ...]
}
isActive boolean Whether or not the email addresses are enabled as notification destinations.
For enabled addresses, "true" is set. For disabled addresses, "false" is set.
assignedConditionProfilesIDs string[] ID of the condition profile for the notification condition in which this email
address is specified as the destination address
assignedConditionProfiles string[] Name of the condition profile for the notification condition in which this email
address is specified as the destination address
Response body
The structure of the response body and the object attributes is as follows:
MailAddress
{
"instanceID":"...",
"email":"...",
"isActive":"...",
"description":"...",
"assignedConditionProfilesIDs":["...", ...],
"assignedConditionProfiles":["...", ...]
}
isActive boolean Whether or not the email addresses are enabled as notification destinations.
For enabled addresses, "true" is set. For disabled addresses, "false" is set.
assignedConditionProfilesIDs string[] ID of the condition profile for the notification condition in which this email
address is specified as the destination address
assignedConditionProfiles string[] Name of the condition profile for the notification condition in which this email
address is specified as the destination address
Status codes
Example code
[Request Header]
POST /Analytics/v1/objects/MailAddress
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"email":"admin@[Link]",
"isActive":true,
"description":"description",
"assignedConditionProfilesIDs":[1,2],
"assignedConditionProfiles":["EventProfile-1","EventProfile-2"]
}
[Response Header]
HTTP/1.1 201 Created
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "mailAddress#b2dd1785-bc8a-4cb2-90d2-cd6a41aab82c",
"email" : "admin@[Link]",
"isActive" : true,
"description" : "description",
"assignedConditionProfilesIDs" : [ ],
"assignedConditionProfiles" : [ ]
}
You can obtain information about a specific email address, such as the assigned notification profile.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/MailAddress/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
MailAddress
{
"instanceID":"...",
"email":"...",
"isActive":"...",
"description":"...",
"assignedConditionProfilesIDs":["...", ...],
"assignedConditionProfiles":["...", ...]
}
isActive boolean Whether or not the email addresses are enabled as notification destinations.
For enabled addresses, "true" is set. For disabled addresses, "false" is set.
assignedConditionProfilesIDs string[] ID of the condition profile for the notification condition in which this email
address is specified as the destination address
assignedConditionProfiles string[] Name of the condition profile for the notification condition in which this email
address is specified as the destination address
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/MailAddress/mailAddress%23b2dd1785-bc8a-4cb2-90d2-cd6a41aab82c
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "mailAddress#b2dd1785-bc8a-4cb2-90d2-cd6a41aab82c",
"email" : "admin@[Link]",
"isActive" : true,
"description" : "description",
"assignedConditionProfilesIDs" : [ ],
"assignedConditionProfiles" : [ ]
}
You can update information about a specific email address, such as the assigned notification profile.
Execution permission
Admin, Modify
Request line
PUT baseURL/v1/objects/MailAddress/{id}
Request body
The structure of the request body and the object attributes are as follows:
MailAddress
{
"instanceID":"...",
"email":"...",
"isActive":"...",
"description":"...",
"assignedConditionProfilesIDs":["...", ...],
"assignedConditionProfiles":["...", ...]
}
isActive boolean Whether or not the email addresses are enabled as notification destinations.
For enabled addresses, "true" is set. For disabled addresses, "false" is set.
assignedConditionProfilesIDs string[] ID of the condition profile for the notification condition in which this email
address is specified as the destination address
assignedConditionProfiles string[] Name of the condition profile for the notification condition in which this email
address is specified as the destination address
Response body
The structure of the response body and the object attributes is as follows:
MailAddress
{
"instanceID":"...",
"email":"...",
"isActive":"...",
"description":"...",
"assignedConditionProfilesIDs":["...", ...],
"assignedConditionProfiles":["...", ...]
}
isActive boolean Whether or not the email addresses are enabled as notification destinations.
For enabled addresses, "true" is set. For disabled addresses, "false" is set.
assignedConditionProfilesIDs string[] ID of the condition profile for the notification condition in which this email
address is specified as the destination address
assignedConditionProfiles string[] Name of the condition profile for the notification condition in which this email
address is specified as the destination address
Status codes
200 OK Success.
Example code
[Request Header]
PUT /Analytics/v1/objects/MailAddress/mailAddress%234ac8f61f-d97c-4225-91ce-f4bb10530e24
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"instanceID":"mailAddress#4ac8f61f-d97c-4225-91ce-f4bb10530e24",
"email":"admin@[Link]",
"isActive":false,
"description":"xxxxx",
"assignedConditionProfilesIDs":[1,2],
"assignedConditionProfiles":["EventProfile-1","EventProfile-2"]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "mailAddress#4ac8f61f-d97c-4225-91ce-f4bb10530e24",
"email" : "admin@[Link]",
"isActive" : false,
"description" : "xxxxx",
"assignedConditionProfilesIDs" : [ ],
"assignedConditionProfiles" : [ ]
}
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/MailAddress/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
Example code
[Request Header]
DELETE /Analytics/v1/objects/MailAddress/mailAddress%23b2dd1785-bc8a-4cb2-90d2-cd6a41aab82c
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 204 No Content
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
You can obtain a list of operations that can be performed on a specific email address.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/MailAddress/{id}/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/MailAddress/111111/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 30f198fbc8b17b25ed2d623b761929ba5a56df2_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ ],
"count" : 0
}
The following operation is the initial step to assign a notification profile to a specific email address.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/MailAddress/{id}/actions/updateTargetNotificationProfile
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
UpdateTargetNotificationProfileParam
{
"notificationProfileParamIDs":["...", ...]
}
notificationProfileParamIDs long[] Specify the IDs of all condition profiles for notification conditions to be
assigned to the destination addresses. If there are condition profiles that have
already been assigned, they are de-assigned by not specifying their IDs. To de-
assign all condition profiles, specify an empty list.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/MailAddress/mailAddress%239a9e8f87-5872-45b1-958e-5628c6e6d899/action
s/updateTargetNotificationProfile
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "updateTargetNotificationProfile",
"href" : "[Link]
872%2d45b1%2d958e%2d5628c6e6d899/actions/updateTargetNotificationProfile/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"notificationProfileParamIDs" : [ ]
} ]
}
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/MailAddress/{id}/actions/updateTargetNotificationProfile/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
UpdateTargetNotificationProfileParam
{
"notificationProfileParamIDs":["...", ...]
}
notificationProfileParamIDs long[] Specify the IDs of all condition profiles for notification conditions to be
assigned to the destination addresses. If there are condition profiles that have
already been assigned, they are de-assigned by not specifying their IDs. To de-
assign all condition profiles, specify an empty list.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/MailAddress/mailAddress%239a9e8f87-5872-45b1-958e-5628c6e6d899/action
s/updateTargetNotificationProfile/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "updateTargetNotificationProfile",
"href" : "[Link]
2%2d45b1%2d958e%2d5628c6e6d899/actions/updateTargetNotificationProfile/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"notificationProfileParamIDs": ["notificationProfile#202c7713-b158-458e-9a5c-022318628723"]
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "c0720425-e506-4c2d-9ffb-78ab795d2299",
"created" : "2016-08-03T[Link].328+09:00",
"updated" : "2016-08-03T[Link].328+09:00",
"completed" : "2016-08-03T[Link].328+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
You can obtain a list of operations related to email addresses, such as the operation to change the status of an email address.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/MailAddress/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/MailAddress/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "changeStatus",
"href" : "[Link]
ke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "updateTargetNotificationProfile",
"href" : "[Link]
icationProfile/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 2
}
The following operation is the initial step to change the status of specific email addresses to active or suspend.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/MailAddress/actions/changeStatus
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ChangeMailAddressStatusParam
{
"isActive":"...",
"instanceIDs":["...", ...]
}
isActive boolean Whether or not to enable the email address when it is changed. To enable it,
specify "true". To disable it, specify "false".
Attribute Type Description
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/MailAddress/actions/changeStatus
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "changeStatus",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"isActive" : false,
"instanceIDs" : [ ]
} ]
}
You can change the status of specific email addresses to active or suspend.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/MailAddress/actions/changeStatus/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ChangeMailAddressStatusParam
{
"isActive":"...",
"instanceIDs":["...", ...]
}
isActive boolean Whether or not to enable the email address when it is changed. To enable it,
specify "true". To disable it, specify "false".
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/MailAddress/actions/changeStatus/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "changeStatus",
"href": "[Link]
e",
"method": "POST",
"type": "application/json",
"parameters":[{
"isActive":true,
"instanceIDs":[
"mailAddress#cbe211af-4466-4ab3-8707-5a70cc609d3d"
]
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "ad33dc90-db20-4be3-9a68-1894d224116a",
"created" : "2016-08-03T[Link].241+09:00",
"updated" : "2016-08-03T[Link].241+09:00",
"completed" : "2016-08-03T[Link].241+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Performing operations related to notification
profiles
You can create, update, or delete notification profiles. You can also create a notification profile specifying which notifications are
sent to a given email address or obtain a list of categories that can be selected as notification targets.
You can obtain a list of information about notification profiles, such as profile names and notification event levels.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/NotificationProfile
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
NotificationProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"notificationEventLevels":["...", ...],
"useAllCategory":"...",
"notificationCategories":["...", ...],
"mailRecipientType":"..."
}
profileName string Name of the condition profile for the notification condition
(For details about the valid values, see the table EventSeverityType in List of
enumerators.)
useAllCategory boolean Whether or not to use all event categories as notification conditions. To use all
event categories as notification conditions, specify "true". To use only specific
event categories as notification conditions, specify "false".
notificationCategories enum[] Category of the events that can be used in notification conditions. Specify this
item only if useAllCategory is "false".
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
(For details about the valid values, see the table MailRecipientType in List of
enumerators.)
Attribute Type Description
TO
CC
BCC
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/NotificationProfile
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "notificationProfile#ab5ae064-5888-4a51-b397-79adf728666b",
"profileName" : "Profile Name@20160812025527454",
"description" : "description",
"notificationEventLevels" : [ "CRITICAL", "WARNING" ],
"useAllCategory" : false,
"notificationCategories" : [ "PERFORMANCE" ],
"mailRecipientType" : "TO"
} ],
"count" : 1
}
Related reference
List of enumerators
Creating notification profile
You can create a new notification profile by specifying details such as the profile name and notification event level.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/NotificationProfile
Request body
The structure of the request body and the object attributes are as follows:
NotificationProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"notificationEventLevels":["...", ...],
"useAllCategory":"...",
"notificationCategories":["...", ...],
"mailRecipientType":"..."
}
profileName string Name of the condition profile for the notification condition
(For details about the valid values, see the table EventSeverityType in List of
enumerators.)
useAllCategory boolean Whether or not to use all event categories as notification conditions. To use all
event categories as notification conditions, specify "true". To use only specific
event categories as notification conditions, specify "false".
notificationCategories enum[] Category of the events that can be used in notification conditions. Specify this
item only if useAllCategory is "false".
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
(For details about the valid values, see the table MailRecipientType in List of
enumerators.)
Attribute Type Description
TO
CC
BCC
Response body
The structure of the response body and the object attributes is as follows:
NotificationProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"notificationEventLevels":["...", ...],
"useAllCategory":"...",
"notificationCategories":["...", ...],
"mailRecipientType":"..."
}
profileName string Name of the condition profile for the notification condition
(For details about the valid values, see the table EventSeverityType in List of
enumerators.)
useAllCategory boolean Whether or not to use all event categories as notification conditions. To use all
event categories as notification conditions, specify "true". To use only specific
event categories as notification conditions, specify "false".
notificationCategories enum[] Category of the events that can be used in notification conditions. Specify this
item only if useAllCategory is "false".
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
(For details about the valid values, see the table MailRecipientType in List of
enumerators.)
TO
CC
BCC
Status codes
Example code
[Request Header]
POST /Analytics/v1/objects/NotificationProfile
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"profileName":"Profile Name@20160812025526397",
"description":"description",
"notificationEventLevels":["CRITICAL","WARNING"],
"useAllCategory":false,
"notificationCategories":["PERFORMANCE"],
"mailRecipientType":"TO"
}
[Response Header]
HTTP/1.1 201 Created
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "notificationProfile#10cf6ab9-b986-4fd2-9cbf-a3e7d0481337",
"profileName" : "Profile Name@20160812025526397",
"description" : "description",
"notificationEventLevels" : [ "CRITICAL", "WARNING" ],
"useAllCategory" : false,
"notificationCategories" : [ "PERFORMANCE" ],
"mailRecipientType" : "TO"
}
Related reference
List of enumerators
You can obtain information about a specific notification profile, such as the profile name and the notification event level.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/NotificationProfile/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
NotificationProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"notificationEventLevels":["...", ...],
"useAllCategory":"...",
"notificationCategories":["...", ...],
"mailRecipientType":"..."
}
profileName string Name of the condition profile for the notification condition
(For details about the valid values, see the table EventSeverityType in List of
enumerators.)
Attribute Type Description
useAllCategory boolean Whether or not to use all event categories as notification conditions. To use all
event categories as notification conditions, specify "true". To use only specific
event categories as notification conditions, specify "false".
notificationCategories enum[] Category of the events that can be used in notification conditions. Specify this
item only if useAllCategory is "false".
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
(For details about the valid values, see the table MailRecipientType in List of
enumerators.)
TO
CC
BCC
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/NotificationProfile/notificationProfile%23a5911a22-d0ec-4ec4-bff3-b178
b644a342
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "notificationProfile#a5911a22-d0ec-4ec4-bff3-b178b644a342",
"profileName" : "Profile Name@20160812025527839",
"description" : "description",
"notificationEventLevels" : [ "CRITICAL", "WARNING" ],
"useAllCategory" : false,
"notificationCategories" : [ "PERFORMANCE" ],
"mailRecipientType" : "TO"
}
Related reference
List of enumerators
You can update information about a specific notification profile, such as the profile name and the notification event level.
Execution permission
Admin, Modify
Request line
PUT baseURL/v1/objects/NotificationProfile/{id}
Request body
The structure of the request body and the object attributes are as follows:
NotificationProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"notificationEventLevels":["...", ...],
"useAllCategory":"...",
"notificationCategories":["...", ...],
"mailRecipientType":"..."
}
profileName string Name of the condition profile for the notification condition
(For details about the valid values, see the table EventSeverityType in List of
enumerators.)
useAllCategory boolean Whether or not to use all event categories as notification conditions. To use all
event categories as notification conditions, specify "true". To use only specific
event categories as notification conditions, specify "false".
notificationCategories enum[] Category of the events that can be used in notification conditions. Specify this
item only if useAllCategory is "false".
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
(For details about the valid values, see the table MailRecipientType in List of
enumerators.)
TO
CC
BCC
Response body
The structure of the response body and the object attributes is as follows:
NotificationProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"notificationEventLevels":["...", ...],
"useAllCategory":"...",
"notificationCategories":["...", ...],
"mailRecipientType":"..."
}
profileName string Name of the condition profile for the notification condition
(For details about the valid values, see the table EventSeverityType in List of
enumerators.)
Attribute Type Description
useAllCategory boolean Whether or not to use all event categories as notification conditions. To use all
event categories as notification conditions, specify "true". To use only specific
event categories as notification conditions, specify "false".
notificationCategories enum[] Category of the events that can be used in notification conditions. Specify this
item only if useAllCategory is "false".
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
(For details about the valid values, see the table MailRecipientType in List of
enumerators.)
TO
CC
BCC
Status codes
200 OK Success.
Example code
[Request Header]
PUT /Analytics/v1/objects/NotificationProfile/notificationProfile%2326c9fb2f-edb6-457e-b2b6-77a7
802b7d66
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"instanceID":12534479899,
"profileName":"Profile Name@20160812025529388",
"description":"descriptionXXXXXXXXX",
"notificationEventLevels":["CRITICAL","INFO"],
"useAllCategory":false,
"notificationCategories":["SETTING","CHANGE"],
"mailRecipientType":"CC"
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "notificationProfile#26c9fb2f-edb6-457e-b2b6-77a7802b7d66",
"profileName" : "Profile Name@20160812025529388",
"description" : "descriptionXXXXXXXXX",
"notificationEventLevels" : [ "CRITICAL", "INFO" ],
"useAllCategory" : false,
"notificationCategories" : [ "SETTING", "CHANGE" ],
"mailRecipientType" : "CC"
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/NotificationProfile/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
Example code
[Request Header]
DELETE /Analytics/v1/objects/NotificationProfile/notificationProfile%2326c9fb2f-edb6-457e-b2b6-7
7a7802b7d66
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 204 No Content
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
You can obtain a list of operations that can be performed on a specific notification profile.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/NotificationProfile/{id}/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/NotificationProfile/111111/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8810cbc381adf14797b70f0c5a4de1bd9d09ad1_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "updateTargetMailAddress",
"href" : "[Link]
ateTargetMailAddress/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to assign the notification-destination email addresses to a specific notification profile.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/NotificationProfile/{id}/actions/updateTargetMailAddress
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
UpdateTargetMailAddressParam
{
"mailAddressIDs":["...", ...]
}
mailAddressIDs string[] Specify the IDs of all email addresses to be assigned as the destination
addresses. If there are email addresses that have already been assigned, they
are de-assigned by not specifying their IDs. To de-assign all email addresses,
specify an empty list.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/NotificationProfile/notificationProfile%232efedee0-2bab-4560-ada1-8bfe
ab7cfd94/actions/updateTargetMailAddress
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "updateTargetMailAddress",
"href" : "[Link]
232efedee0%2d2bab%2d4560%2dada1%2d8bfeab7cfd94/actions/updateTargetMailAddress/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"mailAddressIDs" : [ ]
} ]
}
You can assign the notification-destination email addresses to a specific notification profile.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/NotificationProfile/{id}/actions/updateTargetMailAddress/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
UpdateTargetMailAddressParam
{
"mailAddressIDs":["...", ...]
}
mailAddressIDs string[] Specify the IDs of all email addresses to be assigned as the destination
addresses. If there are email addresses that have already been assigned, they
Attribute Type Description
are de-assigned by not specifying their IDs. To de-assign all email addresses,
specify an empty list.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Status code Reason phrase Description
Example code
[Request Header]
POST
[Link]
ee0-2bab-4560-ada1-8bfeab7cfd94/actions/updateTargetMailAddress/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "updateTargetMailAddress",
"href": "[Link]
32efedee0%2d2bab%2d4560%2dada1%2d8bfeab7cfd94/actions/updateTargetMailAddress/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"mailAddressIDs":["mailAddress#8610bd0e-d8f1-4a15-8a6f-cd1505cf7b73"]
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "5f41abb9-16bc-4a23-b2c2-c928d4d0e976",
"created" : "2016-08-12T[Link].457+09:00",
"updated" : "2016-08-12T[Link].457+09:00",
"completed" : "2016-08-12T[Link].457+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
You can obtain a list of operations related to notification profile settings, such as the operation to assign a notification-destination
email address.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/NotificationProfile/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/NotificationProfile/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getTargetEventCategory",
"href" : "[Link]
EventCategory/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to obtain a list of notification categories, such as performance and event actions, that
can be used in notification profiles.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/NotificationProfile/actions/getTargetEventCategory
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/NotificationProfile/actions/getTargetEventCategory
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getTargetEventCategory",
"href" : "[Link]
entCategory/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
You can obtain a list of notification categories, such as performance and event actions, that can be used in notification profiles.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/NotificationProfile/actions/getTargetEventCategory/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Response body
The structure of the response body and the object attributes is as follows:
TargetEventCategories
{
"notificationCategories":["...", ...]
}
(For details about the valid values, see the table EventCategoryType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/NotificationProfile/actions/getTargetEventCategory/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getTargetEventCategory",
"href": "[Link]
ntCategory/invoke",
"method": "POST",
"type": "application/json",
"parameters": [ ]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "53516abe-3dba-41e9-af05-66c84ff3ed77",
"created" : "2016-08-12T[Link].970+09:00",
"updated" : "2016-08-12T[Link].970+09:00",
"completed" : "2016-08-12T[Link].970+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"notificationCategories" : [ "PERFORMANCE", "EVENT", "SETTING" ]
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PerfComponents/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
E2EPerfComponent
{
"instanceID":"...",
"componentID":"...",
"componentName":"...",
"metricType":"...",
"metricOrder":"...",
"metricName":"...",
"status":"..."
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
LinkDown
Unknown
NA
NotMonitored
NotCollected
Info
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/PerfComponents/cpu%23ABC_172.17.17.115_host-435%5E0%23ESX_CPU_CPUUSAGE
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "cpu#ABC_172.17.17.115_host-435^0#ESX_CPU_CPUUSAGE",
"componentName" : "",
"metricType" : "ESX_CPU_CPUUSAGE",
"metricOrder" : 3400,
"metricName" : "CPU Usage (VMware Host CPU)",
"status" : "Unknown"
}
Related reference
List of enumerators
You can obtain a list of operations for the metrics for specific resources.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PerfComponents/{id}/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/PerfComponents/b20f2b2b-99dd-4bc6-b585-c63a8ce60168/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getGraphData",
"href" : "[Link]
2db585%2dc63a8ce60168/actions/getGraphData/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to obtain performance graph data for a specific metric.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PerfComponents/{id}/actions/getGraphData
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2EGetGraphDataParam
{
"pointTimeRange":"...",
"baseTime":"...",
"conflict":"...",
"perfComponents":[{
"instanceID":"...",
"nodeType":"...",
"metricType":"..."
},
:
],
"timespan":"...",
"cullTimespan":"..."
}
baseTime dateTime Start time for obtaining performance information. The performance
information for a certain period before the specified start time is
obtained. The period is specified by pointTimeRange. If this item is
omitted, the time that the API was executed is used as the start time.
timespan long Interval (in minutes) of aggregating performance data. This item is
used for calculating the average or worst value in performance
information.
nodeType enum Type of the device that the component, from which performance information is
obtained, belongs to
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
metricType enum Type of the metric from which performance information is obtained
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/PerfComponents/cpu%23ABC_172.17.17.115_host-435%5E0/actions/getGraphDa
ta
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getGraphData",
"href" : "[Link]
ost%2d435%5E0/actions/getGraphData/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"pointTimeRange" : 3600000,
"baseTime" : "2016-07-20T[Link].371+09:00"
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/PerfComponents/{id}/actions/getGraphData/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2EGetGraphDataParam
{
"pointTimeRange":"...",
"baseTime":"...",
"conflict":"...",
"perfComponents":[{
"instanceID":"...",
"nodeType":"...",
"metricType":"..."
},
:
],
"timespan":"...",
"cullTimespan":"..."
}
baseTime dateTime Start time for obtaining performance information. The performance
information for a certain period before the specified start time is
obtained. The period is specified by pointTimeRange. If this item is
omitted, the time that the API was executed is used as the start time.
Attribute Type Description
timespan long Interval (in minutes) of aggregating performance data. This item is
used for calculating the average or worst value in performance
information.
nodeType enum Type of the device that the component, from which performance information is
obtained, belongs to
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
metricType enum Type of the metric from which performance information is obtained
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
E2EPerformanceGraphData
{
"metricType":"...",
"metricName":"...",
"thresholdProfileName":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"proportion":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"...",
"maxValueOfDynamic":"...",
"minValueOfDynamic":"...",
"avgValueOfDynamic":"..."
},
:
],
"monitoringMode":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"fixed":"..."
},
:
],
"minValue":"...",
"maxValue":"...",
"unit":"...",
"currentTime":"...",
"pointValues":[{
"pointValuePeak":"...",
"pointValueAverage":"...",
"pointTime":"..."
},
:
]
}
(For details about the valid values, see the table MetricType in List
of enumerators.)
thresholdProfileName string Name of the threshold profile used to judge the performance
status.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item
is specified only for thresholds of user resources.
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
monitoringMode enum Monitoring status of the plan. This item is specified when the thresholds
are recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List
of enumerators.)
thresholdValueOfWarning float Value of the warning threshold. This item is specified when the
thresholds are recalculated for each component.
Attribute Type Description
thresholdValueOfCritical float Value of the critical threshold. This item is specified when the thresholds
are recalculated for each component.
fixed boolean Specifies whether or not to recalculate the thresholds periodically. If the
thresholds are recalculated periodically, "true" is set. If the thresholds are
not recalculated periodically, "false" is set. This item is specified if the
thresholds are to be recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/PerfComponents/cpu%23ABC_172.17.17.115_host-435%5E0%23ESX_CPU_CPUUSAG
E/actions/getGraphData/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getGraphData",
"href": "[Link]
st%2d435%5E0/actions/getGraphData/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"pointTimeRange":10,
"baseTime":"2016-07-20T[Link].426+09:00"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "da852d65-8b37-41ff-b68a-958d11d756ce",
"created" : "2016-07-20T[Link].567+09:00",
"updated" : "2016-07-20T[Link].481+09:00",
"completed" : "2016-07-20T[Link].481+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"instanceID" : "cpu#ABC_172.17.17.115_host-435^0#ESX_CPU_CPUUSAGE",
"metricType" : "ESX_CPU_CPUUSAGE",
"metricName" : "CPU Usage (VMware Host CPU)",
"thresholdProfileName" : "Default Profile for Hypervisor (VMware)",
"thresholdValueOfWarning" : 75.0,
"thresholdValueOfCritical" : 90.0,
"proportion" : false,
"minValue" : 0.0,
"maxValue" : 99.0,
"unit" : "%",
"currentTime" : "2016-07-20T[Link].426+09:00",
"pointValues" : [ ]
} ]
}
Related reference
List of enumerators
You can obtain a list of operations that can obtain resource performance information.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PerfComponents/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/PerfComponents/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getFromNode",
"href" : "[Link]
voke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to obtain a list of metrics for a specific resource.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PerfComponents/actions/getFromNode
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2ENodeDetailParam
{
"targetNodeID":"...",
"targetNodeType":"..."
}
targetNodeType enum Type of the resources for which details are to be obtained
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/PerfComponents/actions/getFromNode
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getFromNode",
"href" : "[Link]
ke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"targetNodeID" : "0",
"targetNodeType" : "TAG"
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/PerfComponents/actions/getFromNode/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2ENodeDetailParam
{
"targetNodeID":"...",
"targetNodeType":"..."
}
targetNodeType enum Type of the resources for which details are to be obtained
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
E2EPerfComponent
{
"instanceID":"...",
"componentID":"...",
"componentName":"...",
"metricType":"...",
"metricOrder":"...",
"metricName":"...",
"status":"..."
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
LinkDown
Unknown
NA
NotMonitored
NotCollected
Info
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/PerfComponents/actions/getFromNode/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getFromNode",
"href": "[Link]
e",
"method": "POST",
"type": "application/json",
"parameters":[{
"targetNodeID":"vm#ABC_172.17.17.115_vm-449",
"targetNodeType":"CPU"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "b20f2b2b-99dd-4bc6-b585-c63a8ce60168",
"created" : "2016-07-20T[Link].909+09:00",
"updated" : "2016-07-20T[Link].095+09:00",
"completed" : "2016-07-20T[Link].095+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Related reference
List of enumerators
You can obtain a list of metrics for a selected component type, such as STORAGE_CACHE.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PerformanceComponent?$query={HQL}&type={E2ENodeType}&basePointNodeID={nod
eID}&basePointNodeType={E2ENodeType}&pointTimeRange={range}&page={page}&pageSize={size}&baseTime
={dateTime}&conflict={conflict}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
Filtering conditions:
Filtering conditions:
Checks whether the value is included in the comparison target. Multiple values
separated by a comma (,) can be specified.
Filtering conditions:
Filtering conditions:
Filtering conditions:
Parameter Description
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Filtering conditions:
conflict={conflict} (Optional) Specify the method used for calculating the aggregation value ("null" or
"peak" or "average").
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PerformanceComponent
{
"instanceID":"...",
"componentID":"...",
"componentName":"...",
"metricType":"...",
"status":"...",
"parentNodeID":"...",
"parentNodeName":"...",
"clusterName":"...",
"description":"...",
"thresholdProfileName":"...",
"performancePeakLatest":"...",
"performancePeakWorst":"...",
"performanceAverageLatest":"...",
"performanceAverageWorst":"..."
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
LinkDown
Unknown
Attribute Type Description
NA
NotMonitored
NotCollected
Info
performancePeakLatest float Latest peak performance value within the specified period
performancePeakWorst float Peak performance value that is closest to the abnormality line within the
specified period
performanceAverageLatest float Latest average performance value within the specified period
performanceAverageWorst float Average performance value that is closest to the abnormality line within the
specified period
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/PerformanceComponent?%24query=metricType%20eq%20%27RAID_STORAGE_RAIDPO
RT_TRANSFERRATE%27&componentID%20eq%20%27raidPort%23470182-CL7-D%27&type=STORAGE_PORT&basePointN
odeID=raidPort%23470182-CL7-D&basePointNodeType=STORAGE_PORT&pointTimeRange=86400000
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 10 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 3ee59bb16b5aa61a596112ff8f602692d799e75d_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "raidPort#470182-CL7-D#RAID_STORAGE_RAIDPORT_TRANSFERRATE",
"componentID" : "raidPort#470182-CL7-D",
"componentName" : "CL7-D",
"metricType" : "RAID_STORAGE_RAIDPORT_TRANSFERRATE",
"status" : "Unknown",
"parentNodeID" : "raidStorage#470182",
"parentNodeName" : "470182",
"thresholdProfileName" : Default Profile for Volume",
"performancePeakLatest" : 135.0,
"performancePeakWorst" : 416.0,
"performanceAverageLatest" : 135.0,
"performanceAverageWorst" : 416.0
} ],
"count" : 1
}
Related reference
List of enumerators
You can obtain a list of operations related to performance information, such as the operation to obtain performance information.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PerformanceData/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/PerformanceData/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getMetricData",
"href" : "[Link]
a/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "getPerformanceData",
"href" : "[Link]
eData/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 2
}
The following operation is the initial step to obtain performance graph information such as performance data and thresholds.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PerformanceData/actions/getPerformanceData
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2EGetGraphDataParam
{
"pointTimeRange":"...",
"baseTime":"...",
"conflict":"...",
"perfComponents":[{
"instanceID":"...",
"nodeType":"...",
"metricType":"..."
},
:
],
"timespan":"...",
"cullTimespan":"..."
}
baseTime dateTime Start time for obtaining performance information. The performance
information for a certain period before the specified start time is
obtained. The period is specified by pointTimeRange. If this item is
omitted, the time that the API was executed is used as the start time.
timespan long Interval (in minutes) of aggregating performance data. This item is
used for calculating the average or worst value in performance
information.
nodeType enum Type of the device that the component, from which performance information is
obtained, belongs to
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
metricType enum Type of the metric from which performance information is obtained
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/PerformanceData/actions/getPerformanceData
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getPerformanceData",
"href" : "[Link]
ata/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"pointTimeRange" : 3600000,
"baseTime" : "2016-08-12T[Link].819+09:00",
"perfComponents" : [ {
"instanceID" : "",
"nodeType" : "VIRTUAL_MACHINE",
"metricType" : "ESX_VM_VM_CPUREADY"
} ],
"timespan" : 1
} ]
}
Related reference
List of enumerators
You can obtain performance graph information such as performance data and thresholds.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/PerformanceData/actions/getPerformanceData/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
E2EGetGraphDataParam
{
"pointTimeRange":"...",
"baseTime":"...",
"conflict":"...",
"perfComponents":[{
"instanceID":"...",
"nodeType":"...",
"metricType":"..."
},
:
],
"timespan":"...",
"cullTimespan":"..."
}
baseTime dateTime Start time for obtaining performance information. The performance
information for a certain period before the specified start time is
obtained. The period is specified by pointTimeRange. If this item is
omitted, the time that the API was executed is used as the start time.
timespan long Interval (in minutes) of aggregating performance data. This item is
used for calculating the average or worst value in performance
information.
nodeType enum Type of the device that the component, from which performance information is
obtained, belongs to
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
metricType enum Type of the metric from which performance information is obtained
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of Collections objects. For details about Collections, see the table below.
result anyType[]
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
"<componentID>":{
"<metricType>": E2EPerformanceGraphData
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
E2EPerformanceGraphData
{
"metricType":"...",
"metricName":"...",
"thresholdProfileName":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"proportion":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"...",
"maxValueOfDynamic":"...",
"minValueOfDynamic":"...",
"avgValueOfDynamic":"..."
},
:
],
"monitoringMode":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"fixed":"..."
},
:
],
"minValue":"...",
"maxValue":"...",
"unit":"...",
"currentTime":"...",
"pointValues":[{
"pointValuePeak":"...",
"pointValueAverage":"...",
"pointTime":"..."
},
:
]
}
(For details about the valid values, see the table MetricType in List
of enumerators.)
thresholdProfileName string Name of the threshold profile used to judge the performance
status.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item
is specified only for thresholds of user resources.
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
monitoringMode enum Monitoring status of the plan. This item is specified when the thresholds
are recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List
of enumerators.)
thresholdValueOfWarning float Value of the warning threshold. This item is specified when the
thresholds are recalculated for each component.
thresholdValueOfCritical float Value of the critical threshold. This item is specified when the thresholds
are recalculated for each component.
fixed boolean Specifies whether or not to recalculate the thresholds periodically. If the
thresholds are recalculated periodically, "true" is set. If the thresholds are
not recalculated periodically, "false" is set. This item is specified if the
thresholds are to be recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/PerformanceData/actions/getPerformanceData/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getPerformanceData",
"href": "[Link]
Data/invoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"pointTimeRange": 3600000,
"baseTime": "2016-08-22T[Link].971+09:00",
"perfComponents": [
{
"instanceID": "vm#ITPDLab_172.17.17.115_vm-247",
"nodeType": "VIRTUAL_MACHINE",
"metricType": "ESX_VM_VM_CPUREADY"
}
],
"timespan": 1
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 94e91ec387da8fb0c24e41fbaed4106e50b4121_Y2UOI2pkMXQ=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID": "d326a9b0-cd1f-46d6-9e44-b39eda3f0c42",
"created": "2016-08-22T[Link].710+09:00",
"updated": "2016-08-22T[Link].710+09:00",
"completed": "2016-08-22T[Link].710+09:00",
"state": "success",
"affectedResource": [
],
"result": [
{
"data": {
"vm#ITPDLab_172.17.17.115_vm-247": {
"ESX_VM_VM_CPUREADY": {
"instanceID": "vm#ITPDLab_172.17.17.115_vm-247#ESX_VM_VM_CPUREADY",
"metricType": "ESX_VM_VM_CPUREADY",
"metricName": "CPU Ready (VMware Virtual Machine)",
"thresholdProfileName": "Default Profile for VM (VMware)",
"proportion": false,
"plans": [
{
"instanceID": "thPlan#ESX_VM",
"planType": "Base",
"planName": "Base",
"schedule": [
1,
2,
3,
4,
5,
6,
7
],
"from": "00:00",
"to": "24:00",
"priority": 1,
"description": "Base Plan",
"monitoringMode": "Dynamic",
"fixed": false
}
],
"minValue": 0.0,
"maxValue": 1.0,
"unit": "msec",
"currentTime": "2016-08-22T[Link].971+09:00",
"pointValues": [
]
}
}
}
}
]
}
Related reference
List of enumerators
The following operation is the initial step to obtain information related to metrics, such as the display name and unit.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PerformanceData/actions/getMetricData
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
MetricDataParam
{
"resourceType":"...",
"componentType":"...",
"priority":"...",
"metricType":"..."
}
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table MetricPriorityType in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/PerformanceData/actions/getMetricData
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getMetricData",
"href" : "[Link]
nvoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"resourceType" : "ESX_VM",
"componentType" : "VIRTUAL_MACHINE",
"priority" : "Basic",
"metricType" : "ESX_VM_VM_CPUREADY"
} ]
}
Related reference
List of enumerators
You can obtain information related to metrics, such as the display name and unit.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/PerformanceData/actions/getMetricData/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
MetricDataParam
{
"resourceType":"...",
"componentType":"...",
"priority":"..."
}
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table MetricPriorityType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of Collections objects. For details about Collections, see the table below.
result anyType[]
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of MetricType objects. For details about MetricType, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
MetricType
{
"metricType":"...",
"metricName":"...",
"displayOrder":"...",
"unit":"...",
"priority":"...",
"resourceType":"...",
"componentType":"...",
"status":"...",
"proportion":"..."
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table MetricPriorityType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
(For details about the valid values, see the table ComponentType in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
proportion boolean Direction of a perfomrance value. If a warning or critical is generated when the
the value goes up, "true" is set. If a warning or critical is generated when the
value goes down , "false" is set.
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/PerformanceData/actions/getMetricData/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getMetricData",
"href": "[Link]
voke",
"method": "POST",
"type": "application/json",
"parameters":[{
"resourceType":"ESX_VM",
"componentType":"VIRTUAL_MACHINE",
"priority":"Basic",
"metricType":"ESX_VM_VM_CPUREADY"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "df788f95-e53f-48e1-b666-8c6e23fe78c4",
"created" : "2016-08-12T[Link].736+09:00",
"updated" : "2016-08-12T[Link].737+09:00",
"completed" : "2016-08-12T[Link].737+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"data" : [ {
"metricType" : "ESX_VM_VM_CPUREADY",
"metricName" : "CPU Ready (VMware Virtual Machine)",
"displayOrder" : 41700,
"unit" : "msec",
"priority" : "Basic",
"resourceType" : "ESX_VM",
"componentType" : "VIRTUAL_MACHINE",
"status" : "Unknown",
"proportion" : false
} ]
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PerformanceNode?$query={HQL}&type={E2ENodeType}&basePointNodeID={nodeID}&
basePointNodeType={E2ENodeType}&pointTimeRange={range}&page={page}&pageSize={size}&baseTime={dat
eTime}&conflict={conflict}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
Filtering conditions:
Filtering conditions:
Checks whether the value is included in the comparison target. Multiple values
separated by a comma (,) can be specified.
Filtering conditions:
Filtering conditions:
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Filtering conditions:
conflict={conflict} (Optional) Specify the method used for calculating the aggregation value ("null" or
"peak" or "average").
Filtering conditions:
Parameter Description
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PerformanceNode
{
"instanceID":"...",
"componentID":"...",
"componentName":"...",
"metricType":"...",
"status":"...",
"parentNodeID":"...",
"parentNodeName":"...",
"clusterName":"...",
"description":"...",
"thresholdProfileName":"...",
"performancePeakLatest":"...",
"performancePeakWorst":"...",
"performanceAverageLatest":"...",
"performanceAverageWorst":"..."
}
componentID string ID of the component of the device that has performance information
componentName string Name of the component of the device that has performance information
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
LinkDown
Unknown
NA
NotMonitored
NotCollected
Info
performancePeakLatest float Latest peak performance value within the specified period
performancePeakWorst float Peak performance value that is closest to the abnormality line within the
specified period
performanceAverageLatest float Latest average performance value within the specified period
performanceAverageWorst float Average performance value that is closest to the abnormality line within the
specified period
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/PerformanceNode/?%24query=metricType%20eq%20%27ESX_H_MEMUSAGE%27&type=
HYPERVISOR&basePointNodeID=h%23ITPDLab_172.17.17.115_host-190&basePointNodeType=HYPERVISOR&point
TimeRange=86400000
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 10 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 3ee59bb16b5aa61a596112ff8f602692d799e75d_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "h#ITPDLab_172.17.17.115_host-190#HV_ESX_H_MEMUSAGE",
"componentID" : "h#ITPDLab_172.17.17.115_host-190",
"componentName" : "Physical memory : 7.99 GB",
"metricType" : "ESX_H_MEMUSAGE",
"status" : "Warning",
"parentNodeID" : "h#ITPDLab_172.17.17.115_host-190",
"parentNodeName" : "[Link]",
"thresholdProfileName" : "Default Profile for Hypervisor (VMware)",
"performancePeakLatest" : 90.0,
"performancePeakWorst" : 90.0,
"performanceAverageLatest" : 90.0,
"performanceAverageWorst" : 90.0
} ],
"count" : 1
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PerformanceVirtualMachine?$query={HQL}&basePointNodeID={nodeID}&basePoint
NodeType={E2ENodeType}&pointTimeRange={range}&page={page}&pageSize={size}&baseTime={dateTime}&co
nflict={conflict}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
Filtering conditions:
Checks whether the value is included in the comparison target. Multiple values
separated by a comma (,) can be specified.
Parameter Description
Filtering conditions:
Filtering conditions:
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Filtering conditions:
conflict={conflict} (Optional) Specify the method used for calculating the aggregation value ("null" or
"peak" or "average").
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
Collections (Type: Collections)
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PerformanceVirtualMachine
{
"instanceID":"...",
"componentID":"...",
"componentName":"...",
"metricType":"...",
"status":"...",
"parentNodeID":"...",
"parentNodeName":"...",
"hypervisorName":"...",
"clusterName":"...",
"thresholdProfileName":"...",
"performancePeakLatest":"...",
"performancePeakWorst":"...",
"performanceAverageLatest":"...",
"performanceAverageWorst":"..."
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
LinkDown
Unknown
NA
NotMonitored
NotCollected
Info
performancePeakLatest float Latest peak performance value within the specified period
performancePeakWorst float Peak performance value that is closest to the abnormality line within the
specified period
performanceAverageLatest float Latest average performance value within the specified period
performanceAverageWorst float Average performance value that is closest to the abnormality line within the
specified period
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/PerformanceVirtualMachine/?%24query=metricType%20eq%20%27ESX_VM_VM_CPU
READY%27&basePointNodeID=vm%23ABC_172.17.17.115_vm-142&basePointNodeType=STORAGE_VOLUME&pointTim
eRange=86400000
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "vm#ABC_172.17.17.115_vm-142#ESX_VM_VM_CPUREADY",
"componentID" : "vm#ABC_172.17.17.115_vm-142",
"componentName" : "CPU",
"metricType" : "ESX_VM_VM_CPUREADY",
"status" : "Unknown",
"parentNodeID" : "vm#ABC_172.17.17.115_vm-142",
"parentNodeName" : "perf_vm",
"hypervisorName" : "[Link]",
"thresholdProfileName" : "Default Profile for VM (VMware)",
"performancePeakLatest" : 0.0,
"performancePeakWorst" : 0.0,
"performanceAverageLatest" : 0.0,
"performanceAverageWorst" : 0.0
} ],
"count" : 1
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PerformanceVolume?$query={HQL}&basePointNodeID={nodeID}&basePointNodeType
={E2ENodeType}&pointTimeRange={range}&page={page}&pageSize={size}&baseTime={dateTime}&conflict=
{conflict}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
Filtering conditions:
Checks whether the value is included in the comparison target. Multiple values
separated by a comma (,) can be specified.
Filtering conditions:
Filtering conditions:
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Filtering conditions:
conflict={conflict} (Optional) Specify the method used for calculating the aggregation value ("null" or
"peak" or "average").
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PerformanceVolume
{
"instanceID":"...",
"componentID":"...",
"componentName":"...",
"metricType":"...",
"status":"...",
"parentNodeID":"...",
"parentNodeName":"...",
"poolName":"...",
"pgName":"...",
"thresholdProfileName":"...",
"performancePeakLatest":"...",
"performancePeakWorst":"...",
"performanceAverageLatest":"...",
"performanceAverageWorst":"...",
"hostGroupIDs":["...", ...],
"hostGroupNames":["...", ...],
"vssbComputeNodeNames":["...", ...],
"nvmHostNicknames":["...", ...],
"lunOwnerIDs":["...", ...],
"lunOwnerNames":["...", ...]
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
LinkDown
Unknown
NA
NotMonitored
NotCollected
Info
performancePeakLatest float Latest peak performance value within the specified period.
performancePeakWorst float Peak performance value that is closest to the abnormality line within the
specified period.
performanceAverageLatest float Latest average performance value within the specified period.
performanceAverageWorst float Average performance value that is closest to the abnormality line within the
specified period.
hostGroupNames string[] Name of the host group that a volume belongs to.
lunOwnerNames string[] Name of the LUN Owner that a volume is associated with.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/PerformanceVolume?%24query=metricType%20eq%20%27RAID_VOLUME_RAIDLDEV_T
OTALIOPS%27&basePointNodeID=raidLdev%2310000-00%5E00%5E63&basePointNodeType=STORAGE_VOLUME&point
TimeRange=86400000
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 10 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 4f5dd90606cb15e3c72928995be8eb650f2de69_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "raidLdev#10000-00^00^63#RAID_VOLUME_RAIDLDEV_TOTALIOPS",
"componentID" : "raidLdev#10000-00^00^63",
"componentName" : "[Link]",
"metricType" : "RAID_VOLUME_RAIDLDEV_TOTALIOPS",
"status" : "Normal",
"parentNodeID" : "raidStorage#10000",
"parentNodeName" : "VSP 5500H (10000)",
"label" : "BasicVol_00099",
"pgName" : "01-29",
"thresholdProfileName" : "Default Profile for Volume",
"performancePeakLatest" : 154.0,
"performancePeakWorst" : 741.0,
"performanceAverageLatest" : 154.0,
"performanceAverageWorst" : 741.0 } ],
"count" : 1
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictionHistory
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
Attribute Type Description
count int Number of data items that meet the conditions related to this query(API).
PredictionHistory
{
"name":"...",
"description":"...",
"reportID":"...",
"userName":"...",
"execState":"...",
"execDate":,
"status":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
},
"numOfTargets":"...",
"lastActionDate":,
"errorMessage":"...",
"metricResults":[{
"metricType":"...",
"metricName":"...",
"nodeType":"...",
"componentType":"...",
"nodeName":"...",
"execState":"...",
"status":"...",
"numOfTargets":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
}
},
:
],
"profileResults":[{
"profileID":"...",
"profileName":"...",
"metricResults":[{
"metricType":"...",
"metricName":"...",
"nodeType":"...",
"componentType":"...",
"nodeName":"...",
"execState":"...",
"status":"...",
"numOfTargets":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
}
},
:
]
},
:
],
"profileID":"..."
}
userName string Name of the user associated with the executed predictive operation.
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
execDate datetime Date and time when this task started executing.
status enum Aggregated status of all the performance resources for the predictive
report result.
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
Normal
Warning
Critical
Attribute Type Description
Unknown
NA
lastActionDate datetime Date and time when the last action executed.
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List
of enumerators.)
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List
of enumerators.)
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
You can obtain historical information for the results of a predictive operation.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictionHistory/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
PredictionHistory
{
"name":"...",
"description":"...",
"reportID":"...",
"userName":"...",
"execState":"...",
"execDate":,
"status":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
},
"numOfTargets":"...",
"lastActionDate":,
"errorMessage":"...",
"metricResults":[{
"metricType":"...",
"metricName":"...",
"nodeType":"...",
"componentType":"...",
"nodeName":"...",
"execState":"...",
"status":"...",
"numOfTargets":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
}
},
:
],
"profileResults":[{
"profileID":"...",
"profileName":"...",
"metricResults":[{
"metricType":"...",
"metricName":"...",
"nodeType":"...",
"componentType":"...",
"nodeName":"...",
"execState":"...",
"status":"...",
"numOfTargets":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
}
},
:
]
},
:
],
"profileID":"..."
}
userName string Name of the user associated with the executed predictive operation.
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
execDate datetime Date and time when this task started executing.
status enum Aggregated status of all the performance resources for the predictive
report result.
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
Normal
Warning
Critical
Unknown
NA
lastActionDate datetime Date and time when the last action executed.
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List
of enumerators.)
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List
of enumerators.)
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Deleting a predictive history
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/PredictionHistory/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PredictionHistory/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
The following operation is the initial step to get information for predictive results.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PredictionHistory/actions/getResult
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetPredictionResultParam
{
"historyID":"...",
"targetIDs":"...",
"cullTimespan":"...",
"rangeFrom":"...",
"rangeTo":"...",
"onlyModelData":"..."
}
onlyModelData boolean Whether the response will have performance data and predictive report results.
Status codes
200 OK Success.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/PredictionHistory/actions/getResult/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetPredictionResultParam
{
"historyID":"...",
"targetIDs":"...",
"cullTimespan":"...",
"rangeFrom":"...",
"rangeTo":"...",
"onlyModelData":"..."
}
onlyModelData boolean Whether the response will have performance data and predictive report results.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of Collections objects. For details about Collections, see the table below.
result anyType[]
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PredictionTargetResult
{
"originalData":{
"metricType":"...",
"metricName":"...",
"thresholdProfileName":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"proportion":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"...",
"maxValueOfDynamic":"...",
"minValueOfDynamic":"...",
"avgValueOfDynamic":"..."
},
:
],
"monitoringMode":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"fixed":"..."
},
:
],
"minValue":"...",
"maxValue":"...",
"unit":"...",
"currentTime":"...",
"pointValues":[{
"pointValuePeak":"...",
"pointValueAverage":"...",
"pointTime":"..."
},
:
]
},
"resultData":[{
"label":"...",
"description":"...",
"resultType":"...",
"data":{
"metricType":"...",
"metricName":"...",
"thresholdProfileName":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"proportion":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"...",
"maxValueOfDynamic":"...",
"minValueOfDynamic":"...",
"avgValueOfDynamic":"..."
},
:
],
"monitoringMode":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"fixed":"..."
},
:
],
"minValue":"...",
"maxValue":"...",
"unit":"...",
"currentTime":"...",
"pointValues":[{
"pointValuePeak":"...",
"pointValueAverage":"...",
"pointTime":"..."
},
:
]
},
"thresholdScore":"...",
"thresholdAlertDate":,
"status":"..."
},
:
],
"execState":"...",
"errorMessage":"...",
"model":{
"instanceID":"...",
"componentID":"...",
"componentName":"...",
"label":"...",
"metricType":"...",
"status":"...",
"predictionStatus":"...",
"parentNodeID":"...",
"parentNodeName":"...",
"hypervisorName":"...",
"clusterName":"...",
"thresholdProfileName":"...",
"poolName":"...",
"pgName":"...",
"nvmHostNicknames":["...", ...],
"hostGroupIDs":["...", ...],
"hostGroupNames":["...", ...],
"realPerformanceLatest":"...",
"realPerformanceWorst":"...",
"predictionPerformanceWorst":"...",
"firstAlertDate":
}
}
(For details about the valid values, see the table PredictionExecState
in List of enumerators.)
(For details about the valid values, see the table MetricType in List
of enumerators.)
thresholdProfileName string Name of the threshold profile used to judge the performance
status.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item
is specified only for thresholds of user resources.
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
Attribute Type Description
monitoringMode enum Monitoring status of the plan. This item is specified when the thresholds
are recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List
of enumerators.)
thresholdValueOfWarning float Value of the warning threshold. This item is specified when the
thresholds are recalculated for each component.
thresholdValueOfCritical float Value of the critical threshold. This item is specified when the thresholds
are recalculated for each component.
fixed boolean Specifies whether or not to recalculate the thresholds periodically. If the
thresholds are recalculated periodically, "true" is set. If the thresholds are
not recalculated periodically, "false" is set. This item is specified if the
thresholds are to be recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
(For details about the valid values, see the table ElementStatusType
in List of enumerators.)
Normal
Warning
Critical
NA
(For details about the valid values, see the table MetricType in List
of enumerators.)
thresholdProfileName string Name of the threshold profile used to judge the performance
status.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item
is specified only for thresholds of user resources.
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
monitoringMode enum Monitoring status of the plan. This item is specified when the thresholds
are recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List
of enumerators.)
thresholdValueOfWarning float Value of the warning threshold. This item is specified when the
thresholds are recalculated for each component.
Attribute Type Description
thresholdValueOfCritical float Value of the critical threshold. This item is specified when the thresholds
are recalculated for each component.
fixed boolean Specifies whether or not to recalculate the thresholds periodically. If the
thresholds are recalculated periodically, "true" is set. If the thresholds are
not recalculated periodically, "false" is set. This item is specified if the
thresholds are to be recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
LinkDown
Unknown
NA
NotMonitored
NotCollected
Info
Attribute Type Description
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
NA
hostGroupNames string[] Name of the host group that a volume belongs to.
firstAlertDate datetime First date and time when the performance value exceeds the threshold.
Status codes
200 OK Success.
Status code Reason phrase Description
Related reference
List of enumerators
Getting the parameter used to get metrics for the predictive result
The following operation performs the initial step to get metrics for a predictive result.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PredictionHistory/actions/getTargets
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
PredictionHistory
{
"name":"...",
"description":"...",
"reportID":"...",
"userName":"...",
"execState":"...",
"execDate":,
"status":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
},
"numOfTargets":"...",
"lastActionDate":,
"errorMessage":"...",
"metricResults":[{
"metricType":"...",
"metricName":"...",
"nodeType":"...",
"componentType":"...",
"nodeName":"...",
"execState":"...",
"status":"...",
"numOfTargets":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
}
},
:
],
"profileResults":[{
"profileID":"...",
"profileName":"...",
"metricResults":[{
"metricType":"...",
"metricName":"...",
"nodeType":"...",
"componentType":"...",
"nodeName":"...",
"execState":"...",
"status":"...",
"numOfTargets":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
}
},
:
]
},
:
],
"profileID":"..."
}
userName string Name of the user associated with the executed predictive operation.
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
execDate datetime Date and time when this task started executing.
status enum Aggregated status of all the performance resources for the predictive
report result.
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
Normal
Warning
Critical
Unknown
NA
lastActionDate datetime Date and time when the last action executed.
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List
of enumerators.)
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
Attribute Type Description
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List
of enumerators.)
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
Status codes
Status code Reason phrase Description
200 OK Success.
Related reference
List of enumerators
You can get the metrics associated with results of a predictive operation.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/PredictionHistory/actions/getTargets/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
PredictionTargetMetric
{
"metricType":"...",
"metricName":"...",
"nodeType":"...",
"componentType":"...",
"nodeName":"...",
"execState":"...",
"status":"...",
"numOfTargets":"...",
"statusDetail":{
"numOfCriticals":"...",
"numOfWarnings":"...",
"numOfNormals":"...",
"numOfUnknowns":"...",
"numOfNAs":"..."
}
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table ComponentType in List
of enumerators.)
(For details about the valid values, see the table PredictionExecState in
List of enumerators.)
(For details about the valid values, see the table ElementStatusType in
List of enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of Collections objects. For details about Collections, see the table below.
result anyType[]
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PredictionTarget
{
"execState":"...",
"status":"...",
"firstAlertDate":
}
(For details about the valid values, see the table PredictionExecState in List of
enumerators.)
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
firstAlertDate datetime Estimated date and time when the value exceeds or falls below the threshold.
Status codes
200 OK Success.
Related reference
List of enumerators
Getting the license status of the Predictive
Analytics feature
You can obtain the license status of the Predictive Analytics feature that is applicable for any monitored resource in Ops Center
Analyzer.
You can obtain the status (enable or not) of the Predictive Analytics feature.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictionLicense
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PredictionLicense
{
"enable":"..."
}
Status codes
200 OK Success.
Admin, Modify
Request line
GET baseURL/v1/objects/PredictionModule
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PredictionModule
{
"label":"...",
"description":"...",
"predictionTypes":[{
"label":"...",
"description":"...",
"selected":"..."
},
:
],
"params":[{
"label":"...",
"description":"...",
"type":"...",
"required":"...",
"defaultValue":,
"rangeMin":,
"rangeMax":,
"selectionItems":[{
"label":"...",
"description":"...",
"selected":"..."
},
:
],
"multiSelection":"..."
},
:
]
}
Status codes
200 OK Success.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictionModule/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
PredictionModule
{
"label":"...",
"description":"...",
"predictionTypes":[{
"label":"...",
"description":"...",
"selected":"..."
},
:
],
"params":[{
"label":"...",
"description":"...",
"type":"...",
"required":"...",
"defaultValue":,
"rangeMin":,
"rangeMax":,
"selectionItems":[{
"label":"...",
"description":"...",
"selected":"..."
},
:
],
"multiSelection":"..."
},
:
]
}
Status codes
200 OK Success.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictionTask
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of PredictionTask objects. For details about PredictionTask, see the table
data anyType[]
below.
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PredictionTask
{
"name":"...",
"taskState":"..."
}
(For details about the valid values, see the table PredictionExecState in List of
enumerators.)
Status codes
Status code Reason phrase Description
200 OK Success.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictionTask/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
PredictionTask
{
"name":"...",
"taskState":"..."
}
(For details about the valid values, see the table PredictionExecState in List of
enumerators.)
Status codes
Status code Reason phrase Description
200 OK Success.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PredictionTask/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
Attribute Type Description
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Status code Reason phrase Description
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PredictionTask/actions/execute
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
{
"reportID":"...",
"profileIDs":["...", ...],
"targetConds":[{
"nodeType":"...",
"resourceIDs":["...", ...],
"withRelated":"..."
},
:
],
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"withRelated":"...",
"predictionPeriod":"...",
"calculationPeriod":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
withRelated boolean Indicates whether the related resource is the same as the target.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Predicting a result
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/PredictionTask/actions/execute/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
PredictionExecParam
{
"reportID":"...",
"profileIDs":["...", ...],
"targetConds":[{
"nodeType":"...",
"resourceIDs":["...", ...],
"withRelated":"..."
},
:
],
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"withRelated":"...",
"predictionPeriod":"...",
"calculationPeriod":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
withRelated boolean Indicates whether the related resource is the same as the target.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of PredictionTask objects. For details about PredictionTask, see the table
result anyType[]
below.
PredictionTask
{
"name":"...",
"taskState":"..."
}
(For details about the valid values, see the table PredictionExecState in List of
enumerators.)
Status codes
Status code Reason phrase Description
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/PredictionTask/actions/cancel
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
PredictionTask
{
"name":"...",
"taskState":"..."
}
(For details about the valid values, see the table PredictionExecState in List of
enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/PredictionTask/actions/cancel/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
PredictionTask
{
"name":"...",
"taskState":"..."
}
(For details about the valid values, see the table PredictionExecState in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of PredictionTask objects. For details about PredictionTask, see the table
result anyType[]
below.
PredictionTask
{
"name":"...",
"taskState":"..."
}
(For details about the valid values, see the table PredictionExecState in List of
enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictiveProfile
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Attribute Type Description
Status codes
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/PredictiveProfile
Request body
The structure of the request body and the object attributes are as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
Attribute Type Description
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
Related reference
List of enumerators
Getting information about a predictive profile
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictiveProfile/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
PUT baseURL/v1/objects/PredictiveProfile/{id}
Request body
The structure of the request body and the object attributes are as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
PredictiveProfile (Type: PredictiveProfile)
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/PredictiveProfile/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictiveReport
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PredictiveReport
{
"name":"...",
"description":"...",
"profileIDs":["...", ...],
"targets":[{
"nodeType":"...",
"resourceIDs":["...", ...],
"withRelated":"..."
},
:
],
"withRelated":"...",
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"actionIDs":,
"lastHistoryID":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this report was created for an ad hoc execution.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
withRelated boolean Indicates whether the related resource is the same as the target.
Status codes
200 OK Success.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/PredictiveReport
Request body
The structure of the request body and the object attributes are as follows:
PredictiveReport
{
"name":"...",
"description":"...",
"profileIDs":["...", ...],
"targets":[{
"nodeType":"...",
"resourceIDs":["...", ...],
"withRelated":"..."
},
:
],
"withRelated":"...",
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"actionIDs":,
"lastHistoryID":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this report was created for an ad hoc execution.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
withRelated boolean Indicates whether the related resource is the same as the target.
Response body
The structure of the response body and the object attributes is as follows:
PredictiveReport
{
"name":"...",
"description":"...",
"profileIDs":["...", ...],
"targets":[{
"nodeType":"...",
"resourceIDs":["...", ...],
"withRelated":"..."
},
:
],
"withRelated":"...",
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"actionIDs":,
"lastHistoryID":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this report was created for an ad hoc execution.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
withRelated boolean Indicates whether the related resource is the same as the target.
Status codes
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/PredictiveReport/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
PredictiveReport
{
"name":"...",
"description":"...",
"profileIDs":["...", ...],
"targets":[{
"nodeType":"...",
"resourceIDs":["...", ...],
"withRelated":"..."
},
:
],
"withRelated":"...",
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"actionIDs":,
"lastHistoryID":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this report was created for an ad hoc execution.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
withRelated boolean Indicates whether the related resource is the same as the target.
Status codes
Status code Reason phrase Description
200 OK Success.
Execution permission
Admin, Modify
Request line
PUT baseURL/v1/objects/PredictiveReport/{id}
Request body
The structure of the request body and the object attributes are as follows:
PredictiveReport
{
"name":"...",
"description":"...",
"profileIDs":["...", ...],
"targets":[{
"nodeType":"...",
"resourceIDs":["...", ...],
"withRelated":"..."
},
:
],
"withRelated":"...",
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"actionIDs":,
"lastHistoryID":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this report was created for an ad hoc execution.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
withRelated boolean Indicates whether the related resource is the same as the target.
Response body
The structure of the response body and the object attributes is as follows:
PredictiveReport
{
"name":"...",
"description":"...",
"profileIDs":["...", ...],
"targets":[{
"nodeType":"...",
"resourceIDs":["...", ...],
"withRelated":"..."
},
:
],
"withRelated":"...",
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"actionIDs":,
"lastHistoryID":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this report was created for an ad hoc execution.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
withRelated boolean Indicates whether the related resource is the same as the target.
Status codes
200 OK Success.
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/PredictiveReport/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/RecoveryActionHistory
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/RecoveryAction
Request body
The structure of the request body and the object attributes are as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
Attribute Type Description
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
Related reference
List of enumerators
Getting information about recovery action history
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/RecoveryAction/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
PUT baseURL/v1/objects/RecoveryAction/{id}
Request body
The structure of the request body and the object attributes are as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
PredictiveProfile
{
"name":"...",
"description":"...",
"predictionPeriod":"...",
"calculationPeriod":"...",
"dataInterval":"...",
"metrics":[{
"metricType":"...",
"threshold":"...",
"proportion":"..."
},
:
],
"moduleID":"...",
"predictionTypes":["...", ...],
"withRelated":"...",
"params":[{
"value":,
"items":["...", ...]
},
:
],
"owner":"...",
"lastUpdated":,
"systemDefined":"...",
"isOndemand":"...",
"numOfReports":"..."
}
PredictiveProfile (Type: PredictiveProfile)
withRelated boolean Whether or not the related resources are included in the targets.
isOndemand boolean Whether or not this profile was created for an ad hoc execution.
(For details about the valid values, see the table MetricType in List of
enumerators.)
Status codes
200 OK Success.
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/RecoveryAction/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
You can obtain a list of storage system models that Ops Center Analyzer is monitoring.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/StorageSystemModels
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
Collections (Type: Collections)
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
StorageSystemModel
{
"modelID":"...",
"modelName":"...",
"profileResourceType":"..."
}
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
Status codes
Status code Reason phrase Description
Example code
[Request Header]
GET /Analytics/v1/objects/StorageSystemModels
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 3a9b57bff1fdbc16e83ca7fd4a2a9f6a7d542d_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"modelID" : "VSP 5500H",
"modelName" : "Hitachi - VSP 5500H",
"profileResourceType" : "RAID_STORAGE"
} ],
"count" : 1
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/StorageSystemPools
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
StorageSystemPool
{
"poolName":"...",
"poolID":"...",
"storageSystemID":"...",
"storageSystemName":"...",
"poolType":"...",
"volumeLocation":["...", ...],
"driveType":["...", ...],
"raidLevel":["...", ...]
}
storageSystemName string Name of the storage system that the pool belongs to
(For details about the valid values, see the table E2EPoolType in List of
enumerators.)
volumeLocation enum[] Location of the storage system in which the volume is created
(For details about the valid values, see the table VolumeLocation in List of
enumerators.)
(For details about the valid values, see the table E2EDriveType in List of
enumerators.)
Status codes
Example code
[Request Header]
GET /Analytics/v1/objects/StorageSystemPools
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 3a9b57bff1fdbc16e83ca7fd4a2a9f6a7d542d_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "raidPool#10000-8",
"poolName" : "8",
"poolID" : "8",
"storageSystemID" : "raidStorage#10000",
"storageSystemName" : "VSP 5500H (10000)",
"poolType" : "HDP",
"volumeLocation" : [ "INTERNAL" ],
"driveType" : [ ],
"raidLevel" : [ "RAID5 (3D+1P)" ]
}, {
"instanceID" : "raidPool#10000-9",
"poolName" : "9",
"poolID" : "9",
"storageSystemID" : "raidStorage#10000",
"storageSystemName" : "VSP 5500H (10000)",
"poolType" : "HDP",
"volumeLocation" : [ "INTERNAL" ],
"driveType" : [ ],
"raidLevel" : [ "RAID5 (3D+1P)" ]
........ } ],
"count" : 2
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/Suggestion/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/Suggestion/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 23 Jan 2017 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO f61a9fad64f2451def69ea9ea934d9b3be5f2f87_UQV8dA9cIGw=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getSuggestion",
"href" : "[Link]
ke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to obtain recovery plans for resolving performance problems.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/Suggestion/actions/getSuggestion
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Suggestion
{
"resourceType":"...",
"resourceID":"...",
"alertTime":"...",
"startTime":"...",
"endTime":"...",
"metricType":"...",
"target":"...",
"checkConsumer":"...",
"planRecords":[{
"planID":"...",
"contentID":"...",
"title":"...",
"planActionType":"...",
"summary":"...",
"actions":[{
"actionIdNum":"...",
"summary":"...",
"steps":["...", ...]
},
:
],
"evaluation":{
"evaluationIdNum":"...",
"certainty":{
"level":"...",
"details":"..."
},
"expectedFinishTime":{
"timeValue":"...",
"unit":"...",
"qualifier":"...",
"annotation":"..."
},
"sideEffects":[{
"possibleImpact":"...",
"resourceData":{
"name":"...",
"e2eViewParam":{
"basePointNodeID":["...", ...],
"basePointNodeType":"..."
}
}
},
:
],
"undoability":{
"level":"...",
"conditions":["...", ...]
}
},
"remarks":"..."
},
:
]
}
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
actions SuggestionAction[] Information about the methods used to implement the plan
undoability Undoability Information about the evaluation of whether the plan can do rollback
(For details about the valid values, see the table CertaintyLevel in List of
enumerators.)
details string Details about factors that lower the probability of success
(For details about the valid values, see the table TimeUnit in List of
enumerators.)
Attribute Type Description
(For details about the valid values, see the table Qualifier in List of
enumerators.)
e2eViewParam E2EViewParam Information about the resource IDs for the resources affected by the impact
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table UndoabilityLevel in List of
enumerators.)
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/Suggestion/actions/getSuggestion
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 23 Jan 2017 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 384d86cd8397edfd44e093e28ff2dcf1b563e471_UQV8dA9cIGw=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getSuggestion",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"resourceType" : "STORAGE_VOLUME",
"resourceID" : "ID of bottleneck resource",
"alertTime" : "2017-01-23T[Link].355+09:00",
"startTime" : "2017-01-23T[Link].355+09:00",
"endTime" : "2017-01-23T[Link].355+09:00",
"metricType" : "RAID_VOLUME_RAIDLDEV_TOTALIOPS",
"target" : 30.0,
"checkConsumer" : false
} ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/Suggestion/actions/getSuggestion/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Suggestion
{
"resourceType":"...",
"resourceID":"...",
"alertTime":"...",
"startTime":"...",
"endTime":"...",
"metricType":"...",
"target":"...",
"checkConsumer":"..."
}
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
A list of Suggestion objects. For details about Suggestion, see the table below.
result anyType[]
Suggestion
{
"resourceType":"...",
"resourceID":"...",
"alertTime":"...",
"startTime":"...",
"endTime":"...",
"metricType":"...",
"target":"...",
"checkConsumer":"...",
"planRecords":[{
"planID":"...",
"contentID":"...",
"title":"...",
"planActionType":"...",
"summary":"...",
"actions":[{
"actionIdNum":"...",
"summary":"...",
"steps":["...", ...]
},
:
],
"evaluation":{
"evaluationIdNum":"...",
"certainty":{
"level":"...",
"details":"..."
},
"expectedFinishTime":{
"timeValue":"...",
"unit":"...",
"qualifier":"...",
"annotation":"..."
},
"sideEffects":[{
"possibleImpact":"...",
"resourceData":{
"name":"...",
"e2eViewParam":{
"basePointNodeID":["...", ...],
"basePointNodeType":"..."
}
}
},
:
],
"undoability":{
"level":"...",
"conditions":["...", ...]
}
},
"remarks":"..."
},
:
]
}
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
actions SuggestionAction[] Information about the methods used to implement the plan
undoability Undoability Information about the evaluation of whether the plan can do rollback
(For details about the valid values, see the table CertaintyLevel in List of
enumerators.)
details string Details about factors that lower the probability of success
(For details about the valid values, see the table TimeUnit in List of
enumerators.)
(For details about the valid values, see the table Qualifier in List of
enumerators.)
e2eViewParam E2EViewParam Information about the resource IDs for the resources affected by the impact
basePointNodeID string[] ID of the base resource. Multiple IDs can be specified if the resources are of the
same type.
Attribute Type Description
(For details about the valid values, see the table E2ENodeType in List of
enumerators.)
(For details about the valid values, see the table UndoabilityLevel in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/Suggestion/actions/getSuggestion/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name" : "getSuggestion",
"href" : "[Link]
e",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"resourceType" : "STORAGE_MP",
"resourceID" : "raidMPB#53038-MPB-2MC",
"alertTime" : "2017-01-23T[Link].258+09:00",
"startTime" : "2017-01-23T[Link].258+09:00",
"endTime" : "2017-01-23T[Link].258+09:00",
"metricType" : "RAID_STORAGE_RAIDMPB_UTILIZATION",
"target" : 30.0,
"checkConsumer" : false
} ]
}
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 23 Jan 2017 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 42e4c1b3a553126bd3fabc3bebd4ceaa67719af_ZAlDR1YdfRJUBwFo_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "c158def9-48ab-4ad8-bb82-598965b60d0f",
"created" : "2017-01-23T[Link].326+09:00",
"updated" : "2017-01-23T[Link].327+09:00",
"completed" : "2017-01-23T[Link].327+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"resourceType" : "STORAGE_MP",
"resourceID" : "raidMPB#53038-MPB-2MC",
"alertTime" : "2016-12-01T[Link].033+09:00",
"startTime" : "2016-12-01T[Link].033+09:00",
"endTime" : "2016-12-20T[Link].033+09:00",
"metricType" : "RAID_STORAGE_RAIDMPB_UTILIZATION",
"target" : 30.0,
"checkConsumer" : false,
"planRecords" : [ ]
} ]
}
Related reference
List of enumerators
You can obtain information about system settings, such as the time zone and locale.
Execution permission
GET baseURL/v1/objects/SystemProperties
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
SystemProperty
{
"type":"...",
"value":"..."
}
SystemProperty (Type: SystemProperty)
(For details about the valid values, see the table SystemPropertyType in List of
enumerators.)
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/SystemProperties
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a61560c2eac97b0564aec48d2883daf39c0dfdf_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V081
0
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"type" : "GroupDescriptionTemplate",
"value" : "Company:\r\nSystem: \r\nTel:\r\nAddress:\r\nContact Person:\
}, {
"type" : "SystemTimeZone",
"value" : "Asia/Tokyo"
}, {
...........
} ],
"count" : 13
}
Related reference
List of enumerators
You can obtain a list of operations that retrieve system summary information (status summaries of consumers and user
resources).
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/SystemSummary/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
Attribute Type Description
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Status code Reason phrase Description
Example code
[Request Header]
GET /Analytics/v1/services/SystemSummary/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 3a9b57bff1fdbc16e83ca7fd4a2a9f6a7d542d_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getSystemStatusSummary",
"href" : "[Link]
Summary/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
The following operation is the initial step to retrieve system summary information (status summaries of consumers and user
resources).
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/SystemSummary/actions/getSystemStatusSummary
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/SystemSummary/actions/getSystemStatusSummary
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 3a9b57bff1fdbc16e83ca7fd4a2a9f6a7d542d_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getSystemStatusSummary",
"href" : "[Link]
mmary/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
You can obtain system summary information (summaries of the status of consumers and user resources).
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/SystemSummary/actions/getSystemStatusSummary/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
GetSystemStatusSummary
{
"status":"...",
"statusMessage":"...",
"messageHighlightParams":["...", ...],
"groupSummaries":[{
"key":"...",
"name":"...",
"critical":"...",
"warning":"...",
"total":"..."
},
:
],
"vmSummary":{
"key":"...",
"name":"...",
"critical":"...",
"warning":"...",
"total":"..."
},
"hostSummary":{
"key":"...",
"name":"...",
"critical":"...",
"warning":"...",
"total":"..."
},
"volumeSummary":{
"key":"...",
"name":"...",
"critical":"...",
"warning":"...",
"total":"..."
}
}
status enum Most severe one of the statuses in the entire system
(For details about the valid values, see the table SystemSummaryStatus in
List of enumerators.)
CRITICAL
WARNING
NORMAL
INFORMATION
statusMessage string Message indicating the status of the entire system. The specified
message might include variables. Each variable is specified in {n} format,
where "n" is an argument sequence number that is 0 or a larger integer.
(Example: Status is {0}.)
messageHighlightParams string[] Variables used in a message that indicates the status of the entire system.
The specified variables are set in the message in the order they are
specified. (Example: Critical)
key string Key used for aggregation. This item is set only if the category is Consumer.
name string Name of the category used for aggregation. This item is set only if the category
is Consumer.
key string Key used for aggregation. This item is set only if the category is Consumer.
name string Name of the category used for aggregation. This item is set only if the category
is Consumer.
key string Key used for aggregation. This item is set only if the category is Consumer.
Attribute Type Description
name string Name of the category used for aggregation. This item is set only if the category
is Consumer.
key string Key used for aggregation. This item is set only if the category is Consumer.
name string Name of the category used for aggregation. This item is set only if the category
is Consumer.
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/SystemSummary/actions/getSystemStatusSummary/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getSystemStatusSummary",
"href": "[Link]
mary/invoke",
"method": "POST",
"type": "application/json",
"parameters":[]
}
[Response Header]
HTTP/1.1 200 OK
Date: Fri, 12 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 3a9b57bff1fdbc16e83ca7fd4a2a9f6a7d542d_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "61a0f99c-c0ce-44e2-b1dd-0241b00
"created" : "2016-08-12T[Link].628+09:00",
"updated" : "2016-08-12T[Link].628+09:00",
"completed" : "2016-08-12T[Link].628+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"status" : "NORMAL",
"statusMessage" : "The system is normal",
"messageHighlightParams" : [ ],
"groupSummaries" : [ {
"key" : "grade#Platinum",
"name" : "Platinum",
"critical" : 0,
"warning" : 0,
"total" : 0
}, {
"key" : "grade#Gold",
"name" : "Gold",
"critical" : 0,
"warning" : 0,
"total" : 0
}, {
"key" : "grade#Silver",
"name" : "Silver",
"critical" : 0,
"warning" : 0,
"total" : 0
}, {
"key" : "grade#Bronze",
"name" : "Bronze",
"critical" : 0,
"warning" : 0,
"total" : 0
} ],
"vmSummary" : {
"critical" : 0,
"warning" : 0,
"total" : 59
},
"hostSummary" : {
"critical" : 0,
"warning" : 0,
"total" : 0
},
"volumeSummary" : {
"critical" : 0,
"warning" : 0,
"total" : 1570
}
} ]
}
Related reference
List of enumerators
You can obtain a list of the types of margins used for dynamic threshold calculations and display names.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ThresholdProfileMargins
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
ThresholdMarginInfo
{
"marginLevel":"...",
"marginName":"...",
"isDefault":"..."
}
isDefault boolean Whether or not the margin is used as an initial value. If the margin is used as an
initial value, "true" is set. If the margin is not used as an initial value, "false" is
set.
Status codes
200 OK Success.
Example code
[Request Header]
GET
[Link]
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"marginLevel" : "Severe",
"marginName" : "Severe"
}, {
"marginLevel" : "Normal",
"marginName" : "Normal",
"isDefault" : true
}, {
"marginLevel" : "Rough",
"marginName" : "Rough"
} ],
"count" : 3
}
You can obtain a list of information about threshold profiles, such as the profile names and thresholds.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ThresholdProfiles
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
ThresholdProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"resourceType":"...",
"profileType":"...",
"profileResourceType":"...",
"representativeProfileId":"...",
"isRepresentativeProfile":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoring":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"..."
},
:
],
"margin":"...",
"marginName":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"...",
"maxValueOfDynamic":"...",
"minValueOfDynamic":"...",
"avgValueOfDynamic":"..."
},
:
],
"monitoringMode":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"fixed":"..."
},
:
],
"numOfResources":"...",
"autoAssignFilters":["...", ...]
}
(For details about the valid values, see the table PerfThresholdResourceType
in List of enumerators.)
User
System
Reserve
profileType enum Type determining whether the threshold profile can be edited. The threshold
profile can be edited only if the type is "User" or "Default".
(For details about the valid values, see the table TemplateCreatorType in List
of enumerators.)
User
Preset
Default
(For details about the valid values, see the table PerformanceResourceType
in List of enumerators.)
representativeProfileId string The Signature of the representative profile among the split profiles.
Attribute Type Description
thresholdValues ThresholdValue[] Information about the thresholds set in the threshold profile. This item is
specified only for the thresholds for system resources.
margin string ID of the margin set in the threshold profile. This item is specified only for the
thresholds for user resources.
marginName string Display name of the margin set in the threshold profile. This item is specified
only for the thresholds for user resources.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item is specified
only for the thresholds for user resources.
autoAssignFilters string[] Rules of automatic assignment to the resources set in the threshold profile.
This item is specified only for the thresholds for user resources.
monitoring boolean Whether or not to enable threshold-based monitoring. If enabled, "true" is set. If
disabled, "false" is set.
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
monitoringMode enum Monitoring status of the plan. This item is specified when the thresholds
are recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List
of enumerators.)
Attribute Type Description
thresholdValueOfWarning float Value of the warning threshold. This item is specified when the
thresholds are recalculated for each component.
thresholdValueOfCritical float Value of the critical threshold. This item is specified when the thresholds
are recalculated for each component.
fixed boolean Specifies whether or not to recalculate the thresholds periodically. If the
thresholds are recalculated periodically, "true" is set. If the thresholds are
not recalculated periodically, "false" is set. This item is specified if the
thresholds are to be recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/ThresholdProfiles
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "thProfile#RAID_STORAGE_PRESET",
"profileName" : "#Preset Profile for Storage",
"description" : "#Preset Profile for Storage",
"resourceType" : "System",
"profileType" : "Preset",
"profileResourceType" : "RAID_STORAGE",
"thresholdValues" : [ {
"instanceID" : "th#RAID_STORAGE_RAIDPORT_TOTALIOPS_PRESET",
"monitoring" : false,
"metricType" : "RAID_STORAGE_RAIDPORT_TOTALIOPS",
"metricTypeName" : "Total IOPS (Port)",
"unit" : "Ops",
"proportion" : false,
"thresholdValueOfWarning" : 0.0,
"thresholdValueOfCritical" : 0.0,
"stepSize" : 1.0,
"max" : 3.4028235E38,
"min" : 0.0
}, {
........
} ],
"margin" : "Normal",
"marginName" : "Normal",
"numOfResources" : 0,
"autoAssignFilters" : [ ]
}, {
........
} ],
"count" : 26
}
Related reference
List of enumerators
You can create a new threshold profile by specifying information such as the profile name and thresholds.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/ThresholdProfiles
Request body
The structure of the request body and the object attributes are as follows:
ThresholdProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"resourceType":"...",
"profileType":"...",
"profileResourceType":"...",
"representativeProfileId":"...",
"isRepresentativeProfile":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoring":"...",
"metricType":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"..."
},
:
],
"margin":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"..."
},
:
]
},
:
]
}
(For details about the valid values, see the table PerfThresholdResourceType
in List of enumerators.)
User
System
Reserve
profileType enum Type determining whether the threshold profile can be edited. The threshold
profile can be edited only if the type is "User" or "Default".
(For details about the valid values, see the table TemplateCreatorType in List
of enumerators.)
User
Preset
Default
Attribute Type Description
(For details about the valid values, see the table PerformanceResourceType
in List of enumerators.)
representativeProfileId string The Signature of the representative profile among the split profiles.
thresholdValues ThresholdValue[] Information about the thresholds set in the threshold profile. This item is
specified only for the thresholds for system resources.
margin string ID of the margin set in the threshold profile. This item is specified only for the
thresholds for user resources.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item is specified
only for the thresholds for user resources.
monitoring boolean Whether or not to enable threshold-based monitoring. If enabled, "true" is set. If
disabled, "false" is set.
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table PlanType in List of
enumerators.)
Attribute Type Description
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
ThresholdProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"resourceType":"...",
"profileType":"...",
"profileResourceType":"...",
"representativeProfileId":"...",
"isRepresentativeProfile":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoring":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"..."
},
:
],
"margin":"...",
"marginName":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"...",
"maxValueOfDynamic":"...",
"minValueOfDynamic":"...",
"avgValueOfDynamic":"..."
},
:
],
"monitoringMode":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"fixed":"..."
},
:
],
"numOfResources":"...",
"autoAssignFilters":["...", ...]
}
(For details about the valid values, see the table PerfThresholdResourceType
in List of enumerators.)
User
System
Reserve
profileType enum Type determining whether the threshold profile can be edited. The threshold
profile can be edited only if the type is "User" or "Default".
(For details about the valid values, see the table TemplateCreatorType in List
of enumerators.)
User
Preset
Default
(For details about the valid values, see the table PerformanceResourceType
in List of enumerators.)
representativeProfileId string The Signature of the representative profile among the split profiles.
thresholdValues ThresholdValue[] Information about the thresholds set in the threshold profile. This item is
specified only for the thresholds for system resources.
margin string ID of the margin set in the threshold profile. This item is specified only for the
thresholds for user resources.
marginName string Display name of the margin set in the threshold profile. This item is specified
only for the thresholds for user resources.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item is specified
only for the thresholds for user resources.
Attribute Type Description
autoAssignFilters string[] Rules of automatic assignment to the resources set in the threshold profile.
This item is specified only for the thresholds for user resources.
monitoring boolean Whether or not to enable threshold-based monitoring. If enabled, "true" is set. If
disabled, "false" is set.
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
monitoringMode enum Monitoring status of the plan. This item is specified when the thresholds
are recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List
of enumerators.)
thresholdValueOfWarning float Value of the warning threshold. This item is specified when the
thresholds are recalculated for each component.
thresholdValueOfCritical float Value of the critical threshold. This item is specified when the thresholds
are recalculated for each component.
fixed boolean Specifies whether or not to recalculate the thresholds periodically. If the
thresholds are recalculated periodically, "true" is set. If the thresholds are
not recalculated periodically, "false" is set. This item is specified if the
thresholds are to be recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
Status codes
Example code
[Request Header]
POST /Analytics/v1/objects/ThresholdProfiles
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"profileName":"ESX Profile-0",
"description":"xxxxxxxxxxxxxxx",
"resourceType":"System",
"profileResourceType":"RAID_STORAGE",
"thresholdValues":[{
"metricType":"RAID_STORAGE_RAIDPORT_TOTALIOPS",
"metricTypeName":"Total IOPS (Port)",
"unit":"Ops",
"instanceID":"th#092967a9-5451-48dd-94fd-ec8b1ef4ae51",
"min":0.0,
"proportion":false,
"max":3.4028235E38,
"stepSize":1.0,
"thresholdValueOfWarning":0.0,
"thresholdValueOfCritical":0.0,
"monitoring":false
}]
}
[Response Header]
HTTP/1.1 201 Created
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "thProfile#ce4cc49a-a5e7-4b0e-9467-46476d425f27",
"profileName" : "ESX Profile-0",
"description" : "xxxxxxxxxxxxxxx",
"resourceType" : "System",
"profileType" : "User",
"profileResourceType" : "RAID_STORAGE",
"thresholdValues" : [ {
"instanceID" : "th#eb34659a-0ebe-44b1-a95e-53af269ee679",
"monitoring" : false,
"metricType" : "RAID_STORAGE_RAIDPORT_TOTALIOPS",
"metricTypeName" : "Total IOPS (Port)",
"unit" : "Ops",
"proportion" : false,
"thresholdValueOfWarning" : 0.0,
"thresholdValueOfCritical" : 0.0,
"stepSize" : 1.0,
"max" : 3.4028235E38,
"min" : 0.0
} ],
"numOfResources" : 0,
"autoAssignFilters" : [ ]
}
Related reference
List of enumerators
You can obtain information about a specific threshold profile, such as the profile name and thresholds.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ThresholdProfiles/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
ThresholdProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"resourceType":"...",
"profileType":"...",
"profileResourceType":"...",
"representativeProfileId":"...",
"isRepresentativeProfile":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoring":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"..."
},
:
],
"margin":"...",
"marginName":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"...",
"maxValueOfDynamic":"...",
"minValueOfDynamic":"...",
"avgValueOfDynamic":"..."
},
:
],
"monitoringMode":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"fixed":"..."
},
:
],
"numOfResources":"...",
"autoAssignFilters":["...", ...]
}
(For details about the valid values, see the table PerfThresholdResourceType
in List of enumerators.)
User
System
Reserve
profileType enum Type determining whether the threshold profile can be edited. The threshold
profile can be edited only if the type is "User" or "Default".
(For details about the valid values, see the table TemplateCreatorType in List
of enumerators.)
User
Preset
Default
(For details about the valid values, see the table PerformanceResourceType
in List of enumerators.)
representativeProfileId string The Signature of the representative profile among the split profiles.
thresholdValues ThresholdValue[] Information about the thresholds set in the threshold profile. This item is
specified only for the thresholds for system resources.
margin string ID of the margin set in the threshold profile. This item is specified only for the
thresholds for user resources.
marginName string Display name of the margin set in the threshold profile. This item is specified
only for the thresholds for user resources.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item is specified
only for the thresholds for user resources.
autoAssignFilters string[] Rules of automatic assignment to the resources set in the threshold profile.
This item is specified only for the thresholds for user resources.
monitoring boolean Whether or not to enable threshold-based monitoring. If enabled, "true" is set. If
disabled, "false" is set.
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
monitoringMode enum Monitoring status of the plan. This item is specified when the thresholds
are recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List
of enumerators.)
thresholdValueOfWarning float Value of the warning threshold. This item is specified when the
thresholds are recalculated for each component.
thresholdValueOfCritical float Value of the critical threshold. This item is specified when the thresholds
are recalculated for each component.
fixed boolean Specifies whether or not to recalculate the thresholds periodically. If the
thresholds are recalculated periodically, "true" is set. If the thresholds are
not recalculated periodically, "false" is set. This item is specified if the
thresholds are to be recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/ThresholdProfiles
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "thProfile#ESX_PRESET",
"profileName" : "#Preset Profile for Hypervisor (VMware)",
"description" : "#Preset Profile for Hypervisor (VMware)",
"resourceType" : "System",
"profileType" : "Preset",
"profileResourceType" : "ESX",
"thresholdValues" : [ {
"instanceID" : "th#ESX_H_CPUUSAGE_PRESET",
"monitoring" : true,
"metricType" : "ESX_H_CPUUSAGE",
"metricTypeName" : "CPU Usage (VMware Host)",
"unit" : "%",
"proportion" : false,
"thresholdValueOfWarning" : 75.0,
"thresholdValueOfCritical" : 90.0,
"stepSize" : 1.0,
"max" : 3.4028235E38,
"min" : 0.0
}, {
........
} ],
"margin" : "Normal",
"marginName" : "Normal",
"numOfResources" : 0,
"autoAssignFilters" : [ ]
}, {
........
} ],
"count" : 26
}
Related reference
List of enumerators
You can update information about a specific threshold profile, such as the profile name and thresholds.
Execution permission
Admin, Modify
Request line
PUT baseURL/v1/objects/ThresholdProfiles/{id}
Request body
The structure of the request body and the object attributes are as follows:
ThresholdProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"resourceType":"...",
"profileType":"...",
"profileResourceType":"...",
"representativeProfileId":"...",
"isRepresentativeProfile":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoring":"...",
"metricType":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"..."
},
:
],
"margin":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"..."
},
:
]
},
:
]
}
(For details about the valid values, see the table PerfThresholdResourceType
in List of enumerators.)
User
System
Reserve
profileType enum Type determining whether the threshold profile can be edited. The threshold
profile can be edited only if the type is "User" or "Default".
(For details about the valid values, see the table TemplateCreatorType in List
of enumerators.)
User
Preset
Default
(For details about the valid values, see the table PerformanceResourceType
in List of enumerators.)
representativeProfileId string The Signature of the representative profile among the split profiles.
thresholdValues ThresholdValue[] Information about the thresholds set in the threshold profile. This item is
specified only for the thresholds for system resources.
margin string ID of the margin set in the threshold profile. This item is specified only for the
thresholds for user resources.
Attribute Type Description
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item is specified
only for the thresholds for user resources.
monitoring boolean Whether or not to enable threshold-based monitoring. If enabled, "true" is set. If
disabled, "false" is set.
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
Attribute Type Description
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
Response body
The structure of the response body and the object attributes is as follows:
ThresholdProfile
{
"instanceID":"...",
"profileName":"...",
"description":"...",
"resourceType":"...",
"profileType":"...",
"profileResourceType":"...",
"representativeProfileId":"...",
"isRepresentativeProfile":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoring":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"..."
},
:
],
"margin":"...",
"marginName":"...",
"plans":[{
"instanceID":"...",
"planType":"...",
"planName":"...",
"schedule":["...", ...],
"from":"...",
"to":"...",
"priority":"...",
"description":"...",
"thresholdValues":[{
"instanceID":"...",
"monitoringMode":"...",
"metricType":"...",
"metricTypeName":"...",
"unit":"...",
"proportion":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"stepSize":"...",
"max":"...",
"min":"...",
"maxValueOfDynamic":"...",
"minValueOfDynamic":"...",
"avgValueOfDynamic":"..."
},
:
],
"monitoringMode":"...",
"thresholdValueOfWarning":"...",
"thresholdValueOfCritical":"...",
"fixed":"..."
},
:
],
"numOfResources":"...",
"autoAssignFilters":["...", ...]
}
(For details about the valid values, see the table PerfThresholdResourceType
in List of enumerators.)
User
System
Reserve
profileType enum Type determining whether the threshold profile can be edited. The threshold
profile can be edited only if the type is "User" or "Default".
(For details about the valid values, see the table TemplateCreatorType in List
of enumerators.)
User
Preset
Default
(For details about the valid values, see the table PerformanceResourceType
in List of enumerators.)
representativeProfileId string The Signature of the representative profile among the split profiles.
thresholdValues ThresholdValue[] Information about the thresholds set in the threshold profile. This item is
specified only for the thresholds for system resources.
margin string ID of the margin set in the threshold profile. This item is specified only for the
thresholds for user resources.
marginName string Display name of the margin set in the threshold profile. This item is specified
only for the thresholds for user resources.
plans ThresholdPlan[] Information about the plans set in the threshold profile. This item is specified
only for the thresholds for user resources.
autoAssignFilters string[] Rules of automatic assignment to the resources set in the threshold profile.
This item is specified only for the thresholds for user resources.
monitoring boolean Whether or not to enable threshold-based monitoring. If enabled, "true" is set. If
disabled, "false" is set.
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
(For details about the valid values, see the table PlanType in List of
enumerators.)
Base
Schedule
schedule integer[] Day of the week when to apply the plan. 1: Mon., 2: Tue., 3: Wed., 4: Thu.,
5: Fri., 6: Sat., and 7: Sun. The value set here takes effect only if the plan
type is "Schedule".
Attribute Type Description
from string Start time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
to string End time of the plan. Specified in "hh:mm" format. The value set here
takes effect only if the plan type is "Schedule".
monitoringMode enum Monitoring status of the plan. This item is specified when the thresholds
are recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List
of enumerators.)
thresholdValueOfWarning float Value of the warning threshold. This item is specified when the
thresholds are recalculated for each component.
thresholdValueOfCritical float Value of the critical threshold. This item is specified when the thresholds
are recalculated for each component.
fixed boolean Specifies whether or not to recalculate the thresholds periodically. If the
thresholds are recalculated periodically, "true" is set. If the thresholds are
not recalculated periodically, "false" is set. This item is specified if the
thresholds are to be recalculated for each component.
(For details about the valid values, see the table MonitoringMode in List of
enumerators.)
(For details about the valid values, see the table MetricType in List of
enumerators.)
proportion boolean Threshold setting. If a warning or critical alert is generated when the
measurement value goes above the threshold, "true" is set. If a warning or
critical alert is generated when the measurement value goes below the
threshold, "false" is set.
Status codes
200 OK Success.
Example code
[Request Header]
PUT /Analytics/v1/objects/ThresholdProfiles/thProfile%23b46e902b-23fc-4a16-9c1b-757e0a669b94
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"instanceID":"thProfile#b46e902b-23fc-4a16-9c1b-757e0a669b94",
"profileName":"ESX Profile-20160720113617720",
"description":"zzzzzzzzzzzzzzzz",
"resourceType":"System",
"thresholdValues":[{
"metricType":"DF_STORAGE_DFPORT_CTL0TRANSRATE",
"metricTypeName":"CTL 0 Transfer Rate (Port)",
"unit":"KBps",
"instanceID":"th#54103f66-2c22-4347-8cad-bf204b260762",
"min":0.0,
"proportion":false,
"max":3.4028235E38,
"stepSize":1.0,
"thresholdValueOfWarning":0.0,
"thresholdValueOfCritical":0.0,
"monitoring":false
},{
.......
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "thProfile#b46e902b-23fc-4a16-9c1b-757e0a669b94",
"profileName" : "ESX Profile-20160720113617720",
"description" : "zzzzzzzzzzzzzzzz",
"resourceType" : "System",
"profileType" : "User",
"profileResourceType" : "DF_STORAGE",
"thresholdValues" : [ {
"instanceID" : "th#54103f66-2c22-4347-8cad-bf204b260762",
"monitoring" : false,
"metricType" : "DF_STORAGE_DFPORT_CTL0TRANSRATE",
"metricTypeName" : "CTL 0 Transfer Rate (Port)",
"unit" : "KBps",
"proportion" : false,
"thresholdValueOfWarning" : 0.0,
"thresholdValueOfCritical" : 0.0,
"stepSize" : 1.0,
"max" : 3.4028235E38,
"min" : 0.0
}, {
........
} ],
"numOfResources" : 0,
"autoAssignFilters" : [ ]
}
Related reference
List of enumerators
Execution permission
Admin, Modify
Request line
DELETE baseURL/v1/objects/ThresholdProfiles/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
Example code
[Request Header]
DELETE /Analytics/v1/objects/ThresholdProfiles/thProfile%23ce4cc49a-a5e7-4b0e-9467-46476d425f27
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 204 No Content
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
You can obtain a list of operations that can be performed on a specific threshold profile.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ThresholdProfiles/{id}/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
Collections (Type: Collections)
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/ThresholdProfiles/111111/actions
Content-Type: application/json
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "updateTargetResource",
"href" : "[Link]
eTargetResource/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "getResourceThresholdValues",
"href" : "[Link]
sourceThresholdValues/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}, {
"name" : "updateDynamicThreshold",
"href" : "[Link]
eDynamicThreshold/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 3
}
The following operation is the initial step to assign a specific threshold profile to resources to be monitored.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ThresholdProfiles/{id}/actions/updateTargetResource
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
InstanceID
{
"instanceID":"..."
}
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/ThresholdProfiles/thProfile%23fc4cd6cb-0a99-4ee3-9938-228838cceb70/act
ions/updateTargetResource
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "updateTargetResource",
"href" : "[Link]
d0a99%2d4ee3v9938%2d228838cceb70/actions/updateTargetResource/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
}
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/ThresholdProfiles/{id}/actions/updateTargetResource/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
InstanceID
{
"instanceID":"..."
}
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/ThresholdProfiles/thProfile%23fc4cd6cb-0a99-4ee3-9938-228838cceb70/ac
tions/updateTargetResource/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "updateTargetResource",
"href" : "[Link]
d0a99%2d4ee3v9938%2d228838cceb70/actions/updateTargetResource/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"instanceID":"vm#ABC_172.17.17.115_vm-142"
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "d10bd225-2b4d-4ea7-90e0-aa5d
"created" : "2016-07-20T[Link].212+09:00",
"updated" : "2016-07-20T[Link].504+09:00",
"completed" : "2016-07-20T[Link].504+09:00
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Related reference
List of enumerators
Preparing to obtain a threshold information with profiles and resources specified
The following operation is the initial step to obtain information about dynamic or static thresholds by specifying threshold profiles
and resources.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ThresholdProfiles/{id}/actions/getResourceThresholdValues
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ResourceThresholdParam
{
"metricType":"...",
"resourceType":"...",
"resourceIds":["...", ...]
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
resourceIds string[] ID of the resource to be obtained. To obtain multiple resources at the same
time, specify the IDs of those resources.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/ThresholdProfiles/thProfile%23fe428a12-35a8-4210-8e9d-d0d28fe38d5d/act
ions/getResourceThresholdValues
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getResourceThresholdValues",
"href" : "[Link]
d35a8%2d4210%2d8e9d%2dd0d28fe38d5d/actions/getResourceThresholdValues/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"instanceID" : "",
"metricType" : "WIN_CPU_LOAD",
"resourceType" : "INVALID_MEMBER",
"resourceIds" : [ ]
} ]
}
Related reference
List of enumerators
You can obtain dynamic or static threshold information by specifying a threshold profile and resources.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/ThresholdProfiles/{id}/actions/getResourceThresholdValues/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ResourceThresholdParam
{
"metricType":"...",
"resourceType":"...",
"resourceIds":["...", ...]
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
resourceIds string[] ID of the resource to be obtained. To obtain multiple resources at the same
time, specify the IDs of those resources.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/ThresholdProfiles/thProfile%23fe428a12-35a8-4210-8e9d-d0d28fe38d5d/ac
tions/getResourceThresholdValues/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getResourceThresholdValues",
"href" : "[Link]
2%2d35a8%2d4210%2d8e9d%2dd0d28fe38d5d/actions/getResourceThresholdValues/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"resourceType":"ESX_VM",
"metricType":"ESX_VM_VM_CPUREADY",
"resourceIds":["vm#ABC_172.17.17.115_vm-142"]
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "21735e31-eb30-4c9d-b049-9c8f161619b4",
"created" : "2016-07-20T[Link].279+09:00",
"updated" : "2016-07-20T[Link].282+09:00",
"completed" : "2016-07-20T[Link].282+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ {
"instanceID" : "vm#ABC_172.17.17.115_vm-142",
"metricType" : "ESX_VM_VM_CPUREADY",
"metricTypeName" : "CPU Ready (VMware Virtual Machine)",
"resourceType" : "ESX_VM",
"resourceId" : "vm#ABC_172.17.17.115_vm-142",
"resourceName" : "exampleVM",
"profileId" : "thProfile#ESX_VM",
"profileName" : "Default Profile for VM (VMware)",
"values" : [ {
"instanceID" : "thPlan#ESX_VM",
"planType" : "Base",
"planName" : "Base",
"schedule" : [ 1, 2, 3, 4, 5, 6, 7 ],
"from" : "00:00",
"to" : "24:00",
"priority" : 1,
"description" : "Base Plan",
"monitoringMode" : "Dynamic",
"unit" : "msec",
"proportion" : false,
"stepSize" : 1.0,
"max" : 3.4028235E38,
"min" : 0.0,
"fixed" : false
} ]
} ]
}
Related reference
List of enumerators
The following operation is the initial step to set dynamic thresholds by specifying user profiles and resources.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/ThresholdProfiles/{id}/actions/updateDynamicThreshold
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ResourceThresholdFixedParam
{
"metricType":"...",
"resourceID":"...",
"resourceType":"...",
"planID":"...",
"fixed":"...",
"value":"..."
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
fixed boolean Whether or not to recalculate the thresholds periodically. If the thresholds are
recalculated periodically, "true" is set. If the thresholds are not recalculated
periodically, "false" is set. This item is specified if the thresholds are to be
manipulated for each component.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/ThresholdProfiles/thProfile%23abcc9f1e-b1b8-45f4-9931-31eedd5905be/act
ions/updateDynamicThreshold
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "updateDynamicThreshold",
"href" : "[Link]
db1b8%2d45f4%2d9931%2d31eedd5905be/actions/updateDynamicThreshold/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"instanceID" : "",
"metricType" : "WIN_CPU_LOAD",
"resourceID" : "",
"resourceType" : "INVALID_MEMBER",
"planID" : "",
"fixed" : false,
"value" : 0.0
} ]
}
Related reference
List of enumerators
You can set dynamic thresholds by specifying a user profile and resources.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/objects/ThresholdProfiles/{id}/actions/updateDynamicThreshold/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
ResourceThresholdFixedParam
{
"metricType":"...",
"resourceID":"...",
"resourceType":"...",
"planID":"...",
"fixed":"...",
"value":"..."
}
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
fixed boolean Whether or not to recalculate the thresholds periodically. If the thresholds are
recalculated periodically, "true" is set. If the thresholds are not recalculated
periodically, "false" is set. This item is specified if the thresholds are to be
manipulated for each component.
Response body
The structure of the response body and the object attributes is as follows:
Job
{
"instanceID":"...",
"created":"...",
"updated":"...",
"completed":"...",
"state":"...",
"affectedResource":["...", ...],
"result":["...", ...]
}
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/objects/ThresholdProfiles/thProfile%236e5c28ee-0b19-46da-a48b-6b340dc0e329/ac
tions/updateDynamicThreshold/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "updateDynamicThreshold",
"href": "[Link]
2d0b19%2d46da%2da48b52d6b340dc0e329/actions/updateDynamicThreshold/invoke",
"method": "POST",
"type": "application/json",
"parameters": [
{
"metricType": "ESX_VM_VM_CPUREADY",
"resourceID": "vm#ITPDLab_172.17.17.115_vm-247",
"resourceType": "ESX_VM",
"planID": "thPlan#6ffc32af-b18d-4afe-bc65-449ceda5c443",
"fixed": false,
"value": 90.0
}
]
}
[Response Header]
HTTP/1.1 200 OK
Date: Mon, 22 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO a27ec87fb489127695fb5c88fcbe68e697ff3e87_Y2UOI2pkMXQ=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID": "23e9ef9a-045c-4593-bb24-2ba9a0f9e545",
"created": "2016-08-22T[Link].925+09:00",
"updated": "2016-08-22T[Link].490+09:00",
"completed": "2016-08-22T[Link].490+09:00",
"state": "success",
"affectedResource": [
],
"result": [
]
}
Related reference
List of enumerators
You can obtain a list of operations related to user resources, such as volumes and virtual machines.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/UserResource/actions
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Action objects. For details about Action, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
Attribute Type Description
count int Number of data items that meet the conditions related to this query(API).
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
Status codes
200 OK Success.
Status code Reason phrase Description
Example code
[Request Header]
GET /Analytics/v1/services/UserResource/actions
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"name" : "getComponentStatusCountByMetric",
"href" : "[Link]
usCountByMetric/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ ]
} ],
"count" : 1
}
Preparing to obtain the number of user resources counted for each metric and for each status
The following operation is the initial step to obtain the number of user resources counted for each metric and for each status.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/services/UserResource/actions/getComponentStatusCountByMetric
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetComponentStatusCountByMetricParam
{
"componentType":"...",
"metricTypes":["...", ...],
"metricMonitorStatuses":["...", ...],
"componentMonitorStatuses":["...", ...],
"parentNodeMonitorStatuses":["...", ...],
"metricStatuses":["...", ...]
}
(For details about the valid values, see the table ComponentType in List of
enumerators.)
STORAGE_VOLUME
VIRTUAL_MACHINE
(For details about the valid values, see the table MetricType in List of
enumerators.)
Attribute Type Description
(For details about the valid values, see the table MetricMonitorStatus in List of
enumerators.)
Monitor
MonitorOff
componentMonitorStatuses enum[] Monitoring status of user resources to be aggregated. Always specify "InUse".
(For details about the valid values, see the table ComponentMonitorType in List
of enumerators.)
InUse
NotMonitored
parentNodeMonitorStatuses enum[] Monitoring status of the device that the aggregation-target user resources
belong to. Always specify "Manage".
(For details about the valid values, see the table ManagementLevelType in List
of enumerators.)
Manage
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
NotMonitored
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/services/UserResource/actions/getComponentStatusCountByMetric
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"name" : "getComponentStatusCountByMetric",
"href" : "[Link]
CountByMetric/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ {
"componentType" : "VIRTUAL_MACHINE",
"metricTypes" : [ "ESX_VM_DISKPART_DISKREAD", "ESX_VM_DISKPART_DISKWRITE" ],
"metricMonitorStatuses" : [ "Monitor", "MonitorOff" ],
"componentMonitorStatuses" : [ "InUse", "NotMonitored" ],
"parentNodeMonitorStatuses" : [ "Manage", "MonitorOff" ],
"metricStatuses" : [ "Critical", "Warning", "Normal" ]
} ]
}
Related reference
List of enumerators
Getting the number of user resources counted for each metric and for each status
You can obtain the number of user resources counted for each metric and for each status.
Execution permission
Admin, Modify
Request line
POST baseURL/v1/services/UserResource/actions/getComponentStatusCountByMetric/invoke
Request body
The structure of the request body and the object attributes are as follows:
Action
{
"name":"...",
"href":"...",
"method":"...",
"type":"...",
"parameters":["...", ...]
}
GetComponentStatusCountByMetricParam
{
"componentType":"...",
"metricTypes":["...", ...],
"metricMonitorStatuses":["...", ...],
"componentMonitorStatuses":["...", ...],
"parentNodeMonitorStatuses":["...", ...],
"metricStatuses":["...", ...]
}
(For details about the valid values, see the table ComponentType in List of
enumerators.)
STORAGE_VOLUME
VIRTUAL_MACHINE
(For details about the valid values, see the table MetricType in List of
enumerators.)
(For details about the valid values, see the table MetricMonitorStatus in List of
enumerators.)
Monitor
MonitorOff
Attribute Type Description
componentMonitorStatuses enum[] Monitoring status of user resources to be aggregated. Always specify "InUse".
(For details about the valid values, see the table ComponentMonitorType in List
of enumerators.)
InUse
NotMonitored
parentNodeMonitorStatuses enum[] Monitoring status of the device that the aggregation-target user resources
belong to. Always specify "Manage".
(For details about the valid values, see the table ManagementLevelType in List
of enumerators.)
Manage
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
NotMonitored
Response body
The structure of the response body and the object attributes is as follows:
ComponentStatusCountByMetric
{
"componentStatus":"...",
"count":"...",
"componentIds":["...", ...]
}
(For details about the valid values, see the table ElementStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
NotMonitored
Status codes
200 OK Success.
Example code
[Request Header]
POST /Analytics/v1/services/UserResource/actions/getComponentStatusCountByMetric/invoke
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"name": "getComponentStatusCountByMetric",
"href": "[Link]
ountByMetric/invoke",
"method": "POST",
"type": "application/json",
"parameters":[{
"componentType":"VIRTUAL_MACHINE",
"metricTypes":["ESX_VM_VM_NETDROPPEDRX","ESX_VM_VM_NETDROPPEDTX"],
"metricMonitorStatuses":["Monitor"],
"componentMonitorStatuses":["InUse"],
"parentNodeMonitorStatuses":["Manage"],
"metricStatuses":["Warning","Critical"]
}]
}
[Response Header]
HTTP/1.1 200 OK
Date: Thu, 11 Aug 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 8113b75377dac59b7c48ee2b947b20d3bbc11f_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V0810
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "52bdddf9-6b3b-437f-b954-43536a11ede6",
"created" : "2016-08-12T[Link].467+09:00",
"updated" : "2016-08-12T[Link].467+09:00",
"completed" : "2016-08-12T[Link].467+09:00",
"state" : "success",
"affectedResource" : [ ],
"result" : [ ]
}
Related reference
List of enumerators
You can obtain a list of users and user-related information, such as user IDs and permissions. If you use an external authorization
server to perform user authentication, you have to manage users on an external authorization server.
Execution permission
User Management
Request line
GET baseURL/v1/objects/Users
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of UserInfo objects. For details about UserInfo, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
UserInfo
{
"instanceID":"...",
"userId":"...",
"analyticsPermissions":["...", ...],
"userManagementPermissions":["...", ...],
"fullName":"...",
"description":"...",
"email":"...",
"customGuiProperties":[{
"key":"...",
"value":"..."
},
:
],
"defaultGuiProperties":[{
"key":"...",
"value":"..."
},
:
]
}
analyticsPermissions string[] User permission for Ops Center Analyzer operations. "Admin" and "Modify" are
set.
userManagementPermissions string[] User permission for manipulating user information. "Admin" can be set.
fullName string Name of the user (full name). Two consecutive dollar signs ($$) are converted
into a single space.
customGuiProperties KeyValue[] Acquires the properties used to customize the GUI (for example, the
dashboard). The contents of the properties change with each version. Do not
specify the properties in the body of the request because these properties are
only used with the Ops Center Analyzer GUI.
defaultGuiProperties KeyValue[] Specifies the data that is acquired from the server in order to customize the
Ops Center Analyzer GUI (for example, the dashboard). The contents of the
properties change with the version.
Status codes
Status code Reason phrase Description
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/Users
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "USER_0",
"userId" : "System",
"analyticsPermissions" : [ "Admin", "Modify" ],
"userManagementPermissions" : [ "Admin" ],
"fullName" : "",
"description" : "Built-in account",
"email" : ""
} ],
"count" : 1
}
Creating a user
You can create a new user by specifying information such as the user ID and permissions. If you use an external authorization
server to perform user authentication, you have to manage users on an external authorization server.
Execution permission
User Management
Request line
POST baseURL/v1/objects/Users
Request body
The structure of the request body and the object attributes are as follows:
UserInfo
{
"userId":"...",
"analyticsPermissions":["...", ...],
"userManagementPermissions":["...", ...],
"fullName":"...",
"description":"...",
"email":"...",
"password":"...",
"customGuiProperties":[{
"key":"...",
"value":"..."
},
:
]
}
analyticsPermissions string[] User permission for Ops Center Analyzer operations. "Admin" and "Modify" are
set.
userManagementPermissions string[] User permission for manipulating user information. "Admin" can be set.
fullName string Name of the user (full name). Two consecutive dollar signs ($$) are converted
into a single space.
customGuiProperties KeyValue[] Acquires the properties used to customize the GUI (for example, the
dashboard). The contents of the properties change with each version. Do not
specify the properties in the body of the request because these properties are
only used with the Ops Center Analyzer GUI.
Response body
The structure of the response body and the object attributes is as follows:
UserInfo
{
"instanceID":"...",
"userId":"...",
"analyticsPermissions":["...", ...],
"userManagementPermissions":["...", ...],
"fullName":"...",
"description":"...",
"email":"...",
"customGuiProperties":[{
"key":"...",
"value":"..."
},
:
],
"defaultGuiProperties":[{
"key":"...",
"value":"..."
},
:
]
}
analyticsPermissions string[] User permission for Ops Center Analyzer operations. "Admin" and "Modify" are
set.
userManagementPermissions string[] User permission for manipulating user information. "Admin" can be set.
fullName string Name of the user (full name). Two consecutive dollar signs ($$) are converted
into a single space.
customGuiProperties KeyValue[] Acquires the properties used to customize the GUI (for example, the
dashboard). The contents of the properties change with each version. Do not
specify the properties in the body of the request because these properties are
only used with the Ops Center Analyzer GUI.
defaultGuiProperties KeyValue[] Specifies the data that is acquired from the server in order to customize the
Ops Center Analyzer GUI (for example, the dashboard). The contents of the
properties change with the version.
Status codes
Example code
[Request Header]
POST /Analytics/v1/objects/Users
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"userId":"Test_UserId",
"analyticsPermissions":[ "Admin", "Modify" ],
"userManagementPermissions":[ "Admin" ],
"fullName":"FullFull",
"description":"template",
"email":"admin@[Link]",
"password":"YWJjZGVm"
}
[Response Header]
HTTP/1.1 201 Created
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "USER_146898064241918",
"userId" : "Test_UserId",
"analyticsPermissions" : [ "Admin", "Modify" ],
"userManagementPermissions" : [ "Admin" ],
"fullName" : "FullFull",
"description" : "template",
"email" : "admin@[Link]"
}
You can obtain information about a specific user, such as the user ID and permissions. To obtain an authenticated user's own
information, specify an underscore (_) for {id}. User management permissions are not needed to obtain the user's own
information. If you use an external authorization server to perform user authentication, you have to manage users on an external
authorization server.
Execution permission
User Management
Request line
GET baseURL/v1/objects/Users/{id}
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
UserInfo
{
"instanceID":"...",
"userId":"...",
"analyticsPermissions":["...", ...],
"userManagementPermissions":["...", ...],
"fullName":"...",
"description":"...",
"email":"...",
"customGuiProperties":[{
"key":"...",
"value":"..."
},
:
],
"defaultGuiProperties":[{
"key":"...",
"value":"..."
},
:
]
}
analyticsPermissions string[] User permission for Ops Center Analyzer operations. "Admin" and "Modify" are
set.
userManagementPermissions string[] User permission for manipulating user information. "Admin" can be set.
fullName string Name of the user (full name). Two consecutive dollar signs ($$) are converted
into a single space.
customGuiProperties KeyValue[] Acquires the properties used to customize the GUI (for example, the
dashboard). The contents of the properties change with each version. Do not
specify the properties in the body of the request because these properties are
only used with the Ops Center Analyzer GUI.
defaultGuiProperties KeyValue[] Specifies the data that is acquired from the server in order to customize the
Ops Center Analyzer GUI (for example, the dashboard). The contents of the
properties change with the version.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/Users/USER_14689806179850
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "USER_14689806179850",
"userId" : "put_test_UserId",
"analyticsPermissions" : [ "Admin", "Modify" ],
"userManagementPermissions" : [ "Admin" ],
"fullName" : "FullFull",
"description" : "template",
"email" : "admin@[Link]"
}
You can update information about a specific user, such as the user ID and permissions. To modify an authenticated user's own
information, specify an underscore (_) for {id}. User management permissions are not needed to modify the user's own
information. However, user management permissions are needed to modify permission settings. If you use an external
authorization server to perform user authentication, you have to manage users on an external authorization server.
Execution permission
User Management
Request line
PUT baseURL/v1/objects/Users/{id}
Request body
The structure of the request body and the object attributes are as follows:
UserInfo
{
"userId":"...",
"analyticsPermissions":["...", ...],
"userManagementPermissions":["...", ...],
"fullName":"...",
"description":"...",
"email":"...",
"password":"...",
"customGuiProperties":[{
"key":"...",
"value":"..."
},
:
]
}
analyticsPermissions string[] User permission for Ops Center Analyzer operations. "Admin" and "Modify" are
set.
userManagementPermissions string[] User permission for manipulating user information. "Admin" can be set.
fullName string Name of the user (full name). Two consecutive dollar signs ($$) are converted
into a single space.
customGuiProperties KeyValue[] Acquires the properties used to customize the GUI (for example, the
dashboard). The contents of the properties change with each version. Do not
specify the properties in the body of the request because these properties are
only used with the Ops Center Analyzer GUI.
Response body
The structure of the response body and the object attributes is as follows:
UserInfo
{
"instanceID":"...",
"userId":"...",
"analyticsPermissions":["...", ...],
"userManagementPermissions":["...", ...],
"fullName":"...",
"description":"...",
"email":"...",
"customGuiProperties":[{
"key":"...",
"value":"..."
},
:
],
"defaultGuiProperties":[{
"key":"...",
"value":"..."
},
:
]
}
analyticsPermissions string[] User permission for Ops Center Analyzer operations. "Admin" and "Modify" are
set.
userManagementPermissions string[] User permission for manipulating user information. "Admin" can be set.
fullName string Name of the user (full name). Two consecutive dollar signs ($$) are converted
into a single space.
customGuiProperties KeyValue[] Acquires the properties used to customize the GUI (for example, the
dashboard). The contents of the properties change with each version. Do not
specify the properties in the body of the request because these properties are
only used with the Ops Center Analyzer GUI.
defaultGuiProperties KeyValue[] Specifies the data that is acquired from the server in order to customize the
Ops Center Analyzer GUI (for example, the dashboard). The contents of the
properties change with the version.
Status codes
200 OK Success.
Example code
[Request Header]
PUT /Analytics/v1/objects/Users/USER_146898063592417
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Request Body]
{
"userId":"User26",
"analyticsPermissions":[ "Admin", "Modify" ],
"userManagementPermissions":[ "Admin" ],
"fullName":"FullFull",
"description":"1234567890123456789012345678901234567890123456789012345678901234567890123456789
@",
"email":"admin@[Link]",
"password":"YWJjZGVmZw=="
}
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"instanceID" : "USER_146898063592417",
"userId" : "Put_test_UserId",
"analyticsPermissions" : [ "Admin", "Modify" ],
"userManagementPermissions" : [ "Admin" ],
"fullName" : "FullFull",
"description" : "12345678901234567890123456789012345678901234567890123456789012345678901234567
89@",
"email" : "admin@[Link]"
}
You can delete a specific user. If you use an external authorization server to perform user authentication, you have to manage
users on an external authorization server.
Execution permission
User Management
Request line
DELETE baseURL/v1/objects/Users/{id}
Request body
Not applicable.
Response body
Not applicable.
Status codes
Example code
[Request Header]
DELETE /Analytics/v1/objects/Users/USER_146898064241918
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 204 No Content
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: application/json
You can obtain a list of virtual machines and information about virtual machines, such as names and status.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/VirtualMachines?page={page}&pageSize={size}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of VirtualMachine objects. For details about VirtualMachine, see the table
data anyType[]
below.
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
VirtualMachine
{
"instanceID":"...",
"name":"...",
"ipAddress":"...",
"status":"...",
"monitorStatus":"...",
"description":"...",
"clusterName":"...",
"hypervisorType":"...",
"hypervisorID":"...",
"hypervisorName":"...",
"hostName":"...",
"thresholdProfileID":"...",
"thresholdProfileName":"...",
"groupIDs":["...", ...],
"groupNames":["...", ...],
"gradeNames":["...", ...],
"gradeOrders":["...", ...],
"managementToolNames":["...", ...],
"managementToolIDs":["...", ...],
"profileResourceType":"...",
"assignmentSchedule":"..."
}
(For details about the valid values, see the table NodeStatusType in List of
enumerators.)
Normal
Warning
Critical
Unknown
(For details about the valid values, see the table ComponentMonitorType in List
of enumerators.)
InUse
NotMonitored
clusterName string Name of the Cluster that the virtual machine belongs to.
hypervisorType enum Type of hypervisor that the virtual machine belongs to.
(For details about the valid values, see the table ArgusNodeType in List of
enumerators.)
SERVER_ESX
SERVER_HYPERV
hypervisorID string ID of the hypervisor that the virtual machine belongs to.
hypervisorName string Name of the hypervisor that the virtual machine belongs to.
thresholdProfileName string Name of the threshold profile assigned to the virtual machine.
gradeNames string[] ID of the grade of the consumer assigned to the virtual machine.
gradeOrders integer[] Priority of the grade of the consumer assigned to the virtual machine.
managementToolNames string[] Name of the data center that the virtual machine belongs to.
managementToolIDs string[] ID of the data center that the virtual machine belongs to.
(For details about the valid values, see the table PerformanceResourceType in
List of enumerators.)
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/VirtualMachines
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "vm#ABC_172.17.17.115_vm-413",
"name" : "%2fvmfs%2fvolumes%2f85e4a185-ce22303c%2fvm0301_vMhot_vmonly%2fvm0301_vMhot_vmo
nl",
"status" : "Unknown",
"monitorStatus" : "InUse",
"description" : "",
"hypervisorType" : "SERVER_ESX",
"hypervisorID" : "h#ABC_172.17.17.115_host-276",
"hypervisorName" : "[Link]",
"hostName" : "vm0301vMhotvmonly",
"thresholdProfileID" : "thProfile#ESX_VM",
"thresholdProfileName" : "Default Profile for VM (VMware)",
"groupIDs" : [ "group#0" ],
"groupNames" : [ "#Unassigned Resources" ],
"gradeNames" : [ "-" ],
"gradeOrders" : [ 2147483647 ],
"managementToolNames" : [ "DataCenter" ],
"managementToolIDs" : [ "dc#ABC_172.17.17.115_datacenter-21" ],
"profileResourceType" : "ESX_VM"
}, {
......
} ],
"count" : 68
}
Related reference
List of enumerators
You can obtain a list of volumes and volume-related information, such as volume names and status.
Execution permission
Admin, Modify
Request line
GET baseURL/v1/objects/Volumes?page={page}&pageSize={size}
Query parameters
The following table describes the values for the supported parameters of a query string:
Parameter Description
Filtering conditions:
pageSize={size} (Optional) Specify the number of items that can be displayed on 1 page.
Filtering conditions:
Request body
Not applicable.
Response body
The structure of the response body and the object attributes is as follows:
Collections
{
"data":["...", ...],
"pagination":{
"page":"...",
"pageSize":"...",
"numPages":"...",
"totalCount":"..."
},
"count":"..."
}
A list of Volume objects. For details about Volume, see the table below.
data anyType[]
pagination Pagination Page information. This parameter is displayed only when the relevant resource
exists.
count int Number of data items that meet the conditions related to this query(API).
Volume
{
"instanceID":"...",
"status":"...",
"ldev":"...",
"storageSubsystemID":"...",
"storageSubsystem":"...",
"storageSubsystemMonitorStatus":"...",
"parityGroup":"...",
"storageSubsystemModel":"...",
"hostGroupIDs":["...", ...],
"hostGroupNames":["...", ...],
"vssbComputeNodeNames":["...", ...],
"thresholdProfileID":"...",
"thresholdProfileName":"...",
"groupIDs":["...", ...],
"groupNames":["...", ...],
"gradeNames":["...", ...],
"gradeOrders":["...", ...],
"profileResourceType":"...",
"virtualMachineIDs":["...", ...],
"virtualMachineNames":["...", ...],
"hostIDs":["...", ...],
"hostNames":["...", ...],
"groupIDsOfRelatedResources":["...", ...],
"groupNamesOfRelatedResources":["...", ...],
"lunOwnerIDs":["...", ...],
"lunOwnerNames":["...", ...],
"volumeLocation":"...",
"ioControlSupportType":"...",
"ioControlTaskIDs":["...", ...],
"ioControlTaskNames":["...", ...],
"ioControlLimitvalIOPS":"...",
"ioControlLimitvalTransferRate":"...",
"mixed":"...",
"automationDirectorTaskIDs":["...", ...],
"assignmentSchedule":"...",
"virtualLdev":"...",
"virtualStorageSubsystem":"...",
"virtualStorageSubsystemModel":"...",
"virtualStorageSubsystemSerialNumber":"...",
"copyType":"...",
"nvmSubsystemNQN":"...",
"nvmNamespaceID":"...",
"nvmHostNQNs":["...", ...],
"nvmHostNicknames":["...", ...]
}
(For details about the valid values, see the table NodeStatusType in List
of enumerators.)
Normal
Warning
Critical
Unknown
storageSubsystemID string ID of the storage system that the volume belongs to.
storageSubsystem string Name of the storage system that the volume belongs to.
storageSubsystemMonitorStatus enum Monitoring status of the storage system that the volume belongs to.
(For details about the valid values, see the table ManagementLevelType
in List of enumerators.)
Manage
Attribute Type Description
parityGroup string Name of the parity group that the volume belongs to.
storageSubsystemModel string Model name of the storage system that the volume belongs to.
hostGroupIDs string[] ID of the host group that the volume belongs to.
hostGroupNames string[] Name of the host group that the volume belongs to.
gradeNames string[] Name of the grade of the consumer assigned to the volume.
gradeOrders integer[] Priority of the grade of the consumer assigned to the volume
virtualMachineNames string[] Name of the virtual machine that uses the volume.
groupIDsOfRelatedResources string[] ID of the consumer assigned to the resource associated with the
volume.
groupNamesOfRelatedResources string[] Name of the consumer assigned to the resource associated with the
volume.
(For details about the valid values, see the table VolumeLocation in List
of enumerators.)
INTERNAL
EXTERNAL_HIGH
EXTERNAL_MID
EXTERNAL_LOW
EXTERNAL
(For details about the valid values, see the table IoControlSupportType
in List of enumerators.)
ioControlTaskNames string[] Name of the I/O control task assigned to the volume.
ioControlLimitvalIOPS long Limit value(IOPS) of the I/O control task assigned to the volume.
ioControlLimitvalTransferRate long Upper limit for the transfer rate, in KBp set to the volume.
mixed boolean true if a path that is assigned I/O control and a path that is not assigned
I/O control are mixed.
virtualStorageSubsystem string Name of the virtual storage system that the volume belongs to.
virtualStorageSubsystemModel string Model name of the virtual storage system that the volume belongs to.
virtualStorageSubsystemSerialNumber string Serial number of the virtual storage system that the volume belongs to.
Status codes
200 OK Success.
Example code
[Request Header]
GET /Analytics/v1/objects/Volumes
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
Host: localhost:22015
Accept: application/json
Content-Type: application/json
[Response Header]
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
WWW-Authenticate: HSSO 33659a74fcee4358dc272b34eca6ded1bf1131ec_YXZvNFIMehp3UB4jbmVyPGUgT3Q=_V08
10
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Transfer-Encoding: chunked
Content-Type: application/json
[Response Body]
{
"data" : [ {
"instanceID" : "raidLdev#10000-00^00^63",
"status" : "Normal",
"ldev" : "[Link]",
"storageSubsystemID" : "raidStorage#10000",
"storageSubsystem" : "VSP 5500H (10000)",
"storageSubsystemMonitorStatus" : "Manage",
"parityGroup" : "01-29",
"storageSubsystemModel" : "VSP 5500H",
"hostGroupIDs" : [ ],
"hostGroupNames" : [ ],
"vssbComputeNodeNames" : [ ],
"label" : "BasicVol_00099",
"thresholdProfileID" : "thProfile#RAID_VOLUME",
"thresholdProfileName" : "Default Profile for Volume",
"groupIDs" : [ "group#0" ],
"groupNames" : [ "#Unassigned Resources" ],
"gradeNames" : [ "-" ],
"gradeOrders" : [ 2147483647 ],
"profileResourceType" : "RAID_VOLUME",
"virtualMachineIDs" : [ ],
"virtualMachineNames" : [ ],
"hostIDs" : [ ],
"hostNames" : [ ],
"groupIDsOfRelatedResources" : [ ],
"groupNamesOfRelatedResources" : [ ],
"lunOwnerIDs" : [ ],
"lunOwnerNames" : [ ],
"volumeLocation" : "INTERNAL",
"ioControlSupportType" : "supported",
"ioControlTaskIDs" : [ ],
"ioControlTaskNames" : [ ],
"automationDirectorTaskIDs" : [ ],
"nvmHostNQNs" : [ ],
"nvmHostNicknames" : [ ] }, {
........
} ],
"count" : 100
}
The API functions that access RAID Agent can obtain performance data collected from the storage system that RAID Agent will
monitor. You can execute API functions even if you are using Tuning Manager - Agent for RAID or the RAID Agent that is bundled in
Ops Center Analyzer.
Note that there are differences in the performance information that can be acquired by using RAID Agent bundled with Ops Center
Analyzer and the performance information that can be acquired by using Tuning Manager - Agent for RAID. For details, see Types
of performance information that can be acquired depending on the Access Type.
Note the following before using API functions that access RAID Agent:
Make sure that communication that uses port 24221/tcp can be established between the Analyzer server and either RAID
Agent or Tuning Manager - Agent for RAID.
The Analyzer server uses the IP address of RAID Agent or Tuning Manager - Agent for RAID registered for the Hitachi
Enterprise Storage probe. Make certain that the Analyzer server can reach the IP address.
You can enhance security by restricting servers that have access to the performance data of RAID Agent. For details, refer
to the Hitachi Ops Center Analyzer Installation and Configuration Guide, and read the information about the function for
restricting the servers that can connect to RAID Agent.
After changing the instance environment for RAID Agent, you must manually refresh the RAID Agent list.
Maximum number of concurrent API requests that can access RAID Agent
This section describes the maximum number of concurrent API requests that can access RAID Agent.
The maximum number of concurrent requests that can be executed to the Analyzer server from an API client is 40. However, note
that the maximum number of concurrent requests that can be executed to an agent host from the Analyzer server is eight.
If the maximum number of requests is exceeded, an error response is returned. Set the execution intervals so that the number of
concurrent requests does not exceed the maximum.
The following are the specifications common to the API functions provided by Ops Center Analyzer that access RAID Agent.
There are some cases in which access uses a low-throughput line (for example, access from a remote location), or the data
required by one request is too large. In such cases, the transmission time can be reduced by compressing the content. However, if
a small amount of data is acquired over a high-throughput line, the compression process might cause a bottleneck. Therefore, be
sure to compress and transfer the content according to the data capacity.
Note that content compression can be used only when the version of the HTTP protocol is 1.1. The supported encoding methods
are gzip and identity. Note that content is not compressed when encoded by using the identity encoding method.
The API client includes the Accept-Encoding header in a request message to report the encoding methods. You can specify
multiple encoding methods in the API client and then assign a priority level to each method.
If an asterisk (*) is reported in the Accept-Encoding header, gzip is used as the encoding method.
For example, if you want either the gzip or identity method to be used as the compression method, you can specify the Accep
t-Encoding header in the request message as follows:
You can use content compression for all URIs, but the contents are only compressed if the size of the response body exceeds 100
bytes.
If content is compressed, the Content-Encoding header and the Vary header are included in the response message. The Cont
ent-Encoding header reports the used encoding method to the client. Similarly, the Vary header reports that the response body
was changed because of compression. However, if the encoding method is identity, the response message does not include
the Content-Encoding header and the Vary header.
The following shows the Content-Encoding header and the Vary header included in the response message if content is
compressed by using the gzip encoding method:
Content-Encoding:
gzip Vary: Accept-Encoding
Common objects
The following common objects can be used independently of API resources. Note that the items in the field for all JSON objects
(including common objects) are displayed in random order.
Collection object
The Collection object is used to contain a set of objects to be returned. The following table describes the schema of the Colle
ction object.
Variable name Type Description
Error object
If an error occurs in a request, both an Error object defined by the schema in the following table and a status code are returned.
However, note that for API that return Job objects, the Job object might be returned depending on where the error occurred.
actions string array Actions that the API client must take
{"errorSource": "[Link]
1&agentInstanceName=instance1",
"message": "The specified agent does not exist. (agent type = RAID, instance name = instance1, h
ost name = HOST1)",
"messageID": "KNAQ35000-E",
"actions":["Check whether the agent information for the specified agent exists."]}
Action object
The Action object is a container for the parameters for executing an action of a resource or service. The following table
describes the schema of the Action object.
type string The media type specified in the Content-Type header of the request
to execute the action
Variable name Type Description
parameters PrimitiveValue object array The parameters needed for executing the action.
The number of elements and the meaning of each element are defined
for each action (API).
PrimitiveValue object
The PrimitiveValue object is a container that is used to treat a non-object variable as an object. The following table describes
the schema of the PrimitiveValue object.
{ "type" : "string",
"value" : "Agent" }
The following table lists and describes API resources and requests for accessing RAID Agent. Note that the resources are
indicated by their URLs.
API functions that obtain performance data collected via a command device1, 2
This request
PD_PEFF GET /<application>/v1/objects/RAID_PD_PEFF Obtaining
obtains the
records performance
performance data
data
indicating the ratio
of the total saving
effect (excluding
system data)
achieved by
accelerated PD_SEFF GET /<application>/v1/objects/RAID_PD_SEFF
compression, records
capacity saving,
snapshot, and
Dynamic
Provisioning.
API functions that obtain performance data collected via an SVP (by using a TCP/IP connection)1, 3
Other APIs
Notes:
1. Outputs the record information corresponding to the type of object specified in object-type under the objects domain.
2. If the Access Type is 3 or 4, some values can be obtained via the REST API.
For details, see Types of performance information that can be acquired depending on the Access Type.
3. If the Access Type is 2 or 4, some values can be obtained via the REST API.
For details, see Types of performance information that can be acquired depending on the Access Type.
4. In the following cases, records are not created. For this reason, performance data cannot be obtained by using the API.
If performance data is collected by using RAID Agent bundled with Ops Center Analyzer
If performance data is collected by using Tuning Manager - Agent for RAID and the value of the log setting has
not been changed from the default value (No)
Obtaining the RAID Agent list parameter when the manual refresh process is executed
You can obtain the parameter that is necessary for executing the manual refresh process for the RAID Agent list.
For an action provided by the Ops Center Analyzer API, this API function returns (to the API client) the Action object whose default
value has been specified in the parameters field. This Action object can be used, without change, as an argument of the API
described in Manually refreshing the RAID Agent list.
GET <scheme>://<host>:<port>/<application>/<version>/services/AgentManager/actions/refresh
Request structure
Not applicable.
Response structure
{
"name":"RefreshAgentInstancesParameters",
"url":"<scheme>://<host>:<port>/<application>/<version>/services/AgentManager/actions/refres
h/invoke",
"method":"POST",
"type":"application/json",
"parameters":[{"type":"string","value":"All"}]
}
Example (obtaining the RAID Agent list parameter when the manual refresh process is executed)
Request header
Response header
HTTP/1.1 200 OK
Date: Thu, 19 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: application/json;charset=utf-8
Response body
{
"name":"RefreshAgentInstancesParameters",
"url":"[Link]
nvoke",
"method":"POST",
"type":"application/json",
"parameters":[{"type":"string","value":"All"}]
}
Related reference
Manually refreshing the RAID Agent list
When you change any configuration settings in RAID Agent such as monitored storage systems or instance information, you must
manually refresh the list information in RAID Agent before acquiring performance data.
POST <scheme>://<host>:<port>/<application>/<version>/services/AgentManager/actions/refresh/invo
ke
Request structure
{
"name" : "RefreshAgentInstancesParameters",
"url" : "<scheme>://<host>:<port>/<application>/<version>/services/AgentManager/actions/refr
esh/invoke",
"method" : "POST",
"type" : "application/json",
"parameters" : [ { ... } ]
}
The following table shows the values that can be specified in parameters.
Variable name Value Number of Description
arguments
parameters type string: Indicates the 1 If more than two arguments are
variable type. specified, the arguments after the
first argument are ignored.
Response structure
{"status":"Completed"}
When the update processing completes normally, the response body includes the Job objects indicated in the following table. If
an error occurs, the response body might include the Job object or the Error object, depending on the cause of the error. The
response body object can be determined from the status code.
errorID string The information that uniquely identifies the error that occurred.
If an error occurs, the same string as the error ID output to the log is
set. This variable is not added if processing ends normally.
If an error occurs, the same string that is output to the log is set. This
variable is not added if processing ends normally.
Request header
Response header
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: application/json;charset=utf-8
Response body
{"status":"Completed"}
GET <scheme>://<host>:<port>/<application>/<version>/objects/Agents?<query-string>
Query string
agentType=RAID
The following table describes the key and values of the query strings that can be specified when obtaining a list of RAID Agent
instances.
agentType Specify either "ALL" or "RAID". The agent type of RAID Agent Yes
Request structure
Not applicable.
Response structure
{
"items":[{
"agentType":"RAID",
"instanceName":"...",
"hostName":"...",
"ipAddr":"...",
"dataModelVersion":...,
"storageVendor":"...",
"storageModel":"...",
"storageSerialNumber":"..."
"lastUpdateTime":"...",
},
:
:
]
}
The following table describes the format of the data included in the response body.
The following table lists and describes the schema for the Agents objects.
hostName Y string The monitoring host name of the host that runs
the RAID Agent
lastUpdateTime Y string The last time the RAID Agent information was
successfully updated.
Legend:
Y: Displayed
* Virtual storage systems are not included in the storage system being monitored.
Request header
Response header
HTTP/1.1 200 OK
Date: Mon, 28 Sep 2015 [Link] GMT
Server: Cosminexus HTTP Server
Last-Modified: Mon, 28 Sep 2015 [Link] GMT
Cache-Control: no-cache
X-Frame-Options: SAMEORIGIN
Transfer-Encoding: chunked
Content-Type: application/json;charset=utf-8
Response body
{
"items":[{
"agentType":"RAID",
"instanceName":"MONITOR1",
"hostName":"esxi4VM02",
"ipAddr":"<IP-address-of-MONITOR1>",
"dataModelVersion":0.0,
"storageVendor":"HITACHI",
"storageModel":"VSP G1000",
"storageSerialNumber":"10051",
"lastUpdateTime":"2015-09-09T[Link]Z"
}]
}
Request structure
Not applicable.
Response structure
{
"items":[{
"instanceName":"...",
"hostName":"...",
"ipAddr":"...",
"dataModelVersion":"...",
"lastUpdateTime":"...",
"storageVendor":"...",
"storageModel":"...",
"storageSerialNumber":"..."
},
:
:
]
}
The following table describes the format of the data included in the response body.
Object name
Number of objects Description
The following table lists and describes the schema for the AgentForRAID objects.
hostName string The monitoring host name of the host that runs the RAID Agent
ipAddr string The IP address of the host on which the RAID Agent is operating
lastUpdateTime string The last time the RAID Agent information was successfully updated.
* Virtual storage systems are not included in the storage system being monitored.
Request header
Response header
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Last-Modified: Fri, 20 Jun 2014 [Link] GMT
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: application/json;charset=utf-8
Response body
{
"items":[{
"instanceName":"VSPG1000_instance",
"hostName":"agent_1",
"ipAddr":"<IP-address-of-agent_1>",
"dataModelVersion":0.0,
"storageVendor":"HITACHI",
"storageModel":"VSP G1000",
"storageSerialNumber":"10051",
"lastUpdateTime":"2014-06-20T[Link]Z"
},
:
:
{
"instanceName":"HUSVM_instance",
"hostName":"agent_2",
"ipAddr":"<IP-address-of-agent_2>",
"dataModelVersion":0.0,
"storageVendor":"HITACHI",
"storageModel":"HUS VM",
"storageSerialNumber":"210944",
"lastUpdateTime":"2014-06-20T[Link]Z"
}]
}
You can obtain the performance data that RAID Agent collected from the monitored targets. Note that performance data is
provided in CSV format.
GET <scheme>://<host>:<port>/<application>/<version>/objects/<object-type>?<query-string>
Additional note
The object-type under the objects domain is formated as "RAID_record-name". For example, if the object-typ
e is RAID_PD_RGC, you can obtain the PD_RGC record information from RAID Agent.
For query-string, enter a key and its value in pairs in the key=value format. You can enter multiple query strings.
To enter multiple query strings, use an ampersand (&) as a separator. An example of specifying the query strings is
indicated in "Query string". In addition, the keys and types of values that can be specified are indicated in
"Specifiable keys and values in the query strings for obtaining performance data". Note that query strings must be
percent-encoded.
Query string
hostName=HOST
&agentInstanceName=AgentInstance
&startTime=2013-12-01T13:00Z
&endTime=2013-12-01T15:00Z
&fields=RECORD_TIME%1FLDEV_NUMBER%1FRANDOM_TOTAL_IO_RATE
&LDEV_NUMBER=[Link]
&LDEV_NUMBER=[Link]
Table. Specifiable keys and values in the query strings for obtaining performance data
hostName Host name The name of the RAID Agent host Yes
agentInstanceN RAID Agent instance name The value that uniquely identifies a RAID Yes
ame Agent instance
value = year-month-dayThour:mi
nuteZ2
endTime1 Same as startTime (Example: endTim The end time (in UTC) of the period for No
e=2013-11-21T19:54Z) which performance data is to be obtained
fields A value that has the following convention Record field names No
can be specified.
For details, see RAID Agent records
value = 1*VCHAR / value (collection via the command device) and
RAID Agent records (collection via the
%1Fvalue;2 SVP by using a TCP/IP connection).
record-field-name A value that follows the following Specify the name of a field as a key, and No
convention can be specified. the value of the field as the value for the
key.
value = *VCHAR ; 2, 5
granularity Specify raw or specify no value. When no The time granularity of the performance No
value is specified, raw is assumed. Note data to be obtained
that this value is not case-sensitive.
accessMode Specify s. Note that this value is not Obtaining data by executing a query No
case-sensitive.
Notes:
Specify both startTime and endTime, or neither of them. You cannot specify only one of these keys.
If you specify neither startTime nor endTime, the performance data of the latest date (for one snapshot) is
returned.
Key Value Required
3. If multiple values can be specified for a key, you can separate the values by %1F, and you can also specify the values by
specifying the same key name on multiple lines. These different notations have the same meaning. The different
notations can be mixed in one request.
fields=WRITE_IO_COUNT%1FWRITE_XFER_RATE
LDEV_NUMBER=[Link]%[Link]
fields=WRITE_IO_COUNT&fields=WRITE_XFER_RATE
LDEV_NUMBER=[Link]&LDEV_NUMBER=[Link]
Request structure
Not applicable.
Response structure
The response body contains performance data in CSV format. The following table describes the variables used in the response
body.
An extra delimiter is added to the end of the data to show that the data ends.
SelectedFieldValue_lm The value of a specific field that is selected by the function that selects data to be obtained1,
2, 3, 4
Notes:
Request header
GET /Analytics/RAIDAgent/v1/objects/RAID_PD?
hostName=agent_1%26agentInstanceName=VSPG1000_instance HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: curl/7.19.7 (i386-redhat-linux-gnu) libcurl/7.19.7
NSS/[Link] zlib/1.2.3 libidn/1.18 libssh2/1.2.2
Host: server_1:22016
Accept: */*
Response header
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Last-Modified: Fri, 20 Jun 2014 [Link] GMT
Keep-Alive: timeout=3, max=100
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: text/csv;charset=utf-8
X-Pad: avoid browser bug
Response body
DKC_SERIAL_NUMBER,VENDOR_ID,DKC_NAME,CACHE_MEMORY_CAPACITY,CACHE_MEMORY_INSTALLED_SIZE,MONITORED
_SLPR_NUMBER,COLLECTION_TIME,INTERVAL,INPUT_RECORD_TYPE,RECORD_TIME
string(32),string(64),string(64),ulong,ulong,string(8),time_t,ulong,string(8),time_t
"10051","HITACHI","VSP G1000",469504,0,"",2014-06-20 [Link],3600,"PD",2014-06-20 [Link]
Request header
GET /Analytics/RAIDAgent/v1/objects/RAID_PI_LDS?
hostName=agent_1%26agentInstanceName=VSPG1000_instance HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: curl/7.19.7 (i386-redhat-linux-gnu) libcurl/7.19.7
NSS/[Link] zlib/1.2.3 libidn/1.18 libssh2/1.2.2
Host: server_1:22016
Accept: */*
Response header
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Last-Modified: Fri, 20 Jun 2014 [Link] GMT
Keep-Alive: timeout=3, max=100
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: text/csv;charset=utf-8
X-Pad: avoid browser bug
Response body
LDEV_NUMBER,READ_IO_COUNT,READ_IO_RATE,READ_HIT_IO_COUNT,READ_HIT_RATE,WRITE_IO_COUNT,WRITE_IO_R
ATE,WRITE_HIT_IO_COUNT,WRITE_HIT_RATE,READ_MBYTES,READ_XFER_RATE,WRITE_MBYTES,WRITE_XFER_RATE,RE
AD_TOTAL_RESPONSE,READ_RESPONSE_RATE,WRITE_TOTAL_RESPONSE,WRITE_RESPONSE_RATE,TOTAL_RESPONSE_RAT
E,RANDOM_TOTAL_IO_RATE,SEQUENTIAL_TOTAL_IO_RATE,RANDOM_TOTAL_XFER_RATE,SEQUENTIAL_TOTAL_XFER_RAT
E,VIRTUAL_SERIAL_NUMBER,VIRTUAL_DKC_NAME,VIRTUAL_LDEV_NUMBER,INTERVAL,INPUT_RECORD_TYPE,RECORD_T
IME
string(16),ulong,float,ulong,float,ulong,float,ulong,float,ulong,float,ulong,float,double,float,
double,float,float,float,float,float,float,string(32),string(32),string(16),ulong,string(8),time
_t
"[Link]",0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,
0,0.0000000E+000,0.000000000000000E+000,0.0000000E+000,0.000000000000000E+000,0.0000000E+000,0.0
000000E+000,0.0000000E+000,0.0000000E+000,0.0000000E+000,0.0000000E+000,"","","",301,"LDS",2014-
06-20 [Link]
"[Link]",0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,
0,0.0000000E+000,0.000000000000000E+000,0.0000000E+000,0.000000000000000E+000,0.0000000E+000,0.0
000000E+000,0.0000000E+000,0.0000000E+000,0.0000000E+000,0.0000000E+000,"","","",301,"LDS",2014-
06-20 [Link]
"[Link]",0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,
0,0.0000000E+000,0.000000000000000E+000,0.0000000E+000,0.000000000000000E+000,0.0000000E+000,0.0
000000E+000,0.0000000E+000,0.0000000E+000,0.0000000E+000,0.0000000E+000,"","","",301,"LDS",2014-
06-20 [Link]
:
:
"[Link]",0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,0,0.0000000E+000,
0,0.0000000E+000,0.000000000000000E+000,0.0000000E+000,0.000000000000000E+000,0.0000000E+000,0.0
000000E+000,0.0000000E+000,0.0000000E+000,0.0000000E+000,0.0000000E+000,"","","",301,"LDS2",2014
-06-20 [Link]
Request header
GET /Analytics/RAIDAgent/v1/objects/RAID_PD_PTC?
hostName=agent_1%26agentInstanceName=VSPG1000_instance HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: curl/7.19.7 (i386-redhat-linux-gnu) libcurl/7.19.7
NSS/[Link] zlib/1.2.3 libidn/1.18 libssh2/1.2.2
Host: server_1:22016
Accept: */*
Response header
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Last-Modified: Fri, 20 Jun 2014 [Link] GMT
Keep-Alive: timeout=3, max=100
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: text/csv;charset=utf-8
X-Pad: avoid browser bug
Response body
PORT_NUMBER,PORT_NAME,CHA_NAME,PORT_WWN,PORT_TYPE,PORT_ROLE,PORT_SPEED,SLPR_NUMBER,COLLECTION_TI
ME,INTERVAL,INPUT_RECORD_TYPE,RECORD_TIME
string(8),string(64),string(16),string(32),string(8),string(16),string(8),string(8),time_t,ulon
g,string(8),time_t
"0","CL1-A","CHA-1EU","50060E8007274300","FIBRE","Target","Auto","",2014-06-20 [Link],3600,"PT
C",2014-06-20 [Link]
"1","CL1-B","CHA-1EU","50060E8007274301","FIBRE","Target","Auto","",2014-06-20 [Link],3600,"PT
C",2014-06-20 [Link]
"2","CL1-C","CHA-1EL","50060E8007274302","FIBRE","External","8Gbps","",2014-06-20 [Link],360
0,"PTC",2014-06-20 [Link]
"3","CL1-D","CHA-1EL","50060E8007274303","FIBRE","Target","Auto","",2014-06-20 [Link],3600,"PT
C",2014-06-20 [Link]
:
:
"116","CL8-E","CHA-2RU","","FICON","Target","","",2014-06-20 [Link],3600,"PTC",2014-06-20 12:0
0:07
"117","CL8-F","CHA-2RU","","FICON","Target","","",2014-06-20 [Link],3600,"PTC",2014-06-20 12:0
0:07
"118","CL8-G","CHA-2RL","50060E8007274376","FCoE","Target","10Gbps","",2014-06-20 [Link],360
0,"PTC",2014-06-20 [Link]
"119","CL8-H","CHA-2RL","50060E8007274377","FCoE","Target","10Gbps","",2014-06-20 [Link],360
0,"PTC",2014-06-20 [Link]
Example 4 (when obtaining the PI_PRCS record information by specifying startTime and
endTime)
Request header
GET /Analytics/RAIDAgent/v1/objects/RAID_PI_PRCS?
hostName=agent_1%26agentInstanceName=VSPG1000_instance
%26startTime=2014-06-19T01:00Z%26endTime=2014-06-19T02:30Z HTTP/1.1
Authorization: Basic c3lzdGVtOm1hbmFnZXI=
User-Agent: curl/7.19.7 (i386-redhat-linux-gnu) libcurl/7.19.7
NSS/[Link] zlib/1.2.3 libidn/1.18 libssh2/1.2.2
Host: server_1:22016
Accept: */*
Response header
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Last-Modified: Thu, 19 Jun 2014 [Link] GMT
Keep-Alive: timeout=3, max=100
Cache-Control: private, max-age=864000
Transfer-Encoding: chunked
Content-Type: text/csv;charset=utf-8
Response body
PROCESSOR_ID,ADAPTOR_ID,CONTROLLER,PROCESSOR_TYPE,PROCESSOR_BUSY_RATE,MAX_PROCESSOR_BUSY_RATE,MA
X_BUFFER_LENGTH,BUFFER_IO_COUNT,MAX_BUFFER_IO_COUNT,BUFFER_IO_RATE,MAX_BUFFER_IO_RATE,INTERVAL,I
NPUT_RECORD_TYPE,RECORD_TIME
string(16),string(16),string(8),string(8),float,float,float,float,float,float,float,ulong,string
(8),time_t
"00","MPB0","","MP",8.8735523E-001,8.8735523E-001,6.5535002E+004,1.0000000E+000,1.0000000E+000,
1.5259022E-003,1.5259022E-003,54,"PRCS",2014-06-19 [Link]
"01","MPB0","","MP",1.2086518E+000,1.2086518E+000,6.5535002E+004,1.0000000E+000,1.0000000E+000,
1.5259022E-003,1.5259022E-003,54,"PRCS",2014-06-19 [Link]
"02","MPB0","","MP",9.0272198E-001,9.0272198E-001,6.5535002E+004,1.0000000E+000,1.0000000E+000,
1.5259022E-003,1.5259022E-003,54,"PRCS",2014-06-19 [Link]
:
:
"2E","MPB5","","MP",3.0648675E+000,3.0648675E+000,6.5535002E+004,1.0000000E+000,1.0000000E+000,
1.5259022E-003,1.5259022E-003,61,"PRCS",2014-06-19 [Link]
"2F","MPB5","","MP",3.1383426E+000,3.1383426E+000,6.5535002E+004,1.0000000E+000,1.0000000E+000,
1.5259022E-003,1.5259022E-003,61,"PRCS",2014-06-19 [Link]
"_Total","MPB5","","MPB",3.0528414E+000,3.0528414E+000,6.5535002E+004,1.0000000E+000,1.0000000E+
000,1.5259022E-003,1.5259022E-003,61,"PRCS",2014-06-19 [Link]
For all actions available in RAID Agent, this API function stores the Action objects for the objects with omitted parameter fields
to the Collection object, and then returns the object to the API client. You can use this Collection object (list of actions) to
find out what kinds of actions are available.
GET <scheme>://<host>:<port>/<application>/<version>/services/AgentManager/actions
Request structure
Not applicable.
Response structure
{
"items":[{"name":"<action-name>",
"url":"<URI-of-the-action>",
"method":"<HTTP-method-used-to-execute-the-action>",
"type":"<media-type-specified-in-the-Content-Type-header-of-the-request-to-execute-the-a
ction>"
}]
}
The following table describes the format of the data included in the response body.
Request header
Response header
HTTP/1.1 200 OK
Date: Thu, 19 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Cache-Control: no-cache
Transfer-Encoding: chunked
Content-Type: application/json;charset=utf-8
Response body
{
"items":[{"name":"RefreshAgentInstancesParameters",
"url":"[Link]
sh/invoke",
"method":"POST",
"type":"application/json"
}]
}
You can obtain the detailed version information of the API that accesses RAID Agent.
GET <scheme>://<host>:<port>/<application>/<version>/configuration/Version
Request structure
Not applicable.
Response structure
The configuration of the response body is as follows:
{
"productName":"<product-name>",
"productVersion":"<product-version>",
"apiVersion":"<api-version>",
"description":"<explanation-of-the-API-version>"
}
The following table describes the format of the data included in the response body.
apiVersion string The version of the API that accesses the RAID Agent.
description string Description of the version of the API that accesses the RAID Agent.
Request header
Response header
HTTP/1.1 200 OK
Date: Thu, 19 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Last-Modified: Thu, 29 May 2014 [Link] GMT
Cache-Control: private, max-age=86400
Transfer-Encoding: chunked
Content-Type: application/json;charset=utf-8
Response body
{
"productName": "Hitachi Ops Center Analyzer",
"productVersion": "10.00.00",
"apiVersion": "1.0",
"description": "The initial version for supporting RAID Agent API"
}
Obtaining metadata
You can obtain the metadata for JSON objects that are used by data-acquisition API resources (for example, the API resource for
obtaining a list of RAID Agent instances) other than the resource for obtaining performance data. The representation of metadata
follows the JSON Schema. Note that the metadata for resources that obtain performance data is always provided together with
CSV headers. You cannot obtain only metadata.
GET <scheme>://<host>:<port>/<application>/<version>/domain-types/<object-type>
Request structure
Not applicable.
Response structure
The schema follows the JSON Schema for the individual object.
The following shows the configuration of the response body received when metadata on the AgentForRAID object is obtained.
Request header
HTTP/1.1 200 OK
Date: Fri, 20 Jun 2014 [Link] GMT
Server: Cosminexus HTTP Server
Last-Modified: Thu, 29 May 2014 [Link] GMT
Cache-Control: private, max-age=86400
Transfer-Encoding: chunked
Content-Type: application/schema+json;charset=utf-8
Response body
Records starting with PD are of the PD (product detail) record type. PD-type records collect performance data, information
indicating the system status at a certain time (such as detailed information about processes that are currently running).
You can use PD-type records to identify the status of the system at a certain time.
Records starting with PI are of the PI (product interval) record type. PI-type records collect performance data over a fixed
interval, such as the number of processes that are running per minute. You can use PI-type records to analyze the changes
or trends in the system status over time.
Records are listed in alphabetical order. Each record includes the following information.
Function
Provides an overview of the performance data that is stored in the record and includes important notes.
Collection Interval
Key Fields
Indicates fields that work as keys to identify an instance of a multi-instance record. There are two types of key fields: those
common to all records, and those unique to a record. Key Fields only indicates the fields unique to the record.
Lifetime
Indicates the period during which consistency is guaranteed for the performance data that is collected in the record.
Fields
Provides a table that describes the fields of each record. The table contains the following items.
Reserved fields are indicated by "--" in columns other than the Field Name column or the Description column.
Field Name
Description
Format
Delta
In contrast to data collected as cumulative values, data that indicates the amount of difference between values is called
the delta.
Data Source
Source of the obtained value. If the field value is the result of a calculation based on the values of other fields, the formula
used is shown in the Data Source column. For example, if the Data Source column of a field shows READ_IO_COUNT / I
NTERVAL, the value of the READ_IO_COUNT field of this record is divided by the value of the INTERVAL field (of the same
record), and the resulting value is stored in this field.
"--" means that the method used to obtain the field value or the source of the value is not disclosed.
Related reference
List of common key fields
List of data types
Delta
The following table lists key fields that are common to all records. For details about key fields specific to particular records, see
the descriptions of those records.
DEVICEID Names of the instance and host on which the RAID Agent is running
m: Minute
Field name Description
H: Hour
D: Day
W: Week
M: Month
Y: Year
TIME The time when the record was created (in GMT)
The following table lists the data types for field values and the corresponding C and C++ data types. The values shown in the
Format column of each field table are those shown below in the Field column under Data type.
Field C or C++
string(n) char[ ] Number in Character string with a length of n bytes. The last
parentheses character is null.
timeval Various structures 8 Numeric value (first 4 bytes are seconds, next 4 bytes are
microseconds)
utime Various structures 8 Numeric value (first 4 bytes are seconds, next 4 bytes are
microseconds)
Data type Bytes Description
Field C or C++
Delta
The difference between the values of the previously collected data and currently collected data for the performance data of a field
is called delta. The data source of the field is the information that is managed as cumulative values.
For example, suppose a field whose data source is a counter for I/O processing, where the counter value obtained during the first
collection is 3 and the counter value obtained during the second collection is 7. The output value of this field at the second
collection is 7 (the counter value at the second collection) if the delta attribute is not applied to the field or 4 (the difference
between the first value and the second value) if the delta attribute is applied to the field.
As shown in the following table, which performance data values are collected varies depending on the conditions.
Record type Delta Data source Does the data source include fields for Value
which (Delta = Yes)?
Yes
Because performance data of the PI record type includes data (such as delta values) that requires differences from data
obtained during the previous collection, data from two or more collections is required. This means that the amount of time
required to store performance data in a Performance database (RAID Agent database) from the time when the RAID Agent
service starts is, at a maximum, twice the time that is set for Collection Interval.
For example, if you start RAID Agent whose performance data collection interval is set to 300 seconds (5 minutes) at 6:32
PM, the first data collection will start at 6:35 PM. However, the record to be stored in the Performance database is not
created at this time, because the data required for calculating the difference does not exist. At the next data collection
(which starts at 6:40 PM), performance data will be created based on the data collected at 6:35 PM and 6:40 PM, and then
stored in the Performance database.
If you change the time on a machine on which RAID Agent is installed, performance data is collected as follows:
When the time on a computer is changed to a time that is earlier than the last time the RAID Agent collected
performance data
The performance data that was previously collected from the new set time to the last collection time is overwritten.
When the time on a computer is changed to a time that is later than the present time
The performance data ranging from the currently set time to the new set time is not collected.
For notes specific to each record, see the explanation of each record.
When using RAID Agent bundled with Ops Center Analyzer to monitor VSP E series, VSP 5000 series, VSP G350, G370, G700,
G900, VSP F350, F370, F700, F900 storage systems, the type of performance information that can be acquired and the path via
which the information is acquired varies depending on the Access Type you specify when you configure an instance.
Access Type Path via which RAID Agent acquires performance information
4: REST-API
Via the REST API (by using a TCP/IP connection)
Note that, in the following cases, RAID Agent acquires the performance information collected via both the command device and
the SVP (by using a TCP/IP connection).
When RAID Agent bundled with Ops Center Analyzer is used to monitor storage systems for models other than the
following: VSP E series, VSP 5000 series, VSP G350, G370, G700, G900, VSP F350, F370, F700, F900
When Tuning Manager - Agent for RAID is used
The performance information that can be acquired via the REST API (by using a TCP/IP connection) is the same as the
performance information that can be acquired via the command device or via the SVP (by using a TCP/IP connection). As such,
information on whether performance information can be collected via the REST API (by using a TCP/IP connection) for a
particular record or field is provided in RAID Agent records (collection via the command device) or RAID Agent records (collection
via the SVP by using a TCP/IP connection).
Storage systems in the VSP N series are equivalent to those in the VSP F series or VSP G series. As such, the values that can be
acquired for VSP N series by using RAID Agent are the same as those that can be acquired for VSP F series and VSP G series.
Descriptions of storage system models in the VSP F series or VSP G series also apply to the corresponding storage system
models in the VSP N series.
The following table lists each model in the VSP N series and the corresponding model in the VSP F series or VSP G series.
Storage system model in the VSP N series Corresponding storage system model in the VSP F series or
VSP G series
Restrictions regarding volumes, ports and parity group for mainframe systems
Some restrictions apply when you monitor volumes, ports and parity group used for mainframe systems.
Restrictions when monitoring volumes and parity group for mainframe systems
When a logical device has an emulation type used for mainframe systems, some performance data cannot be obtained. For
details, see the following tables.
Table. Records that are not supported when monitoring volumes and parity group for mainframe systems (for VSP 5000 series)
Access Type
Record ID Field
1 2 3 4
PI_LDE RANDOM_READ_XFER_RATE N1 N1 N2 N2
RANDOM_WRITE_XFER_RATE
SEQUENTIAL_READ_XFER_RATE
SEQUENTIAL_WRITE_XFER_RATE
PI_LDS RANDOM_TOTAL_XFER_RATE N1 N1 N2 N2
SEQUENTIAL_TOTAL_XFER_RATE
PI_LDSX -- Y N2 Y N2
PI_RGS RANDOM_READ_XFER_PCT N1 N1 N2 N2
RANDOM_READ_XFER_RATE
RANDOM_TOTAL_XFER_RATE
Access Type
Record ID Field
1 2 3 4
RANDOM_WRITE_XFER_PCT
RANDOM_WRITE_XFER_RATE
SEQUENTIAL_READ_XFER_PCT
SEQUENTIAL_READ_XFER_RATE
SEQUENTIAL_TOTAL_XFER_RATE
SEQUENTIAL_WRITE_XFER_PCT
SEQUENTIAL_WRITE_XFER_RATE
Legend:
Y: Can be collected
N: Cannot be collected
Notes:
1. The value is 0.
2. This record is not created.
Table. Records that are not supported when monitoring volumes for mainframe systems (for VSP G1000 (80-03 or later), G1500,
and VSP F1500)
Record ID Field
PI_LDE RANDOM_READ_XFER_RATE
RANDOM_WRITE_XFER_RATE
SEQUENTIAL_READ_XFER_RATE
SEQUENTIAL_WRITE_XFER_RATE
PI_LDS RANDOM_TOTAL_XFER_RATE
SEQUENTIAL_TOTAL_XFER_RATE
Record ID Field
PI_RGS RANDOM_READ_XFER_PCT
RANDOM_READ_XFER_RATE
RANDOM_TOTAL_XFER_RATE
RANDOM_WRITE_XFER_PCT
RANDOM_WRITE_XFER_RATE
SEQUENTIAL_READ_XFER_PCT
SEQUENTIAL_READ_XFER_RATE
SEQUENTIAL_TOTAL_XFER_RATE
SEQUENTIAL_WRITE_XFER_PCT
SEQUENTIAL_WRITE_XFER_RATE
Table. Records that are not supported when monitoring volumes for mainframe systems (for VSP G1000 (earlier than 80-03))
Record ID Field
PI_LDE RANDOM_READ_XFER_RATE
PI_LDA
RANDOM_WRITE_XFER_RATE
SEQUENTIAL_READ_XFER_RATE
SEQUENTIAL_WRITE_XFER_RATE
READ_MBYTES
READ_XFER_RATE
WRITE_MBYTES
WRITE_XFER_RATE
PI_LDS RANDOM_TOTAL_XFER_RATE
Record ID Field
READ_MBYTES
READ_RESPONSE_RATE
READ_TOTAL_RESPONSE
READ_XFER_RATE
SEQUENTIAL_TOTAL_XFER_RATE
TOTAL_RESPONSE_RATE
WRITE_MBYTES
WRITE_RESPONSE_RATE
WRITE_TOTAL_RESPONSE
WRITE_XFER_RATE
PI_PLS READ_RESPONSE_RATE
READ_XFER_RATE
WRITE_RESPONSE_RATE
WRITE_XFER_RATE
PI_RGS RANDOM_READ_XFER_PCT
RANDOM_READ_XFER_RATE
RANDOM_TOTAL_XFER_RATE
RANDOM_WRITE_XFER_PCT
RANDOM_WRITE_XFER_RATE
READ_MBYTES
Record ID Field
READ_AVG_RESPONSE
READ_TOTAL_RESPONSE
READ_XFER_PCT
READ_XFER_RATE
SEQUENTIAL_READ_XFER_PCT
SEQUENTIAL_READ_XFER_RATE
SEQUENTIAL_TOTAL_XFER_RATE
SEQUENTIAL_WRITE_XFER_PCT
SEQUENTIAL_WRITE_XFER_RATE
TOTAL_RESPONSE_RATE
WRITE_MBYTES
WRITE_AVG_RESPONSE
WRITE_TOTAL_RESPONSE
WRITE_XFER_PCT
WRITE_XFER_RATE
For ports that are used to connect to mainframe systems, there are some fields for which configuration information and
performance data cannot be collected, depending on certain storage system and port attributes. Note that, regarding the PI_PTSX
record, you cannot collect performance data about mainframe systems, irrespective of the storage system or port attributes. The
PI_MPTS record is not created for ports with FNP attributes.
Table. Records that are not supported when monitoring ports for mainframe systems (for VSP 5000 series)
Access Type
Record ID Field
1 2 3 4
PD_PTC PORT_WWN N1 Y Y Y
Access Type
Record ID Field
1 2 3 4
PI_PTS -- Y Y N2 N2
Legend:
Y: Can be collected
N: Cannot be collected
Notes:
Table. Records Whose Field Values Are Always 0 When Monitoring Ports for Mainframes (for VSP G1000 (earlier than 80-03) or for
ports with FNP attributes)
Record ID Field
PI_PTS AVG_IO_RATE
AVG_XFER_RATE
MAX_IO_RATE
MAX_XFER_RATE
MIN_IO_RATE
MIN_XFER_RATE
The following table lists the I/O types and whether performance information can be collected by RAID Agent when a program for
managing storage systems is used.
Program name I/O Type Types of performance Can/cannot collect performance information of each
information resource subject to I/O loads
Legend:
Y: Can be collected
* When monitoring a logical device that is not mapped to a port or when monitoring a parity group to which the logical device
belongs, the value of Unassigned Open Volume Monitoring must be Y or y.
The table below describes whether performance data for each resource can be obtained for an environment that uses VVols of
VMware.
Resources Can/cannot collect Values that can be collected and those that cannot be collected
performance information
Port Y Each of the following values can be collected as the total value for the
port:
Legend:
Y: Can be collected
The following figure shows the configuration when a global-active device is used. Also, the following table shows whether
performance data can be collected for each resource within the figure.
I/O type Resources Can/cannot Values that can be Resource Configuration figure
collect collected location number
performance data
I/O from the Target port Y Displays the I/O from the Primary 1
host host for both read and site/Secondary
write. site
I/O to the Initiator port Y Not only the I/O of the Primary 3
remote site copy pair for a global- site/Secondary
active device but the site
performance value of the
entire LU connected to the
port.
Legend:
Y: Can be collected
When Compatible PAV or Compatible Hyper PAV is used, records for base volumes can be obtained, but records for alias volumes
cannot be obtained.
In addition to I/O performance information for base volumes, performance information in base volumes also contains I/O
performance information for alias volumes.
The following describes the record creation results in cases where the data to be stored in a field cannot be obtained. If an error
occurs during performance data collection, or if a field that is not supported by the monitored system is included in the created
record, the record creation results are as follows:
Records are not created when any of the following conditions are met:
RAID Agent cannot acquire the performance data to be stored in a field defined as a key field.
RAID Agent cannot acquire the performance data to be stored in a field containing performance information about
RAID Agent.
RAID Agent takes longer than the time specified for Collection Interval while acquiring performance data.
Records containing blank fields are created if RAID Agent cannot acquire performance data to be stored in a character-
type field that contains RAID Agent configuration information.
Records containing fields with a value of 0 are created when RAID Agent cannot acquire performance data to be stored in
a numeric-type field that contains RAID Agent configuration information.
If a pool is configured by a parity group for which accelerated compression is enabled, there is a function that automatically adds
pool volumes that pool. If this function is enabled, the logical capacity will increase automatically. To check the capacity of a pool
configured by a parity group for which accelerated compression is enabled, check the physical capacity of the pool.
Note:
To check whether to automatically add pool volumes according to the compression ratio of a parity group for which accelerated
compression is enabled, you can check the detailed pool information displayed in the Auto Expansion field in E2E View.
PI record type
48 hours
PD record type
The retention period varies with the record. The following table shows the retention periods.
PD_CLPC 168
PD_ELC 168
PD_LDC 168
PD_LSEC 168
PD_PEFF 8784
PD_PLC 8784
PD_PLF 168
Record ID Retention period (unit: hours)
PD_PLR 744
PD_PLTR 744
PD_PLTC 744
PD_PLTS 744
PD_PTC 168
PD_RGC 168
PD 168
PD_PDX 168
PD_SEFF 8784
PD_UMSX 168
PD_UMS 168
PD_VVF 168
PD_VVTC 744
PD_VVC 744
This Appendix describes the records that can be collected via the command device. Note that if VMware Fault Tolerance (VMware
vSphere(R) Fault Tolerance) is used, performance data cannot be collected via command devices.
Furthermore, if the Access Type is 3 or 4, some values can be obtained via the REST API.
For details, see Types of performance information that can be acquired depending on the Access Type.
PD
The PD record stores the performance data indicating the detailed information of the storage system.
Collection Interval
3600
Key Field
None
Lifetime
Fields
The PD_CLPC record stores performance data indicating the CLPR configuration information. This is a multi-instance record. If the
Access Type is 3 or 4, this record will not be created.
Collection Interval
3600
Key Field
CLPR_NUMBER
Lifetime
From when the CLPR is defined to when it is deleted, or to when its definition is changed.
Fields
PD_ELC
The PD_ELC record holds performance data indicating configuration information for an externally connected LDEV (logical
device). This is a multi-instance record. If the Access Type is 3 or 4, this record will not be created.
Note: If there are no externally connected LDEVs mapped in external storage systems, this report cannot be used.
Collection Interval
3600
Key Field
LDEV_NUMBER
Lifetime
Fields
Notes:
1. If virtual IDs are set for volumes in an externally connected storage system, the RAID Agent collects the virtual ID
information.
Field Name Description Format Delta Data Source
2. If the externally connected storage system is VSP E series or VSP Fx00 model, the value is VSP Gx00. For example, if the
externally connected storage system is VSP F400, the value is VSP Gx00.
3. Not supported by HUS VM storage system.
4. If the externally connected storage system is VSP G1000, the value stored in the DKC_NAME field is VSP G1000 G1500
F1500.
PD_LDC
The PD_LDC record stores the performance data indicating the configuration information of the logical device. This is a multi-
instance record.
Collection Interval
3600
Key Field
LDEV_NUMBER
Lifetime
Fields
Internal
Field Name Description Format Delta Data Source
External
LUSE
ExampleRAID5(3D+1P)
RAID1(4D+4D)
RAID1(2D+2D)x2
VIRTUAL_DKC_NAME9, 10, 11, 12, 14, 15 Product name of the virtual storage string(32) No --
system to which the logical device
belongs
VIRTUAL_SERIAL_NUMBER9, 10, 11, 15 Serial number (in decimal) of the virtual string(32) No --
storage system to which the logical
Field Name Description Format Delta Data Source
device belongs
V-VOL
POOL
Notes:
1. If the logical device is a component of a LUSE, this field only stores the record for the following logical device:
If the LUSE consists of externally connected logical devices, or logical devices of V-VOLs for Copy-on-Write
Snapshot/Thin Image or Dynamic Provisioning, and no LU path is set for the LUSE, the LUSE is not recognized and
records are created for individual logical devices. In this case, the PD_LSEC record is not created for individual logical
devices.
2. Tuning Manager - Agent for RAID does not collect information about Copy-on-Write Snapshot pools or Thin Image pools.
When the pool to which the logical device belongs is blocked, this field becomes empty. However, when the pool is
blocked because the usage rate of the pool capacity is 100%, a value is stored in this field.
3. The value cannot be collected when the logical device is a Dynamic Provisioning V-VOL.
4. The value cannot be collected when the logical device is a Copy-on-Write Snapshot V-VOL or a Thin Image V-VOL.
5. The value cannot be collected if the logical device is an externally connected LDEV.
6. The field value is always 0 when the logical device is a Copy-on-Write Snapshot V-VOL or a Thin Image V-VOL.
7. The field value is always 0 when the logical device is a Dynamic Provisioning V-VOL.
8. If the logical device is an externally connected LDEV, the field value will always be 0.
9. If the logical device does not belong to a virtual storage system, the field value will be NULL.
10. The value cannot be collected for the following storage systems: HUS VM.
11. If the logical device that composes a copy pair of global-active device is not virtualized, the field value will be NULL.
12. If the virtual storage system is VSP F400 or VSP F600, the value is VSP G400 G600. If the virtual storage system is VSP
F800, the value is VSP G800.
13. If either of the following applies to the logical device, the field value will be NULL.
The logical device that is part of a copy pair of a global-active device is not virtualized.
A virtualized logical device number is not set.
14. If the virtual storage system is VSP G1000, the value stored in the VIRTUAL_DKC_NAME field is VSP G1000 G1500
F1500.
15. If the Access Type is 3 or 4, the information in this field is not obtained.
PD_LSEC
The PD_LSEC record holds performance data indicating configuration information for logical devices that make up the LUSE. This
is a multi-instance record.
Collection Interval
In the following cases, this record will not be created.
If the LUSE consists of externally connected logical devices, or logical devices of V-VOLs for Copy-on-Write Snapshot/Thin
Image or Dynamic Provisioning, and no LU path is set for the LUSE
If no LUSE exists in the storage system
If the Access Type is 3 or 4
3600
Key Field
LDEV_NUMBER
Lifetime
Fields
Internal
External
device belongs.
Example:
RAID5(3D+1P)
V-VOL
Notes:
1. When the Dynamic Provisioning pool to which the logical device belongs is blocked, this field becomes empty. However,
when the Dynamic Provisioning pool is blocked because the usage rate of the pool capacity is 100%, a value is stored in
this field.
2. The value cannot be collected if the logical device is externally connected.
3. The value cannot be collected when the logical device is a Copy-on-Write Snapshot V-VOL or a Thin Image V-VOL.
4. The value cannot be collected when the logical device is a Dynamic Provisioning V-VOL.
Field Name Description Format Delta Data Source
5. If the logical device is an externally connected LDEV, the field value will always be 0.
6. The field value is always 0 when the logical device is a Copy-on-Write Snapshot V-VOL or a Thin Image V-VOL.
7. The field value is always 0 when the logical device is a Dynamic Provisioning V-VOL.
PD_PEFF
The PD_PEFF record stores performance data indicating the ratio of the total saving effect (excluding system data) achieved by
accelerated compression, capacity saving (deduplication and compression), snapshot, and Dynamic Provisioning for the pool.
This is a multi-instance record.
Note:
Tuning Manager - Agent for RAID does not collect information about Copy-on-Write Snapshot pools and Thin Image pools.
If the Dynamic Provisioning pool is blocked, RAID Agent does not collect information about the Dynamic Provisioning pool.
However, if the Dynamic Provisioning pool is blocked because the usage rate of the pool capacity is 100%, RAID Agent
collects information about the pool.
Collection Interval
3600
Key Field
POOL_ID
Lifetime
Fields
CALCULATION_END_TIME The end date and time for calculating (in string(32) No --
4
UTC)
CALCULATION_START_TIME The start date and time for calculating (in string(32) No --
UTC)4
Notes:
1. A record cannot be created for storage systems other than VSP E series, VSP 5000 series, VSP G350, G370, G700, G900,
VSP F350, F370, F700, F900.
2. If a value cannot be obtained, the field value becomes one of the following:
If the micro-version is earlier than 88-03-01, the value is -1.
If the calculation is not complete, the value is -2.
If the information is invalid, the value is -3.
3. Under certain circumstances, the field value can display as 99999 (for example: before data has been written to newly-
created pool or virtual volume).
4. Times are displayed in YYYY-MM-DD hh:mm:ss format. If a value cannot be obtained, an empty character string ("") is
displayed.
5. If the Access Type is 3 or 4, the information in this field is not obtained.
PD_PLC
The PD_PLC record stores performance data that indicates the operation status of Dynamic Provisioning pools, Copy-on-Write
Snapshot pools, and Thin Image pools. This is a multi-instance record.
Note:
Tuning Manager - Agent for RAID does not collect information about Copy-on-Write Snapshot pools or Thin Image pools.
If the pool is blocked, RAID Agent does not collect information about the pool. However, if the pool is blocked because the
usage rate of the pool capacity is 100%, RAID Agent collects information about the pool.
Collection Interval
3600
Key Field
POOL_ID
Lifetime
Fields
Field Name Description Format Delta Data Source
Dynamic Provisioning
Dynamic Provisioning
(Tiering)
Data Direct Mapping
Thin Image
Enabled
Disabled
""
0x00
Deduplication Not
Available11
0x02
Deduplication Not
Available11
0x03
Deduplication Available
Field Name Description Format Delta Data Source
Notes:
If the pool contains a parity group for which accelerated compression is also enabled, the amount includes the
capacity of the expanded area.
5. This value is not exactly the same as the device capacity information that is recognized by the host because this
capacity information is managed by the storage system.
6. If the pool contains a parity group for which accelerated compression is also enabled, the value is the amount after
compression.
7. If the total amount of pool volumes created from parity groups that support the accelerated compression function is less
than the physical capacity of the parity groups that support the accelerated compression function, the value is always
100. If a parity group that supports the accelerated compression function does not exist, the value is 0.
8. For the values to be displayed, see the manual of the storage system being used.
9. If the pool contains a parity group for which accelerated compression is also enabled, the value is the amount that
includes the capacity of the expanded area.
10. If the settings of the capacity saving function (deduplication and compression) are enabled, the amount is the amount
actually used after the size of the capacity is reduced. Note that if the pool contains a parity group for which accelerated
compression is also enabled, the value does not include the compressed amount.
11. For both 0x00 and 0x02, the deduplication function is disabled.
12. The capacity used by the deduplication system data volume is not included.
13. The saved amount does not include the amount of metadata and garbage data.
14. The saved capacity includes the amount of zero data reduction, metadata, and garbage data. If you are using VSP G200,
G400, G600, G800, VSP F400, F600, F800, VSP G1000 (earlier than version 80-06-21), G1500 (earlier than version 80-06-
21), or VSP F1500 (earlier than version 80-06-21), the saved capacity does not includes the amount of zero data
reduction, metadata, and garbage data.
15. When the capacity saving function (deduplication and compression) is used, the saving ratio is calculated against the
amount of metadata and garbage data generated internally in addition to user data.
16. The compressed capacity with the accelerated compression function for VSP G200, G400, G600, G800, VSP F400, F600,
F800, VSP G1000 (earlier than version 80-06-21), G1500 (earlier than version 80-06-21), or VSP F1500 (earlier than
version 80-06-21).
If the Access Type is 3 or 4, the compressed capacity with the accelerated compression function for VSP G350, G370,
G700, G900, VSP F350, F370, F700, F900 (earlier than version 88-03-01).
17. Reduction rate (%) of capacity compressed by the accelerated compression function for VSP G200, G400, G600, G800,
VSP F400, F600, F800, VSP G1000 (earlier than version 80-06-21), G1500 (earlier than version 80-06-21), or VSP F1500
(earlier than version 80-06-21).
If the Access Type is 3 or 4, reduction rate (%) of capacity compressed by the accelerated compression function for
VSP G350, G370, G700, G900, VSP F350, F370, F700, F900 (earlier than version 88-03-01).
18. The saved capacity includes the amount of zero data reduction, metadata, garbage data, metadata reduction, and
garbage data reduction.
19. A value cannot be obtained for storage systems other than VSP E series, VSP 5000 series, VSP G350, G370, G700, G900,
VSP F350, F370, F700, F900, VSP G1000 (versions 80-06-21 and later), G1500 (versions 80-06-21 and later), and VSP
F1500 (versions 80-06-21 and later). If a value cannot be obtained, the value -1 is used.
20. If the capacity after the reduction becomes larger than the capacity before the reduction, the value is -2, which indicates
an invalid value.
21. If the data reduction function is disabled or the timing is just after a pool is created or a volume is deleted, the value
might be -2 which indicates an invalid value. If the reduction is highly effective (the capacity after the reduction is close
to 0), the value will be 99999.
22. The saved capacity includes the amount of metadata reduction and garbage data reduction.
23. When the data reduction function is used, the saving ratio is calculated against the amount of metadata, garbage data
and parity data generated internally in addition to user data.
24. If the Access Type is 3 or 4, the information in this field is not obtained.
25. If the Access Type is 1 or 2, a value cannot be obtained for storage systems other than VSP E series, VSP 5000 series,
VSP G350, G370, G700, G900, VSP F350, F370, F700, F900, VSP G1000 (versions 80-06-41 and later), G1500 (versions
80-06-41 and later), and VSP F1500 (versions 80-06-41 and later).
If the Access Type is 3 or 4, a value cannot be obtained for storage systems other than VSP E series, VSP 5000 series
(versions 90-01-42 and later), VSP G350, G370, G700, G900, VSP F350, F370, F700, and F900 (versions 88-03-29 and
later).
PD_PLF
The PD_PLF record stores performance data indicating the page I/O processing status of the Dynamic Provisioning pool. If the Ac
cess Type is 3 or 4, this record will not be created.
Note:
Information about Copy-on-Write Snapshot pools, Thin Image pools, and Dynamic Provisioning pools that do not have tier
management enabled is not collected.
If the Dynamic Provisioning pool is blocked, RAID Agent does not collect information about the pool. However, if the
Dynamic Provisioning pool is blocked because the usage rate of the pool capacity is 100%, RAID Agent collects
information about the pool.
Performance data is saved whenever monitoring information for the storage system is updated. If you collect records
immediately after RAID Agent starts, the system might collect the same data it collected earlier.
Information about Dynamic Provisioning pools is not collected if monitoring information has never been collected by the
storage system.
If RAID Agent is collecting records when the storage system is aggregating monitoring information, the collecting of
records is canceled, and the KAVF18514-W message is output to the common log.
If you stop and then restart the RAID Agent, monitoring information that covers the same time period might be stored
twice.
Collection Interval
3600
Key Fields
Lifetime
From the time when tiers are set up in a Dynamic Provisioning pool with tier management enabled to when they are removed.
Fields
Notes:
PD_PLR
The PD_PLR record stores performance data indicating the progress of tier relocations for Dynamic Provisioning pools that have
tier management enabled. This is a multi-instance record. If the Access Type is 3 or 4, this record will not be created.
Note:
Information about Copy-on-Write Snapshot pools, Thin Image pools, and Dynamic Provisioning pools that do not have tier
management enabled is not collected.
RAID Agent does not collect information about a blocked Dynamic Provisioning pool except when the pool is blocked
because of its usage rate reaching 100%.
Performance data is saved whenever tier relocation information for the storage system is updated. If you collect
performance data immediately after RAID Agent starts, the data that was collected the last time might be saved again.
Information about Dynamic Provisioning pools is not collected if tier relocation information has never been collected by
the storage system.
If RAID Agent is collecting records when the storage system is aggregating monitoring information, the collecting of
records is canceled, and the KAVF18514-W message is output to the common log.
Collection Interval
3600
Key Field
POOL_ID
Lifetime
From the time when a Dynamic Provisioning pool that has tier management enabled and tiers are set up until the time they are
removed.
Fields
COLLECTION_TIME Time (in GMT) that the data was collected time_t No --
from the storage system
Field Name Description Format Delta Data Source
Notes:
1. Depending on the current status of data placement among the tiers, the amount of time required for tier relocation (as
predicted by the progress percentage) might not match the actual time required.
2. The time of the storage system is obtained.
3. The value is displayed in YYYY/MM/DD hh:mm:ss format.
4. Times are displayed in hh:mm:ss format.
PD_PLTC
The PD_PLTC record stores performance data indicating the operation status for each tier type of a Dynamic Provisioning pool
that has tier management enabled. This is a multi-instance record. If the Access Type is 3 or 4, this record will not be created.
Note:
RAID Agent does not collect information about a Copy-on-Write Snapshot pool or a Thin Image pool, or a Dynamic
Provisioning pool that has tier management disabled.
If the Dynamic Provisioning pool is blocked, RAID Agent does not collect information about the pool. However, if the
Dynamic Provisioning pool is blocked because the usage rate of the pool capacity is 100%, RAID Agent collects
information about the pool.
The capacity information for this record is not exactly the same as the device capacity information that is recognized by
the host because this capacity information is managed by the storage system.
Collection Interval
3600
Key Fields
Lifetime
From when the tier and a Dynamic Provisioning pool that has tier management enabled are set up to when it is removed.
Fields
Period Mode
Continuous Mode
Notes:
1. If the total amount of pool volumes created from parity groups that support the accelerated compression function is less
than the physical capacity of the parity groups that support the accelerated compression function, the value is always
100.
2. If a parity group that supports the accelerated compression function does not exist, the value is 0.
3. Not supported by HUS VM.
4. If the pool contains a parity group for which accelerated compression is also enabled, the value is the amount that
includes the capacity of the expanded area.
5. A value is stored only when the pool contains a parity group for which accelerated compression is also enabled. In other
cases, the value is 0.
6. If the pool contains a parity group for which accelerated compression is also enabled, the value is the amount before
compression.
7. If the pool contains a parity group for which accelerated compression is also enabled, the value is the amount after
compression.
8. FMC is the value to be stored when the drive type is FMC, FMD DC2, or FMD HDE. SSD Mixed is the value to be stored
when different types of flash drives exist.
PD_PLTR
The PD_PLTR record stores performance data indicating the number of pages moved by tier relocations for Dynamic Provisioning
pools that have tier management enabled. This is a multi-instance record. If the Access Type is 3 or 4, this record will not be
created.
Note:
Information about Copy-on-Write Snapshot pools, Thin Image pools, and Dynamic Provisioning pools that do not have tier
management enabled is not collected.
RAID Agent does not collect information about a blocked Dynamic Provisioning pool except when the pool is blocked
because of its usage rate reaching 100%.
Performance data is saved whenever tier relocation information for the storage system is updated. If you collect
performance data immediately after RAID Agent starts, the data that was collected the last time might be saved again.
Information about Dynamic Provisioning pools is not collected if tier relocation information has never been collected by
the storage system.
If RAID Agent is collecting records when the storage system is aggregating monitoring information, the collecting of
records is canceled, and the KAVF18514-W message is output to the common log.
Collection Interval
3600
Key Fields
Lifetime
From the time when a Dynamic Provisioning pool that has tier management enabled and tiers are set up until the time they are
removed.
Fields
COLLECTION_TIME Time (in GMT) that the data was collected time_t No --
from the storage system
Notes:
PD_PLTS
The PD_PLTS record stores performance data indicating the operation status for each tier type of a Dynamic Provisioning pool
that has tier management enabled. This is a multi-instance record. If the Access Type is 3 or 4, this record will not be created.
Note:
RAID Agent does not collect information about a Copy-on-Write Snapshot pool, a Thin Image pool, or a Dynamic
Provisioning pool that has tier management disabled.
If the Dynamic Provisioning pool is blocked, RAID Agent does not collect information about the pool. However, if the
Dynamic Provisioning pool is blocked because the usage rate of the pool capacity is 100%, RAID Agent collects
information about the pool.
Performance data is stored only when the monitoring information for the storage system is updated. However, if you
collect the record immediately after RAID Agent starts, the same data that was collected last might be stored.
Information about the Dynamic Provisioning pool is not collected if monitoring information has never been collected in the
storage system.
If the storage system aggregates monitoring information while RAID Agent is collecting records, the collection of the
records is canceled. In this case, the KAVF18514-W message is output to the common log.
Collection Interval
3600
Key Fields
Lifetime
From when the tier and a Dynamic Provisioning pool that has tier management enabled are set up to when it is removed.
Fields
Field Name Description Format Delta Data Source
COLLECTION_TIME Time (in GMT) that the data was collected time_t No --
from the storage system
RECORD_TIME Time (in GMT) that the record was stored time_t No --
Notes:
Field Name Description Format Delta Data Source
1. If the monitoring mode of the Dynamic Provisioning pool is Continuous Mode, the value is predicted based on the trends
of past performance values.
2. Times are obtained from the storage system.
3. Times are displayed in YYYY/MM/DD hh:mm:ss format.
4. FMC is the value to be stored when the drive type is FMC, FMD DC2, or FMD HDE. SSD Mixed is the value to be stored
when different types of flash drives exist.
PD_PTC
The PD_PTC record stores the performance data indicating the configuration information of the port of the storage system. This is
a multi-instance record.
Collection Interval
Note:
The items in (1) and (2) below all have the same field name (PORT_NUMBER), but the values output to the items in (1) are different
from those output to the items in (2).
For this reason, if you want to check whether the port information of one record matches that of another, check the PORT_NAME
field.
3600
Key Field
PORT_NUMBER
Lifetime
Fields
Example:
Target
Initiator
RCU Target
External
Bidirectional
(Null string) : If the port type is
FICON
Notes:
1. The value cannot be collected if the type of port on the storage system is FICON.
2. The value can be collected only when the type of the port on the storage system is FIBRE or FCoE.
3. If the Access Type is 3 or 4, the information in this field is not obtained.
4. If you are monitoring a VSP 5000 series storage system and the Access Type is 1, you cannot collect values for
mainframe systems.
PD_RGC
The PD_RGC record holds performance data indicating configuration information for a parity group. This is a multi-instance
record. The following records are not generated:
Records for external volume groups or virtual volume groups (Copy-on- Write Snapshot, Thin Image, and Dynamic
Provisioning virtual volume groups)
Records for parity groups without a logical device
Collection Interval
3600
Key Field
RAID_GROUP_NUMBER
Lifetime
Fields
ExampleRAID5(3D+1P)
RAID1(4D+4D)
Example when the Access Type
is 3 or 4
RAID1(2D+2D)x2
Notes:
PD_SEFF
The PD_SEFF record stores performance data indicating the ratio of the total saving effect (excluding system data) achieved by
accelerated compression, capacity saving (deduplication and compression), snapshot, and Dynamic Provisioning for the storage
system.
Collection Interval
3600
Key Field
None
Lifetime
Fields
CALCULATION_END_TIME The end date and time for calculating (in string(32) No --
4
UTC)
CALCULATION_START_TIME The start date and time for calculating (in string(32) No --
UTC)4
Notes:
1. A record cannot be created for storage systems other than VSP E series, VSP 5000 series, VSP G350, G370, G700, G900,
VSP F350, F370, F700, F900.
2. If a value cannot be obtained, the field value becomes one of the following:
If the micro-version is earlier than 88-03-01, the value is -1.
If the calculation is not complete, the value is -2.
If the information is invalid, the value is -3.
3. Under certain circumstances, the field value can display as 99999 (for example: before data has been written to newly-
created pool or virtual volume).
4. Times are displayed in YYYY-MM-DD hh:mm:ss format. If a value cannot be obtained, an empty character string ("") is
displayed.
5. If the Access Type is 3 or 4, the information in this field is not obtained.
PD_UMS
The PD_UMS record stores performance data indicating the 20 highest activity rates for the resources allocated to each MP Blade.
If the Access Type is 3 or 4, this record will not be created.
Collection Interval
300
Key Fields
Lifetime
Fields
For LDEVs
For journals
For LDEVs
LDEV
Journal
External Volume
PD_VVC
The PD_VVC record stores performance data indicating the operation status of the V-VOL for Dynamic Provisioning. This is a
multi-instance record.
Note:
Information about Copy-on-Write Snapshot V-VOLs, Thin Image V-VOLs, and the V-VOLs that are not associated with the
Dynamic Provisioning pool is not collected.
If the Dynamic Provisioning pool to which the Dynamic Provisioning V-VOL belongs is blocked, RAID Agent does not collect
information about the V-VOL. However, if the Dynamic Provisioning pool is blocked because the usage rate of the pool
capacity is 100%, RAID Agent collects information about the V-VOL.
Collection Interval
3600
Key Field
LDEV_NUMBER
Lifetime
Fields
Field Name Description Format Delta Data Source
If Full Allocation is
enabled
Full Allocation
(Null string)
0x00
Disabled
0x02
0x03
Inline
Inline mode.
Post-process
Post-process mode.
Field Name Description Format Delta Data Source
""
Example:
Notes:
PD_VVF
The PD_VVF record stores performance information indicating the page I/O status for the virtual volumes mapped to the Dynamic
Provisioning pool. If the Access Type is 3 or 4, this record will not be created.
Note:
Information about Copy-on-Write Snapshot pools, Thin Image pools, and Dynamic Provisioning pools that do not have tier
management enabled is not collected.
RAID Agent does not collect information about a blocked Dynamic Provisioning pool except when the pool is blocked
because of its usage rate reaching 100%.
RAID Agent does not collect information about the V-VOLs that are not associated with the Dynamic Provisioning pool.
Performance data is saved whenever tier relocation information for the storage system is updated. If you collect
performance data immediately after RAID Agent starts, the data that was collected the last time might be saved again.
Information about Dynamic Provisioning pools is not collected if tier relocation information has never been collected by
the storage system.
If RAID Agent is collecting records when the storage system is aggregating monitoring information, the collecting of
records is canceled, and the KAVF18514-W message is output to the common log.
If you stop and then restart the RAID Agent, monitoring information that covers the same time period might be stored
twice.
Collection Interval
3600
Key Fields
LDEV_NUMBER and PARTITION_NUMBER
Lifetime
From when a virtual volume is set up in a Dynamic Provisioning pool with tier management enabled to when the volume is
removed.
Fields
Notes:
The PD_VVTC record stores performance data indicating the operation status of the virtual volume for each tier type of a Dynamic
Provisioning pool that has tier management enabled. This is a multi-instance record. If the Access Type is 3 or 4, this record will
not be created.
Note:
RAID Agent does not collect information about a Copy-on-Write Snapshot V-VOL, a Thin Image V-VOL, or a Dynamic
Provisioning V-VOL that has tier management disabled.
If the Dynamic Provisioning pool to which the Dynamic Provisioning V-VOL belongs is blocked, RAID Agent does not collect
information about the V-VOL. However, if the Dynamic Provisioning pool is blocked because the usage rate of the pool
capacity is 100%, RAID Agent collects information about the V-VOL.
RAID Agent does not collect information about the V-VOLs that are not associated with the Dynamic Provisioning pool.
Collection Interval
3600
Key Fields
Lifetime
From the time the Dynamic Provisioning V-VOL that has tier management enabled is set up to when it is removed.
Fields
Notes:
1. This value is not exactly the same as the device capacity information that is recognized by the host because this
capacity information is managed by the storage system.
2. FMC is the value to be stored when the drive type is FMC, FMD DC2, or FMD HDE. SSD Mixed is the value to be stored
when different types of flash drives exist.
PI
The PI record stores the performance data indicating the operation status of the storage system.
Collection Interval
60
Key Field
None
Lifetime
Fields
pending data.
Notes:
1. This field stores the value that was the most recent at the time that the record was created.
2. Not supported by VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, or HUS VM storage systems.
3. If the Access Type is 3 or 4, the information in this field is not obtained.
PI_CHS
The PI_CHS record stores performance data indicating the aggregate value of the port performance information for each CHA in a
storage system. If the Access Type is 3 or 4, this record will not be created.
Collection Interval
60
Key Field
CHA_NAME
Lifetime
Fields
* If the port type is ESCON or FICON, this value can be collected only when the storage system is VSP 5000 series, VSP G1000
(80-03 or later), G1500, or VSP F1500.
PI_CLMS
The PI_CLMS record stores performance data indicating the write pending rate and cache memory of the CLPR for each MP Blade
in a storage system. This is a multi-instance record.
Collection Interval
60
Key Fields
Lifetime
From the time when the MP Blade and CLPR are set up until the time they are removed
Fields
MP blade of the
MP_BLADE_ID field.
PI_CLPS
The PI_CLPS record stores performance data indicating the operation status of the cache memory for each CLPR. This is a multi-
instance record.
Collection Interval
60
Key Field
CLPR_NUMBER
Lifetime
From when the CLPR is defined to when it is deleted, or to when its definition is changed.
Fields
--
CACHE_SIDE_FILE_RATE This field cannot be used -- --
because it is reserved.
by write-pending data
(MB).1
Notes:
1. This field stores the value that was the most recent at the time the record was created.
2. If the Access Type is 3 or 4, the information in this field is not obtained.
PI_JNLS
The PI_JNLS record stores performance data indicating the operation status of the journal group. If the Access Type is 3 or 4,
this record will not be created.
Collection Interval
300
Key Field
JOURNAL_ID
Lifetime
Fields
PI_LDA
The PI_LDA record stores the performance data indicating the values summarizing the execution status of read and write
operations on the logical devices for each storage system. If the Access Type is 3 or 4, this record will not be created.
Note: If the logical devices were excluded from the monitoring targets during the setup of the RAID Agent instance environment,
information about those logical devices will not be applied to this record.
Collection Interval
300
Key Field
None
Lifetime
Fields
* For logical devices for which the mainframe emulation type is set, this value can be collected only when the storage system is
VSP 5000 series, VSP G1000 (80-03 or later), G1500, or VSP F1500.
PI_LDE
The PI_LDE record stores performance data indicating the execution status of random and sequential read and write operations
on the logical device. This is a multi-instance record.
Note that if you are monitoring a VSP 5000 series storage system and the Access Type is 3 or 4, you cannot collect
performance information about mainframe systems.
PI_LDS
Key Field
LDEV_NUMBER
Lifetime
Fields
Notes:
1. If the logical device is an externally connected LDEV, the field value will always be 0.
2. The field value is always 0 when the logical device is a Copy-on-Write Snapshot V-VOL or a Thin Image V-VOL.
3. The field value is always 0 when the logical device is a Dynamic Provisioning V-VOL.
4. If the logical device is a component of a LUSE, the value of LDEV_NUMBER indicates the logical device number of the
first logical device of the LUSE.
Each performance information field contains statistics on random and sequential read or write operations performed on
the entire logical device group that makes up the LUSE. No record is created for individual logical devices that are
included in the LUSE. If the LUSE consists of externally connected logical devices, or logical devices of V-VOLs for Copy-
on-Write Snapshot/Thin Image or Dynamic Provisioning, and no LU path is set for the LUSE, the LUSE is not recognized
and records are created for individual logical devices.
5. This field is not supported for logical devices for which the mainframe emulation type is set.
6. If the logical device does not belong to a virtual storage system, the field value will be NULL.
7. The value cannot be collected for the following storage systems: HUS VM.
8. If the logical device that composes a copy pair of global-active device is not virtualized, the field value will be NULL.
9. If the virtual storage system is VSP F400 or VSP F600, the value is VSP G400 G600. If the virtual storage system is VSP
F800, the value is VSP G800.
10. If either of the following applies to the logical device, the field value will be NULL.
The logical device that is part of a copy pair of a global-active device is not virtualized.
A virtualized logical device number is not set.
11. For storage systems other than those of the following models, if the storage system has a built-in flash drive (FMD, FMC,
or SSD), the value displayed as the usage rate of the parity groups of the flash drive might be higher than the actual
usage rate, regardless of the load on the flash drive: VSP 5000 series, VSP Gx00, VSP Fx00, VSP G1000, G1500, and VSP
F1500.
For such storage systems, do not use as reference the value displayed as the usage rate of the parity groups of the flash
drive.
12. If the virtual storage system is VSP G1000, the value stored in the VIRTUAL_DKC_NAME field is VSP G1000 G1500
F1500.
13. If the Access Type is 3 or 4, the information in this field is not obtained.
14. Depending on the logical device number, one of the following values is used: LDE, LDE1, LDE2, or LDE3.
PI_LDS
The PI_LDS record stores the performance data indicating the execution status of read and write operations on the logical device.
This is a multi-instance record.
Note that if you are monitoring a VSP 5000 series storage system and the Access Type is 3 or 4, you cannot collect
performance information about mainframe systems.
Collection Interval
300
Key Field
LDEV_NUMBER
Lifetime
Fields
READ_XFER_RATE3 Read data transfer rate (MB per float No READ_MBYTES / INTERVAL
second).
VIRTUAL_DKC_DETAIL_NAME
This field cannot be used -- -- --
because it is reserved.
--
WRITE_HIT_RATE This field cannot be used -- --
because it is reserved.
Notes:
1. If the logical device is a component of a LUSE, the value of LDEV_NUMBER indicates the logical device number of the
first logical device of the LUSE.
Each performance information field contains statistics on the read or write operations performed on the entire logical
device group that makes up the LUSE. No record is created for individual logical devices that are included in the LUSE. If
the LUSE consists of externally connected logical devices, or logical devices of V-VOLs for Copy-on-Write Snapshot/Thin
Image or Dynamic Provisioning, and no LU path is set for the LUSE, the LUSE is not recognized and records are created
for individual logical devices.
2. This field is not supported for logical devices for which the mainframe emulation type is set.
3. For logical devices for which the mainframe emulation type is set, this value can be collected only for VSP 5000 series,
VSP G1000 (80-03 or later), G1500, or VSP F1500 storage systems.
4. If the logical device does not belong to a virtual storage system, the field value is NULL.
5. The value cannot be collected for the following storage systems: HUS VM.
6. If the logical devices that compose a global-active device copy pair are not virtualized, the field value will be NULL.
7. For VSP F400 or VSP F600 virtual storage systems, the value is VSP G400 G600. For VSP F800 vitual storage systems,
the value is VSP G800.
8. If either of the following applies to the logical device, the field value will be NULL.
The logical device is part of a global-active device copy pair, and is not virtualized.
No virtualized logical device number is set for the logical device.
9. For a VSP G1000 virtual storage system, the value stored in the VIRTUAL_DKC_NAME field is VSP G1000 G1500 F1500.
10. If the Access Type is 3 or 4, the information in this field is not obtained.
11. Depending on the logical device number, one of the following values is used: LDS, LDS1, LDS2, or LDS3.
PI_PLS
The PI_PLS record stores performance data indicating the operation status of the Dynamic Provisioning pool. This is a multi-
instance record. If the Access Type is 3 or 4, this record will not be created.
Note: RAID Agent does not collect information about Copy-on-Write Snapshot pools and Thin Image pools.
Collection Interval
300
Key Field
POOL_ID
Lifetime
Fields
Notes:
1. Performance values do not include information about virtual volumes that are used as S-VOLs of Thin Image.
2. The field value is 0 when the mainframe emulation type is set for a Dynamic Provisioning pool and the Mainframe
Volume Monitoring value for that pool is N.
3. For Dynamic Provisioning pools for which the mainframe emulation type is set, this value can be collected only for when
the storage system is VSP 5000 series, VSP G1000 (80-03 or later), G1500, or VSP F1500.
PI_PLTI
The PI_PLTI record stores performance data indicating the execution status of read and write processing for each type of tier for
Dynamic Provisioning pools that have tier management enabled. This is a multi-instance record. If the Access Type is 3 or 4,
this record will not be created.
Note:
Information about Copy-on-Write Snapshot pools, Thin Image pools and Dynamic Provisioning pools that do not have tier
management enabled is not collected.
RAID Agent does not collect information about a blocked Dynamic Provisioning pool except when the pool is blocked
because of its usage rate reaching 100%.
Collection Interval
900
Key Fields
Lifetime
From the time when a Dynamic Provisioning pool that has tier management enabled is set up until the time when the pool is
removed.
Fields
RECORD_TIME Time (in GMT) that the data was collected time_t No --
from the storage system and the record
was generated
* FMC is the value to be stored when the drive type is FMC, FMD DC2, or FMD HDE. SSD Mixed is the value to be stored when
different types of flash drives exist.
PI_PRCS
The PI_PRCS record stores performance data indicating the operation status of the on-board processor of the storage system.
This is a multi-instance record.
Collection Interval
60
Key Fields
Lifetime
Fields
Field Name Description Format Delta Data Source
Notes:
1. For VSP G1000, G1500, or VSP F1500, if the value in the PROCESSOR_TYPE field is MPB, the value in the field is the
average of the Buffer IO performance values of all the microprocessors in the MP blade. For VSP E series, VSP 5000
series, VSP Gx00 models, VSP Fx00 models, or HUS VM storage system, if the value in the PROCESSOR_TYPE field is MP
B, the value in the field is the average of the Buffer IO performance values of all the microprocessors in the MP unit.
2. For VSP G1000, G1500, or VSP F1500, the value in the PROCESSOR_BUSY_RATE field is the average activity rate of all the
microprocessors in the MP blade if the value in the PROCESSOR_TYPE field is MPB. For VSP E series, VSP 5000 series,
VSP Gx00 models, VSP Fx00 models, or HUS VM storage system, the value in the PROCESSOR_BUSY_RATE field is the
average activity rate of all the microprocessors in the MP unit if the value in the PROCESSOR_TYPE field is MPB.
3. For VSP G1000, G1500, VSP F1500, or HUS VM, the value in the PROCESSOR_ID field is _Total if the value in the
PROCESSOR_TYPE field is MPB.
4. If the Access Type is 3 or 4, the information in this field is not obtained.
PI_PTS
The PI_PTS record stores the performance data indicating the read and write status of each port of the storage system. This is a
multi-instance record.
Collection Interval
Note that if you are monitoring a VSP 5000 series storage system and the Access Type is 3 or 4, you cannot collect
performance information about mainframe systems.
Note:
The items in (1) and (2) below all have the same field name (PORT_NUMBER), but the values output to the items in (1) are different
from those output to the items in (2).
For this reason, if you want to check whether the port information of one record matches that of another, check the PORT_NAME
field.
60
Key Field
PORT_NUMBER
Lifetime
Notes:
1. If the port type is ESCON or FICON, this value can be collected only for when the storage system is VSP 5000 series, VSP
G1000 (80-03 or later), G1500, or VSP F1500.
2. If the value of the PORT_ROLE field is not Bidirectional, the value will be 0.
3. If the storage system is VSP G1000, G1500, VSP F1500, or HUS VM, the value cannot be collected.
4. If the Access Type is 3 or 4, the information in this field is not obtained.
5. If the value set for Collection Interval is greater than 60, the value will be an average value.
PI_RGS
The PI_RGS record holds performance data indicating the execution status of read or write operations on a parity group. This is a
multi-instance record. The following records are not generated:
Records for external volume groups or virtual volume groups (Copy-on-Write Snapshot, Thin Image, and Dynamic
Provisioning virtual volume groups)
Records for parity groups without a logical device
Note that if you are monitoring a VSP 5000 series storage system and the Access Type is 3 or 4, you cannot collect
performance information about mainframe systems.
Collection Interval
300
Key Field
RAID_GROUP_NUMBER
Lifetime
Fields
READ_XFER_RATE3, 4 Read data transfer rate (MB per double No READ_MBYTES / INTERVAL
second)
WRITE_XFER_RATE3, 4 Write data transfer rate (MB per double No WRITE_MBYTES / INTERVAL
second)
Notes:
Field Name Description Format Delta Data Source
1. For storage systems other than those of the following models, if the storage system has a built-in flash drive (FMD, FMC,
or SSD), the value displayed as the usage rate of the parity groups of the flash drive might be higher than the actual
usage rate, regardless of the load on the flash drive: VSP 5000 series, VSP Gx00, VSP Fx00, VSP G1000, G1500, and VSP
F1500.
For such storage systems, do not use as reference the value displayed as the usage rate of the parity groups of the flash
drive.
2. This field is not supported for parity groups that include a logical device for which the mainframe emulation type is set.
3. For parity groups that include a logical device for which the mainframe emulation type is set, this value can be collected
only when the storage system is VSP 5000 series, VSP G1000 (80-03 or later), G1500, or VSP F1500.
4. If the Access Type is 3 or 4, the information in this field is not obtained.
PI_VVTI
The PI_VVTI record stores performance data indicating the execution status of read and write processing for each type of tier for
Dynamic Provisioning V-VOLs that have tier management enabled. This is a multi-instance record. If the Access Type is 3 or 4,
this record will not be created.
Note:
Information about Copy-on-Write Snapshot V-VOLs, ThinImage V-VOLs, and Dynamic Provisioning V-VOLs that do not have
tier management enabled is not collected.
RAID Agent does not collect information about a Dynamic Provisioning V-VOL that belongs to a blocked Dynamic
Provisioning pool except when the pool is blocked because of its usage rate reaching 100%.
Information about V-VOLs that are not associated with Dynamic Provisioning pools is not collected.
Collection Interval
900
Key Fields
Lifetime
From the time when a Dynamic Provisioning V-VOL that has tier management enabled is set up until the time when the V-VOL is
removed.
Fields
RECORD_TIME Time (in GMT) that the data was collected time_t No --
from the storage system and the record
was generated
* FMC is the value to be stored when the drive type is FMC, FMD DC2, or FMD HDE. SSD Mixed is the value to be stored when
different types of flash drives exist.
RAID Agent records (collection via the SVP by using a TCP/IP connection)
Certain records can be collected via the SVP by using a TCP/IP connection. Note that, when records are collected via the SVP by
using a TCP/IP connection, performance values do not include certain values (such as peformance values for pool volumes for
which I/O processing from servers does not occur).
Furthermore, if the Access Type is 2 or 4, some values can be obtained via the REST API.
For details, see Types of performance information that can be acquired depending on the Access Type.
PD_PDX
The PD_PDX record stores the performance data indicating the detailed information of the storage system. If the Access Type is
2 or 4, this record will not be created.
Collection Interval
3600
Key Field
None
Lifetime
Fields
Field Name Description Format Delta Data Source
PD_UMSX
The PD_UMSX record stores the performance data indicating the 100 highest activity rates for the resources allocated to each MP
Blade. If the Access Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
Fields
Example: MPB0
Field Name Description Format Delta Data Source
Open-Target
Open-Initiator
Open-External
BackEnd
System
LDEV number
LDEV
Journal
External Volume
* The value cannot be collected for VSP E series, VSP Gx00 models, and VSP Fx00 models.
PI_CBMB
The PI_CBMB record stores the performance data indicating the performance between a channel blade and main blade. If the Acc
ess Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
From when the channel blade and the main blade are set up to when they are removed
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, VSP G1000,
G1500, or VSP F1500.
2. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_CCMS
The PI_CCMS record stores the performance data indicating the performance between a cache switch and cache memory. If the A
ccess Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, and HUS VM
storage systems.
2. For VSP G1000, G1500, and VSP F1500, no value is stored in this field.
3. For VSP G1000, G1500, and VSP F1500, the cache memory name is stored in this field.
4. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_CHAC
The PI_CHAC record stores the performance data indicating the performance between a channel adapter and cache switch. If the
Access Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, and HUS VM
storage systems.
2. For VSP G1000, G1500, and VSP F1500, the cache memory name is stored in this field.
3. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_CHDR
The PI_CHDR record stores the performance data indicating the usage of the data recovery reconfiguration circuit for a channel
adapter. If the Access Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, and HUS VM
storage systems.
2. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_CLMX
The PI_CLMX record stores the CLPR usage status for each MP Blade or MP unit. If the Access Type is 2 or 4, this record will
not be created.
Collection Interval
60
Key Fields
Lifetime
From when the MP Blade and the CLPR are set up to when they are removed
Fields
Name of the
microprocessor unit
that the processor
belongs to
Name of the MP
blade that the
Field Name Description Format Delta Data Source
processor belongs to
* The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_CPS
The PI_CPS record stores the performance data indicating the usage rate of the cache path in a main blade. If the Access Type
is 2 or 4, this record will not be created.
Collection Interval
60
Key Field
MAIN_BLADE_NAME
Lifetime
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, VSP G1000,
G1500, or VSP F1500.
2. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_DBMB
The PI_DBMB record stores the performance data indicating the performance between a disk blade and main blade. If the Access
Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
From when the disk blade and the main blade are set up to when they are removed
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, VSP G1000,
G1500, or VSP F1500.
2. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_DKAC
The PI_DKAC record stores the performance data indicating the performance between a disk adapter and cache switch. If the Acc
ess Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, and HUS VM
storage systems.
2. For VSP G1000, G1500, and VSP F1500, the cache memory name is stored in this field.
3. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_DKDR
The PI_DKDR record stores the performance data indicating the performance of the data recovery reconfiguration circuit for a disk
adapter. If the Access Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, and HUS VM
storage systems.
2. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_ELDS
The PI_ELDS record stores the performance data indicating the performance of an externally connected volume. If the Access T
ype is 2 or 4, this record will not be created.
Note:
If the CU number of the target LDEV is not set to be monitored, the record will not be created.
Collection Interval
3600
Key Field
LDEV_NUMBER
Lifetime
Fields
Field Name Description Format Delta Data Source
Example: [Link]
PI_EVGS
The PI_EVGS record stores the performance data indicating the performance of external volume groups. If the Access Type is 2
or 4, this record will not be created.
Note:
All the CU numbers of the LDEVs that belong to the target parity group must be set to be monitored for the record to be created.
Collection Interval
3600
Key Field
RAID_GROUP_NUMBER
Lifetime
Fields
The PI_HBAS record stores the performance data indicating the traffic performance between an HBA and a storage system. If the
Access Type is 2 or 4, this record will not be created.
Note:
If WWNs to be monitored are not set in advance, the record will not be output. Only the record for the HBAs registered to the
WWNs to be monitored will be output.
Collection Interval
60
Key Field
HBA_WWN
Lifetime
Fields
PI_HWSP
The PI_HWSP record stores the performance data indicating the traffic performance between an HBA for each port and a storage
system. If the Access Type is 2 or 4, this record will not be created.
Note:
If WWNs to be monitored are not set in advance, the record will not be output. Only the record for the HBAs registered to the
WWNs to be monitored will be output.
Collection Interval
60
Key Fields
Lifetime
Fields
PI_JNLX
The PI_JNLX record stores the performance data indicating the performance of a journal group (about journal-based remote copy
by Universal Replicator or Universal Replicator for Mainframe). If the Access Type is 2 or 4, this record will not be created.
Note:
The value stored in this record is the total value of the performance data for the LDEVs that belong to the monitored CUs. The
performance data of the LDEVs that belong to the CUs that are not monitored is not calculated together.
Collection Interval
60
Key Field
JOURNAL_ID
Lifetime
Fields
PI_LDSX
The PI_LDSX record stores the performance data indicating the performance of a volume.
Note that if you are monitoring a VSP 5000 series storage system and the Access Type is 2 or 4, you cannot collect
performance information about mainframe systems.
Note:
If the CU number of the target LDEV is not set to be monitored, the record will not be created.
Collection Interval
1 or 3 3600
2 or 4 300
Key Field
LDEV_NUMBER
Lifetime
Fields
Example: [Link]
Notes:
1. The value cannot be collected for VSP E series, VSP Gx00 models, VSP Fx00 models, and HUS VM storage systems.
2. If the Access Type is 2 or 4, the information in this field is not obtained.
3. If the Access Type is 2 or 4, a value cannot be obtained for storage systems other than VSP E series, VSP 5000 series
(versions 90-02-01 and later), VSP G350, G370, G700, G900, VSP F350, F370, F700, F900 (versions from 88-03-31 to
earlier than 88-04-00, or versions 88-04-02 and later).
PI_LDTC
The PI_LDTC record stores the performance data indicating the performance of an internal, external, or virtual volume (data of
remote copy by TrueCopy or TrueCopy for Mainframe, and monitoring data for global-active device). If the Access Type is 2 or 4,
this record will not be created.
Note:
If the CU number of the target LDEV is not set to be monitored, the record will not be created.
Collection Interval
3600
Key Field
LDEV_NUMBER
Lifetime
Fields
Example: [Link]
* The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, and VSP Fx00 models storage systems.
PI_LDU
The PI_LDU record stores the performance data indicating the activity rate of internal volumes. If the Access Type is 2 or 4, this
record will not be created.
Note:
If the CU number of the target LDEV is not set to be monitored, the record will not be created.
Collection Interval
3600
Key Field
LDEV_NUMBER
Lifetime
Fields
Example: [Link]
Notes:
1. For storage systems other than those of the following models, if the storage system has a built-in flash drive (FMD, FMC,
or SSD), the value displayed as the usage rate of the parity groups of the flash drive might be higher than the actual
usage rate, regardless of the load on the flash drive: VSP 5000 series, VSP Gx00, VSP Fx00, VSP G1000, G1500, and VSP
F1500.
For such storage systems, do not use as reference the value displayed as the usage rate of the parity groups of the flash
drive.
2. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_LDUR
The PI_LDUR record stores the performance data indicating the performance of an internal, external, or virtual volume (about
remote copy by Universal Replicator or Universal Replicator for Mainframe). If the Access Type is 2 or 4, this record will not be
created.
Note:
If the CU number of the target LDEV is not set to be monitored, the record will not be created.
Collection Interval
3600
Key Field
LDEV_NUMBER
Lifetime
Example: [Link]
The PI_LSP record stores the performance data indicating the performance of the LUs for each port. Note that if an applicable LU
is connected to multiple ports, the performance values for that LU will be the same. If the Access Type is 2 or 4, this record will
not be created.
Note:
If the CU number of the target LU (LDEV) is not set to be monitored, the record will not be created.
Collection Interval
3600
Key Fields
Lifetime
Fields
Example: [Link]
PI_LTSP
The PI_LTSP record stores performance data indicating the performance of the LUs for each port (data of remote copy by
TrueCopy or TrueCopy for Mainframe, and monitoring data for global-active device). Note that if an applicable LU is connected to
multiple ports, the performance values for that LU will be the same. If the Access Type is 2 or 4, this record will not be created.
Note:
If the CU number of the target LDEV is not set to be monitored, the record will not be created.
Collection Interval
3600
Key Fields
Lifetime
Fields
Example: [Link]
* The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, and VSP Fx00 models storage systems.
PI_LUSP
The PI_LUSP record stores performance data indicating the performance of the LUs for each port. Note that if an applicable LU is
connected to multiple ports, the performance values for that LU will be the same. If the Access Type is 2 or 4, this record will not
be created.
Note:
If the CU number of the target LU (LDEV) is not set to be monitored, the record will not be created.
Collection Interval
3600
Key Fields
Lifetime
Fields
Example: [Link]
PI_MBDR
The PI_MBDR record stores performance data indicating the usage rate of the data recovery reconfiguration circuit for a main
blade. If the Access Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, VSP G1000,
G1500, or VSP F1500.
2. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_MPCS
The PI_MPCS record stores the performance data indicating the performance between an MP Blade and cache switch. If the Acce
ss Type is 2 or 4, this record will not be created.
Collection Interval
60
Key Fields
Lifetime
Fields
Example: MPB0
Name of the
microprocessor unit
that the processor
belongs to
Notes:
1. The value cannot be collected for VSP E series, VSP 5000 series, VSP Gx00 models, VSP Fx00 models, and HUS VM
storage systems.
2. For VSP G1000, G1500, and VSP F1500, the cache memory name is stored in this field.
3. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_MPS
The PI_MPS record stores the performance data indicating the performance of a microprocessor. If the Access Type is 2 or 4,
this record will not be created.
Collection Interval
60
Key Fields
Fields
String created by
concatenating the name of the
microprocessor unit that the
processor belongs to and the
microprocessor name
String created by
concatenating the name of the
MP blade that the processor
belongs to and the
microprocessor name
* The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_MPTS
The PI_MPTS record stores the performance data indicating the performance of ports for mainframe systems. This record is not
created for ports with FNP attributes. If the Access Type is 2 or 4, this record will not be created.
Collection Interval
Note:
The items in (1) and (2) below all have the same field name (PORT_NUMBER), but the values output to the items in (1) are different
from those output to the items in (2).
For this reason, if you want to check whether the port information of one record matches that of another, check the PORT_NAME
field.
60
Key Field
PORT_NUMBER
Lifetime
Fields
Notes:
1. The value cannot be collected for VSP E series, VSP Gx00 models, VSP Fx00 models, HUS VM.
2. The CMR processing time is the time required for a monitored port to return a command response to the storage system
in response to I/O access from the storage system to that port.
3. The connection time is the time obtained by subtracting the CMR delay time from the response time.
4. The average disconnection time is the time during which processing is stopped to perform I/O processing for a drive
when the storage system performs I/O access to a monitored port.
5. The number of open exchanges is the average of the number of active I/O access operations for a monitored port.
Field Name1 Description Format Delta Data Source
6. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_PTSX
The PI_PTSX record stores the performance data indicating the performance of storage system ports. However, you cannot
collect performance data about mainframe systems. You can collect performance data about mainframe system ports by using
the PI_MPTS record.
Collection Interval
Note:
The items in (1) and (2) below all have the same field name (PORT_NUMBER), but the values output to the items in (1) are different
from those output to the items in (2).
For this reason, if you want to check whether the port information of one record matches that of another, check the PORT_NAME
field.
60
Key Field
PORT_NUMBER
Lifetime
Fields
Notes:
The PI_RGSX record stores performance data indicating the performance of a parity group, external volume group, and a virtual
volume group. If the Access Type is 2 or 4, this record will not be created.
Note:
All the CU numbers of the LDEVs that belong to the target parity group must be set to be monitored for the record to be created.
Collection Interval
3600
Key Field
RAID_GROUP_NUMBER
Lifetime
Fields
* The value cannot be collected for VSP E series, VSP Gx00 models, VSP Fx00 models, and HUS VM storage systems.
PI_RGU
The PI_RGU record stores the performance data indicating the activity rate of parity groups. If the Access Type is 2 or 4, this
record will not be created.
Collection Interval
3600
Key Field
RAID_GROUP_NUMBER
Lifetime
Fields
Notes:
1. For storage systems other than those of the following models, if the storage system has a built-in flash drive (FMD, FMC,
or SSD), the value displayed as the usage rate of the parity groups of the flash drive might be higher than the actual
usage rate, regardless of the load on the flash drive: VSP 5000 series, VSP Gx00, VSP Fx00, VSP G1000, G1500, and VSP
F1500.
For such storage systems, do not use as reference the value displayed as the usage rate of the parity groups of the flash
drive.
2. The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.
PI_SCPS
The PI_SCPS record stores the performance data indicating the performance of the entire storage system (monitoring data for
TrueCopy or TrueCopy for Mainframe, Universal Replicator or Universal Replicator for Mainframe, or global-active device). If the Ac
cess Type is 2 or 4, this record will not be created.
Note:
The value stored in this record is the total value of the performance data for the LDEVs that belong to the monitored CUs. The
performance data of the LDEVs that belong to the CUs that are not monitored is not calculated together.
Collection Interval
60
Key Field
None
Lifetime
Fields
second)
PI_SCS
The PI_SCS record stores performance data indicating the cache performance of the entire storage system. If the Access Type
is 2 or 4, this record will not be created.
Collection Interval
60
Key Field
None
Lifetime
Fields
* The value cannot be collected if data is collected by using RAID Agent bundled with Ops Center Analyzer.