2.7.2 Trend data Management Database

By building a trend data management DB in the intelligent integrated management database, trend data collected from the managed database can be centrally managed by the trend data management DB.

Organization of this subsection

(1) Database configuration

See 2.7.1(1)(a) Database configuration in Intelligent Integrated Management Database.

To Page Top

(2) Installation and Setup

Build a trend data management DB in the intelligent integrated management database to manage trend data.

For information about building an Intelligent Integrated Management Database (Trend Data Management DB), see the description about construction of Intelligent Integrated Management Database in the JP1/Integrated Management 3 - Manager Configuration Guide.

To Page Top

(3) Deleting trend data

(a) Functional Overview

This function automatically deletes trend data that has passed the retention period from the trend data management DB starting from the time of trend data (in the format of "time, value").

The default retention period is 32 days (46080 minutes).

The retention period can be changed on the setup command for the Intelligent Integrated Management Database (jimgndbsetup). The upper limit is 1096 days (3 years).

However, changing the settings requires a restart of the Trend Data Management Service.

■Operation image

For example, if the retention period is "32 days" and the execution time of the delete function is "2022/01/21 09:05:42.055", trend data for the past 32 days from "2022/01/21 09:05:42.055", that is, "2021/12/20 09:05:42.055" to "2022/01/21 09:05:42.055" will be saved and trend data outside this period will be deleted.

The following is an example of whether each trend data stored in the database is deleted under the above conditions:

Trend data stored in a database	Whether it will be deleted
: :	Deleted
Data on 2021/12/20 09:05:42.017	Deleted
Data on 2021/12/20 09:06:42.017	Not deleted
Data on 2021/12/20 09:07:42.017
: :
Data on 2022/01/21 09:05:42.017

(b) Setting and changing the retention period

You can set and change the retention period of trend data with the jimgndbsetup command.

■Setting the retention period

For physical host environments

Specify the retention period^# in item RETENTION of the Intelligent Integrated Management Database setup information file (jimgndbsetupinfo.conf).
For clustered environment

Specify the retention period^# in the item RETENTION of the Cluster environment Intelligent Integrated Management Database setup information file (jimgndbclustersetupinfo.conf).

#: Trend data that has passed the set retention period is deleted periodically (every 30 minutes).

The following is an example of the entry "RETENTION".

# IM GNDATABASE SERVICE - Retention
RETENTION=32

For details about Intelligent Integrated Management Database setup information file, and cluster environment Intelligent Integrated Management Database setup information file, see Intelligent Integrated Management Database setup information file (jimgndbsetupinfo.conf) and Cluster environment Intelligent Integrated Management Database setup information file (jimgndbclustersetupinfo.conf) in Chapter 2 Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

■Running the jimgndbsetup command

An example of running the jimgndbsetup command is shown below.

jimgndbsetup -f setup-information-file-name^#

#

For physical host environments

Intelligent Integrated Management Database Setup Information File Name
For clustered environment

Cluster Environment Intelligent Integrated Management Database Setup Information File Name

For details about the jimgndbsetup command, see jimgndbsetup in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(c) When to automatically delete trend data

Trend data is automatically deleted every 30 minutes starting when the retention period is set by the jimgndbsetup command. If the retention period of trend data is the default (32 days (46080 minutes)), trend data whose retention period has passed 46080 minutes is deleted every 30 minutes.

If the database is stopped at the time of automatic deletion of trend data, automatic deletion of trend data is executed when the database is started. In this case, the next automatic deletion operation is scheduled 30 minutes after the automatic deletion process completes.

Also, the timing and interval for deleting trend data cannot be changed by the user.

You can check the scheduled date and time of deletion of trend data with the jimgndbstatus command.

For details about the jimgndbstatus command, see jimgndbstatus in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

(d) About saving trend data for deletion

Trend data that has passed the retention period is deleted from the trend data management DB. If there is trend data (time series data) that you want to use even after the retention period has elapsed, use the time-series data acquisition API^# of JP1/IM - Manager (Intelligent Integrated Management Platform) to output and save the corresponding data.

For details on the time-series data acquisition API, see 5.11.2 Time-series data acquisition in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

#: JP1/IM - Agent product plug-in is required. JP1/IM - Use the time-series data acquisition method (__timeSeriesDataGet method) for acquiring trend information implemented by the agent's product plug-in.

■ Use case "Output and save trend data (time series data) to be deleted monthly"

Do the following:

List the SID and metric of the IM management node specified in the time series data acquisition API in advance.

•Checking the SID of the output target JP1/IM - Agent

Check the SID of JP1/IM - Agent that outputs time series data using the API for acquiring IM management node information.

SID of JP1/IM - Agent is identified from the node of Prometheus SID (_JP1PC-IMB_JP1/IM agent management base hostname/_JP1PC-M_P hostname/_HOST_P hostname/_PROMETHEUS_) or agent SID (_JP1PC-IMB_JP1/IM agent management base hostname/_JP1PC-M_P hostname/_JP1PC-AHOST_I hostname/_HOST_I hostname/_JP1PC-A_jp1_pc_nodelabel).

P hostname: Host name of the host on which the Prometheus server is set up

I hostname: Host name of the monitored host

jp1pc_nodelabel: setting value in jp1_pc_nodelabel of scrape_configs in Prometheus configuration file (jpc_prometheus_server.yml)

For details on the IM management node information acquisition API, see 5.8.3 IM management node information acquisition in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The following is an image of executing an API for retrieving IM management node information using the OSS curl command on a Windows command prompt.
- Run Login API
```
curl -XPOST -H "Content-Type: application/json" -c path-of-the-output-destination-text-file-A -d "{\"user\":\"JP1-user-name\",\"password\":\"password\"}" http://hostname:20703/im/api/v1/login
```
- Execute API for retrieving IM management node information
```
curl -GET -H "Content-Type: application/json" -b path-of-text-file-A http://hostname:20703/im/api/v1/nodes/configInfo
```
- Execution result of API for IM management node information acquisition (JSON format)
```
{"simtData":
[{
  "sid":"XXXX/XXXX",
  "value":{"component":"/HITACHI/JP1/XXXX","visible":"true","label":"XXXX"}
},{
  .......
},{
  "sid":"YYYY/YYYY/YYYY",
  "value":{ ......
     "methods":[.......,"__metricListGet","__timeSeriesDataGet",......],
     ......}
},{
   ......
}]
}
```
•Checking which metrics can be output

Use the metric list acquisition API to check the metric name of the time series data.

For details on the metric list acquisition API, see 5.11.1 Metric list acquisition in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The following is an image of executing the metric list acquisition API using the OSS curl command on a Windows command prompt.
- Example of executing the Login API
```
curl -XPOST -H "Content-Type: application/json" -c path-of-the-output-destination-text-file-A -d "{\"user\":\"JP1-user-name\",\"password\":\"password\"}" http://hostname:20703/im/api/v1/login
```
- Example of executing the metric list acquisition API
```
curl -XPOST -H "Content-Type: application/json" -b path-of-text-file-A -d "{\"sid\":\"JP1/IM-Agent-SID\"}" http://hostname:20703/im/api/v1/nodes/metrics
```
- Example of metric list acquisition API execution result (JSON format)
```
{"metrics":[
{
  "name":Metric-name,
  "default":Default-settings,
  "label":Metric-display-name,
  "description":"Metric-description"
} {
............
}
]}
```
Specify the SID of the JP1/IM - Agent node, the metric, and the output period (start date and time and end date and time) and execute the time-series data acquisition API.

•Get trend data

Use the time series data acquisition API to get the metric name of trend data (time series data). Since the API for acquiring time series data is executed by combining SID and metric, if there are multiple SIDs or metrics of JP1/IM - Agent nodes for which you want to output trend data, you need to execute the number of SIDs × number of metrics.

For details on the time-series data acquisition API, see 5.11.2 Time-series data acquisition in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

The maximum number of data that can be acquired by the Time Series Data Acquisition API is 30,000. For example, if the number of data per instance is one, the number of data will be 44,640 if data for × month (31 days) per minute is output, so it is necessary to divide the output target period into two times. The necessity of splitting and the number of splits depend on the data interval, output target period, and metric content (number of data per instance).

In addition, since the time series data acquisition API can fetch data in JSON format, it is necessary to extract trend data from JSON format data.

Specifically, since the "data" of "timeSeriesData" is stored in the format "{"time":date-and-time-data, "value":(metric)-value-at-that-date-and-time}," it is necessary to extract the data of "date-and-time-data" and "(metric)-value-at-that-date-and-time".

The following is an example of a request and response for the Time Series Data Acquisition API.
- Example Time Series data retrieval API Request
```
POST http://hostname:20703/im/api/v1/nodes/timeSeries
{
"sid":"_JP1PC-IMB_MHOST/_JP1PC-M_AHOST/_JP1PC-AHOST_AHOST/_HOST_AHOST/_JP1PC-A_Linux%20metric%20collector%28Node%20exporter%29",
"metric": "cpu_used_rate",
"startTime": "2021-06-01T00:00:00Z",
"endTime": "2021-06-15T23:59:59Z",
"countPerInstance":1,
"instanceCount":30000
}
```
- Time Series data acquisition API Response Example
```
< HTTP/1.1 200 OK
< Content-Type: application/json
{    
    "metric":"cpu_used_rate",
    "timeSeriesData":[
            {
                 "unit":"%",
                 "data":[
                  {"time":"2021-06-01T00:00:00Z","value":14.04},
                               ......
              ]
    ],
    "exceedCountDetected": {
        "countPerInstance": false,
        "instanceCount": false
    }
}
```
The following is an image of executing the time series data acquisition API using the OSS curl command on a Windows command prompt and outputting one month's worth of data in two parts.
- Example of executing the Login API
```
curl -XPOST -H "Content-Type: application/json" -c path-of-the-output-destination-text-file-A -d "{\"user\":\"JP1-user-name\",\"password\":\"password\"}" http://hostname:20703/im/api/v1/login
```
- Example of executing Time Series data acquisition API <1st time>
```
curl -XPOST -H "Content-Type: application/json" -b path-of-text-file-A -d "{\"sid\":\"JP1/IM-Agent-SID\",
\"metric\":\"metric-name\",
\"startTime\":\"2021-06-01T00:00:00Z\",
\"endTime\":\"2021-06-15T23:59:59Z\",
\"countPerInstance\":30000,
\"instanceCount\":1}" 
http://hostname:20703/im/api/v1/nodes/timeSeries
```
- Example of execution result of Time Series data acquisition API (JSON format) <1st time>
```
{"metric":
"cpu_used_rate",
"timeSeriesData":[
  {"unit":"%",
  "data":[
    {"time":"2021-06-01T00:00:00Z","value":10.480632},
     ......
  ]}
],
"exceedCountDetected":{"countPerInstance":false,"instanceCount":false}
}
```
- Example of executing Time Series data acquisition API <2nd time>
```
curl -XPOST -H "Content-Type: application/json" -b path-of-text-file-A -d "{\"sid\":\"JP1/IM-Agent-SID\",
\"metric\":\"metric-name\",
\"startTime\":\"2021-06-16T00:00:00Z\"
\"endTime\":\"2021-06-30T23:59:59Z\",
\"countPerInstance\":30000,
\"instanceCount\":1}" 
http://hostname:20703/im/api/v1/nodes/timeSeries
```
- Example of execution result of Time Series data acquisition API (JSON format) <2nd time>
```
{"metric":
"cpu_used_rate",
"timeSeriesData":[
  {"unit":"%",
  "data":[
    {"time":"2021-06-16T00:00:00Z","value":9.560327},
     ......
  ]}
],
"exceedCountDetected":{"countPerInstance":false,"instanceCount":false}
}
```

(e) Manual deletion of trend data (psql commands)

If you want to delete trend data in the Intelligent Integrated Management Database without stopping operation, delete trend data by directly manipulating the table with the superuser role (Postgres).

The procedure for deleting trend data is as follows:

Run the following command to connect to the Intelligent Integrated Management Database with the superuser role:
```
psql -d imgndb -U postgres -W -p port-number-of-the-Intelligent-Integrated-Management-Database
```
When prompted for a password, enter the password shown below.
```
2BXY7aVkbicj
```
Run the following command to get a list of metric names:
```
select * from metric;
```
When you execute the above command, you can get the values of metric_name (metric name obtained as trend data) and table_name (name of the table that stores trend data for time series).
Check the table corresponding to the metric name confirmed in step 2 (repeat the number of metrics from step 3 onwards).

The name of the table corresponding to the metric name is "prom_data. Metric Name".

You can run the following command to check the number of records in the table corresponding to each metric name.
```
select count(*) from prom_data.metric-name;
```
Check the number and content of records to be deleted.

As an example, if you want to delete records one month before the current time (keep records from the last one month), you can check the number of records in the table corresponding to each metric name by executing the following command.
```
select count(*) from prom_data.metric-name where time <= cast(now() - interval# '1 months' as timestamp);
```
You can also run the following command to check the contents of the record to be deleted.
```
select * from prom_data.metric-name where time <= cast(now() - interval# '1 months' as timestamp);
```
#

The unit of the value specified by interval can also be minutes, hour, etc.

You can also specify a specific date, as shown in the following example.
```
select * from prom_data.metric-name where time <= '2021-09-30';
```
Delete trend data.

Since trend data is managed in units called chunks (child tables by date and time interval), trend data is deleted in chunks.

As an example, if you want to delete data older than one month, run the following command:
```
select drop_chunks('prom_data.metric-name', older_than => interval^# '1 months');
```
#

The unit of the value specified by interval can also be minutes, hour, etc.

You can also specify a specific date, as shown in the following example.
```
select drop_chunks('prom_data.metric-name', older_than => '2021-09-30');
```
If you delete trend data in chunks, chunks containing only the data for the period specified at the time of deletion will be deleted. Therefore, data from the specified period is not deleted if it is stored in a chunk that contains data outside the specified period.

(f) Automatic deletion of trend data (size cap)

Monitor the amount of disk space used by Trend data Management Database. If the amount of disk space used exceeds the standard value (90% of the value specified in TDDBDISKMAX of Intelligent Integrated Management Database setup information file, or cluster environment Intelligent Integrated Management Database setup information file), remove the old trend data to reduce the amount of disk space used.

You can use Intelligent Integrated Management Database setup command to set the following items:

Max Disk Requirements for Trend data Management Database

Trend data is automatically deleted when it exceeds 90% of the specified value.
Duration of trend data to be deleted

When automatic deletion of trend data is executed, the data of the specified period from the oldest trend data is deleted.

■Monitoring Disk Requirements and Trend Data Deletion Timing: Monitors disk requirements and deletes trend data (when the threshold is exceeded) as one task and performs this task at 1-minute intervals. (The next task is executed one minute after the completion of one task.)
■About the duration of trend data to be deleted: Specify in TDDBCUTOFFTERM of Intelligent Integrated Management Database setup information file, or cluster environment Intelligent Integrated Management Database setup information file.

(g) Deleting Trend Data Manually (Specify integrated agent, user-defined Prometheus, and user-defined Fluentd host names and Delete)

Integrated agent host's Prometheus and Fluentd, user-defined Prometheus, and user-defined Fluentd have the ability of removing trend data stored in Trend data Management Database.

Use REST API of Delete trend data in JP1/IM - Manager to remove trend data from Trend data Management Database through Trend Data Management Service (Promscale). It can also be deleted from the List of Integrated Agents window of integrated operation viewer.

Restarts Trend Data Management Service automatically after the trend data is deleted. If deletion of trend data fails, Trend Data Management Service does not restart. However, if you specify more than one target for deletion and the deletion of some trend data succeeds, restart Trend Data Management Service.

Trend data cannot be deleted concurrently for Trend data Management Database on the same host. After the trend data is deleted and Trend Data Management Service is restarted, Trend data Management Database of the same host cannot be executed consecutively for a certain period of time (the interval at which Delete trend data is executed). If the command is executed concurrently or continuously, a warning message (KAJY62015-W) is displayed. For details about the interval during which Delete trend data cannot be executed consecutively, see the setting item "jp1.imdd.trenddata.deleteInterval" in the Intelligent Integrated Management Base definition file (imdd.properties) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

For details on API of Delete trend data , see 5.11.4 Delete Trend Data in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference. For details about the List of Integrated Agents window of integrated operation viewer, see 2.2.1 List of Integrated Agents window in the JP1/Integrated Management 3 - Manager GUI Reference.

■Scope of deletion

Delete all trend data stored in Trend data Management Database by Prometheus or Fluentd (including user-defined Prometheus and user-defined Fluentd) of the host that you specified for deleting trend data

Trend data to be deleted is shown below.

Performance data^# and alert infomation scraped by Prometheus
Metric sent by Fluentd's log trapper in metric capabilities

The following trend data deletions cannot be performed.

Delete only the trend data collected by a particular Exporter
Delete only the trend data in a specific monitored target
Delete trend data for which the monitored target host is specified as the deletion target

#: Exporter you scrape is for both the configuration of the same host as Prometheus and the configuration of a different host. Exporter also monitors both the configuration of the same host and the configuration of a different host.

■About JP1 Events in Delete trend data

When trend data is deleted, one of the following event ID events is issued for JP1: For details on JP1 events, see 3.2.3 List of JP1 events output by JP1/IM - Agent in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

00003F86 (Delete trend data successful)
00003F87 (Delete trend data failed)
00003F88 (Delete trend data succeeded, but Trend Data Management Service restart failed)

If the manager is in a hierarchical configuration, we recommend that you configure lower manager to forward JP1 events for the above event ID to detect the deletion of trend data in the Integrated Manager. For details about forwarding events, see the forwarding of JP1 events section in the JP1/Base User's Guide.

■About restarting Trend Data Management Service

When Trend Data Management Service restarts, it prints messages in the following message ID to the integrated trace log: For details about messages, see the appropriate section in the JP1/Integrated Management 3 - Manager Messages.

Message ID	Output trigger
KAJY62016-I	When Trend Data Management Service Restart Starts
KAJY62017-I	Upon a successful Trend Data Management Service restart
KAJY62018-E	When Trend Data Management Service Restart Fails

When Trend Data Management Service is restarted automatically after trend data is deleted, Trend Data Management Service restart process according to Intelligent Integrated Management Database and Trend Data Management Service startup status is as shown in the following tables.

Service status		Trend Data Management Service Restart Process
Intelligent Integrated Management Database servicing	Trend Data Management Service	Trend Data Management Service Restart Process
Startup	Startup	Restart Trend Data Management Service. The event ID notifies JP1 event of 00003F86. Print KAJY62017-I messaging to the unified trace log.
Stop	Stop	Does not start Trend Data Management Service. The event ID notifies JP1 event of 00003F86. Print KAJY62017-I messaging to the unified trace log.
Startup	Stop	Does not start Trend Data Management Service. The event ID notifies JP1 event of 00003F86. Print KAJY62017-I messaging to the unified trace log.
Stop	Startup	Trend Data Management Service is stopped and not started. The event ID notifies JP1 event of 00003F86. Print KAJY62017-I messaging to the unified trace log.

■Notes on Deleting trend data

1. Deleting trend data automatically restarts Trend Data Management Service on the manager host that manages integrated agent host, user-defined Prometheus, and your own Fluentd. Therefore, you need to adjust the following parameters:

<When the specified manager host is a cluster environment>

Adjust the cluster soft parameters so that restarting Trend Data Management Service does not cause failover. Also, adjust Intelligent Integrated Management Base definition file parameter so that Trend Data Management Service reboots continuously and no failover occurs when you perform consecutive trend data deletions.

Cluster soft parameters

See 7.5.3 Setting Cluster Soft Parameters (for Windows) and 8.5.3 Setting Cluster Soft Parameters (for Linux) in the JP1/Integrated Management 3 - Manager Configuration Guide.
Intelligent Integrated Management Base definition file Parameters

See 7.4.1 Creating a new cluster environment (For Windows) and 8.4.1 Creating a new cluster environment (for UNIX) in the JP1/Integrated Management 3 - Manager Configuration Guide.

<When monitoring Trend Data Management Service process/service of the specified manager host>

Adjust the following parameters so that they are not detected as unhealthy when Trend Data Management Service restarts:

Prometheus configuration file Parameters

Set the scrape_interval (scrape interval) of Prometheus configuration file (jpc_prometheus_server.yml) to 15 seconds or longer. For details about the Prometheus configuration file, see Prometheus configuration file (jpc_prometheus_server.yml) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
Alert configuration file Parameters

For the period specified in for of alert configuration file (jpc_alerting_rules.yml), set twice or more of scrape interval specified in Prometheus configuration file (jpc_prometheus_server.yml). For details about the alert configuration file, see alert configuration file (jpc_alerting_rules.yml) in Chapter2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
Intelligent Integrated Management Base definition file Parameters

Sets Delete trend data interval to twice or more of scrape interval specified by Prometheus configuration file (jpc_prometheus_server.yml). For details about Delete trend data interval, see property "jp1.imdd.trenddata.deleteInterval" of Intelligent Integrated Management Base definition file (imdd.properties) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

If both of the above are true, set Delete trend data interval to the larger of the values.

The parameter settings described above are based on a value that assumes that the restart time of Trend Data Management Service is about 7 seconds, and are calculated so that the values are larger than that. Therefore, if Trend Data Management Service restart time is measured to take longer than 7 seconds, the parameter must be adjusted before using Trend data deletion function to avoid false positives in clustered software or process/service monitoring.

The restart time of Trend Data Management Service is calculated from the time of KAJY62016-I and KAJY62017-I messages that are output to the integrated trace log when deleting trend data is executed. Based on the calculated value, set the parameter value with sufficient room considering the load on the system.

Assuming that Trend Data Management Service is restarted for 7 seconds, the following cases and corrective actions will be taken when the parameters are set as follows:

- Example of parameter settings

Cluster software monitoring interval: 14 seconds
Number of times that cluster software has stopped: 2 consecutive times
Delete trend data interval: 28 seconds

<When monitoring processing of cluster software is delayed>

False detection occurs when the monitoring process of the cluster software is delayed and takes twice or more time (28 seconds or more) than the setting value of the monitoring interval.

In this case, do one or both of the following to prevent false positives:

Set the interval for Delete trend data to twice or more (56 seconds or more) the interval for monitoring the cluster software when delayed (28 seconds or more).
Set three or more times consecutively for the number of times that the cluster software is judged to have stopped.

<When Trend Data Management Service restart processing is delayed>

False detection occurs when Trend Data Management Service restart process is delayed and takes at least twice the expected time (14 seconds or more).

In this case, do one or both of the following to prevent false positives:

Set the cluster software monitoring interval to twice or more (28 seconds or more) the restart time for Trend Data Management Service at the time of delay (14 seconds or more) and to set the interval to Delete trend data at least twice or more (56 seconds or more).
Set three or more times consecutively for the number of times that the cluster software is judged to have stopped.

2. After the trend data is deleted, Trend Data Management Service is restarted, so the trend data cannot be viewed during the restart. The approximate restart time for Trend Data Management Service is 7 seconds or less.

While trend data cannot be referenced, integrated operation viewer window operates as follows. If this happens, after Trend Data Management Service reboots, you can do so by refreshing or rerunning.

Details area - Tabs area - In the Trend graph view area of the Trends tab, when a graph is displayed, an error of KAJY22006-E is displayed, an error of KAJY24610-E is displayed in the detailed message, and an error of KAJY62000-E is displayed in the message.
Panels that show information about metric in the following dashboards, including the Alert information panel, have a red ! on the left side of the title and a NO DATA in the View Info area.
Details area - Tabs area - Dashboard to display on the Dashboard tab
View menu - Dashboard List - Dashboard List dialog box
When the Generate Tree Information button is clicked in the List of Definition Files for Managers window and tree information generation is executed from the Generate Tree Information dialog box, a KAJY02028-W warning is displayed, a KAJY04704-E error is displayed in the message details, and a KAJY62000-E error is displayed in the message.

3. If you change the hostname of integrated agent, user-defined Prometheus, or user-defined Fluentd and then remove the previously saved trend data, specify the hostname before the change.

4. If you specify more than one manager host to delete trend data and the operation is interrupted by an error, the manager host that is not deleting trend data does not issue JP1 events for 3F86, 3F87, 3F88 by the event ID.

5. If you have read/manipulate permissions to the IM management node of the hosts where the integrated agent, user-defined Prometheus, or user-defined Fluentd is running, and you specified to delete trend data, delete all trend data stored on that host by Prometheus and Fluentd.

6. Delete trend data cannot be executed consecutively. If the command is executed continuously at intervals shorter than Delete trend data interval, a warning message (KAJY62015-W) is displayed and the trend data cannot be deleted. Also, concurrent execution is not possible. For details about Delete trend data interval, see property "jp1.imdd.trend.delete.interval" of Intelligent Integrated Management Base definition file (imdd.properties) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.

7. If you have user-defined Prometheus or user-defined Fluentd installed on your integrated agent host, the trend data is also deleted when they store trend data in Trend data Management Database.

8. Even if you specify a host that does not exist in the deletion target, the system performs the deletion operation and restarts Trend Data Management Service.

9. In some cases, trend data is not deleted. The following table shows the cases in which trend data is not deleted and the deletion method.

No.	Case where trend data is not deleted	Deletion procedure
1	SAP system monitoring function monitors the system log information or CCMS alert information of SAP system.	In Trend data deletion API, specify the following value for the `agenthost` parameter of the request, and execute it: SAP instance name specified in `instance` of the `[Metric Settings]` section of text-formatted log file monitoring definition file
2	Fluentd log trapper specifies a hostname other than integrated agent, user-defined Prometheus, or user-defined Fluentd in instance of text-formatted log file monitoring definition file, or `[Metric Settings]` section of Windows event-log monitoring definition file, even if it is set incorrectly or in a different case.	In Trend data deletion API, specify the following value for the `agenthost` parameter of the request, and execute it: Text specified in `instance` of the `[Metric Settings]` section of text-formatted log file monitoring definition file, or Windows event-log monitoring definition file
3	Fluentd's log trapper does not specify a instance for the `[Metric Settings]` section of text-formatted log file monitoring definition file, or Windows event-log monitoring definition file.	Perform manual deletion of trend data (psql commands). However, because all the specified metric are subject to deletion, if there are multiple log monitoring settings, or if there are log monitoring settings for multiple hosts, the trend data of log monitoring for all Fluentd is subject to deletion.
4	Performance monitoring function specifies a jp1_pc_prome_hostname in the `global.external_labels` section of Prometheus configuration file that is not a hostname for integrated agent, user-defined Prometheus, or user-defined Fluentd, even if it is set incorrectly or in a different case.	In Trend data deletion API, specify the following value for the `agenthost` parameter of the request, and execute it: `jp1_pc_prome_hostname` specified in the `global.external_labels` section of Prometheus configuration file

10. For hierarchical configurations, the Integration Manager and lower manager must be versioned with JP1/IM - Manager 13-10 or later. Otherwise, the trend data cannot be deleted.

(h) Deleting Trend Data Manually (Delete from Managed Object)

When you remove a integrated agent from Intelligent Integrated Management Base managed, integrated agent host's Prometheus and Fluentd remove the trend data stored in Trend data Management Database.

Use REST API of integrated agent info deletion in JP1/IM - Manager to remove trend data from Trend data Management Database through Trend Data Management Service (Promscale). Trend data saved by integrated agent host's Prometheus or Fluentd in Trend data Management Database can also be deleted from integrated operation viewer's List of Integrated Agent window.

Trend Data Management Service does not restart if all of the trend data to be deleted fails. Restart Trend Data Management Service if some of the trend data to be deleted has been successfully deleted.

Trend data cannot be deleted concurrently for Trend data Management Database on the same host. After the trend data is deleted and Trend Data Management Service is restarted, Trend data Management Database of the same host cannot be executed consecutively for a certain period of time (the interval at which Delete trend data is executed). If the command is executed concurrently or continuously, a warning message (KAJY62015-W) is displayed. For details about the interval during which Delete trend data cannot be executed consecutively, see the setting item jp1.imdd.trenddata.deleteInterval in Intelligent Integrated Management Base definition file (imdd.properties) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference. See also.

For details about API for deleting integrated agent information, see 5.18.2 Delete integrated agent info in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference. For details about the List of Integrated Agents window of integrated operation viewer, see 2.2.1 List of Integrated Agents window in the JP1/Integrated Management 3 - Manager GUI Reference.

■Scope of deletion

See Scope of deletion of 2.7.2(3)(g) Deleting Trend Data Manually (Specify integrated agent, user-defined Prometheus, and user-defined Fluentd host names and Delete).

However, you cannot specify anything other than integrated agent host (the one on which JP1/IM - Agent is installed) for deleting trend data.

■About JP1 Events in Delete trend data

See About JP1 Events in Delete trend data of 2.7.2(3)(g) Deleting Trend Data Manually (Specify integrated agent, user-defined Prometheus, and user-defined Fluentd host names and Delete).

■About restarting Trend Data Management Service

See About restarting Trend Data Management Service of 2.7.2(3)(g) Deleting Trend Data Manually (Specify integrated agent, user-defined Prometheus, and user-defined Fluentd host names and Delete).

■Notes on Deleting Trend Data

1. See 1,2,4 to 7,9 in 2.7.2(3)(g) Deleting Trend Data Manually (Specify integrated agent, user-defined Prometheus, and user-defined Fluentd host names and Delete).

2. If you change the hostname of integrated agent and then delete the previously saved trend data, use Delete trend data API to delete the trend data.

3. If deletion of trend data fails, integrated agent data to be deleted is not deleted.

4. For hierarchical configurations, the Integration Manager and lower manager must be versioned with JP1/IM - Manager 13-10 or later. Otherwise, the trend data cannot be deleted. The operation of integrated agent is as follows.

If the Integration Manager is JP1/IM - Manager 13-00 or 13-01 and lower manager is JP1/IM - Manager 13-10 or later, you can delete integrated agent managed by lower manager from the Integration Manager.
If the version of the Integration Manager's JP1/IM - Manager is 13-10 or later and the version of the lower manager 's JP1/IM - Manager is 13-00 or 13-01, you cannot delete integrated agent managed by lower manager from the Integration Manager. In this case, take one of the following actions:

- Upgrade lower manager's JP1/IM - Manager to version 13-10 or later, and delete the integration agent information managed by lower manager from the Integration Manager.

- Delete the integration agent information managed by lower manager from lower manager.

(i) How to use the method for deleting trend data for each use case

The following shows how to delete trend data according to the use case.

Use Case	Delete method to use
Deletes unused metric trend data because database sizing misdesign is likely to exceed the database disk size limit before the database retention period.	Deleting trend data manually (psql commands) ^#1
To use the development and verification environment as a production environment, delete trend data saved in the development and verification environment.	Use one of the following methods: Intelligent Integrated Management Database re-setup ^#2 Deleting trend data manually (specify integrated agent, user-defined Prometheus, and user-defined Fluentd host names and delete)
The trend data of metric of a label that resulted in an unintended value due to a setting error such as a definition file, and unnecessary IM management node was displayed. The trend data of the label that resulted in an unintended value is deleted.	Use one of the following methods: Deleting trend data manually (psql commands) ^#1 Deleting trend data manually (specify integrated agent, user-defined Prometheus, and user-defined Fluentd host names and delete) ^#3
Because the value of the label of metric becomes unintended content due to the setting error of the definition file, etc., and unnecessary linestring is displayed in the graph of the trend display, the trend data of metric of the label with the unintentional value is deleted.
Because you want to remove integrated agent from Intelligent Integrated Management Base managed objects and also delete IM management node of Prometheus, Exporter, Fluentd managed by integrated agent, delete trend data stored in Trend data Management Database by Prometheus or Fluentd on the integrated agent host.	Deleting trend data manually (delete from managed object)
You want to remove user-defined Prometheus or user-defined Fluentd from Intelligent Integrated Management Base managed objects, and also remove IM management node for user-defined Prometheus, Exporter, and Fluentd. You delete trend data stored in Trend data Management Database by user-defined Prometheus or user-defined Fluentd.	Deleting trend data manually (specify integrated agent, user-defined Prometheus, and user-defined Fluentd host names and delete)

#1

The following cases cannot be handled because all the specified metrics will be deleted.

HostA and hostB each collect Windows exporter's windows_memory_cache_bytes of metric, and hostA's metric does not require windows_memory_cache_bytes, but hostB's metric is required.

#2

In integrated agent host, you must reconfigure the initial secret and remove the individual secret.

#3

The following cases are not supported because Prometheus of the specified host (integrated agent host) and the trend data stored by Fluentd in Trend data Management Database are deleted.

You want to remove unwanted trend data due to misconfiguration of Windows exporter of hostA, but you do not want to remove the trend data of Fluentd.

To Page Top