The Store status screen is accessible by logging into the Web Console and navigating to [Manage→DPOD Health→Store].

This screen consists of the following sections allowing to view the Store general health and delete data if necessary:

Cluster Health

Displays the cluster health status.

Detail	Description	Desired State

Detail

Description

Desired State

ex-raw-trans

The general state of the Big Data store.

GREEN – Everything is working properly.
YELLOW – System is up and running, but there’s a problem requiring your attention (e.g. one of the nodes is down, but another node took over).
RED – There is a major problem with the Big Data store. DPOD is malfunctioning. Contact the support team.

Note: During the first 10-20 minutes following a system startup, a value of YELLOW or RED is normal.

GREEN

(RED and YELLOW acceptable during startup)

Shards

Details of the allocation of logical data to physical storage in the Store. All shards should be assigned, and unassigned shards number should be 0.

Note: During the first 10-20 minutes following a system startup, a value greater than zero is normal.

If unassigned shards persist, see Error Accessing Store - Unassigned Shards.

0 Unassigned shards

(A larger than 0 value acceptable during startup)

Index Sets

This list displays the data sets that stores DPOD data.

Detail	Description	Desired State

Detail	Description	Desired State
Name	Index set name.
Indices Count	The number of indices within that index set that currently exist. There should be at least 1 index for each index set, and most index sets should contain between 1 and 20 indices. However, in case the storage allocated to DPOD is big enough (a few TB), the indices count for `wdp-syslog*` might reach a couple of hundreds of indices.	1-20 for most index sets 1-300 for Syslog indices when storage allows.
Size	Total size of the index set.	Greater than 0 for most index sets, depending on your usage.
Translog Size	Size of a temporary translog used by the active index for improved indexing performance.	Less than 1 GB
Documents Count	Total documents (such as Syslog messages, resource sampling, etc.) of the index set. Some index sets might contain 0 documents, if certain features are not in use in DPOD.	Greater than 0 for most index sets, depending on your usage.
Oldest Document Time	Oldest record in the index set. Verify that this fits your requirements, and if not – you may need to Increase Store Space.	As per your requirements.
Newest Document Time	Newest record in the index set. Verify that this fits your requirements, and if not – you may need to Increase Store Space.	As per your requirements.

DPOD uses index sets to manage different data types in the Big Data store:

apic-log: Contains transactional API-C data collected by the Syslog agents from monitored devices. This is the primary source of information for API-C product view dashboards and investigation.
wdp-config-service: Contains sampled configuration data about DataPower Gateway services. This is the primary source of information for the Explore section in Gateway product view.
wdp-device-resources: Contains samples of device resources, e.g.: monitored devices CPU, memory, hardware state, etc.
wdp-service-resources: Contains sampled service resources, e.g.: memory consumption by monitored services, etc.
wdp-syslog: Contains log records collected by the Syslog agents from monitored devices, except system messages, e.g.: transaction started, network call states, integration code errors, etc.
wdp-syslog-sys-*: Contains log records of system events collected by the Syslog agent from monitored devices.
wdp-wsm : Contains payload message collected by the WS-M agent when WS-M payload capture is enabled.
Other index sets are restricted and are for internal use only.

The data disk retention is automatically managed by DPOD. For each type of data (transactional, resources, payload, etc.), once its quota is full, old data will be discarded to make room for new data of the same type. A bigger disk size will hold a longer history.

Nodes

These are instances of the store services which implement a role in the Store cluster such as storing the data and running queries.

Detail	Description	Desired State

Detail	Description	Desired State
Name	Node Name
Version	Node Version	All versions should be the same
Host Name	Node's host name
Type	A correctly set up system should have at least one ‘D’ node (data processing node), and an odd number of ‘M’ nodes (master nodes).	D Nodes > 0 Odd M Nodes number

Nodes Health

The Nodes Health table contains additional information about the Store nodes (for example, the amount of swap space used, average time to index documents, etc).

These metrics are for DPOD support troubleshooting. When required, DPOD support will guide you through the usage of these metrics.

Pending tasks

This table shows a list of pending tasks in the Store, typically while the Store is initializing or performing administrative tasks.

Tasks appearing in this list for a while can indicate a problem in the Store.

This table may be used for troubleshooting by DPOD support team. When required, DPOD support team will guide you through the usage of this table.

Delete Stored Data Operations

This widget appears on the Store management screen, and lets the user perform operations to purge various sections of Store data according to data type, as specified below.

These are sensitive operations, which might affect your system in unexpected ways. These operations cannot be rolled back.
Do not perform these operations if you are unsure how they will affect your system.

The only operational situation where deleting an index set is recommended, is when sensitive data was collected using WS-M agents.
To safely delete this sensitive data, first shut down all WS-M agents (using the app-util scripts) and then delete the Index set.
Wait for 1-2 minutes until the index set is recreated before you start the WS-M agents again.

Operation	Description	Usage

Operation	Description	Usage
Delete Payload (WS-M) Data	Purge payload information recorded by WS-M	User
Delete Syslog TRAN Data	Purge transaction records received via Syslog	User
Delete Syslog SYS ERROR Data	Purge system error records received via Syslog	User
Delete Syslog AUTH Data	Purge system authorization records received via Syslog	User
Delete Syslog DEFAULT Data	Purge system default records received via Syslog(unclassified)	User
Delete DEVICE Resources Data	Purge device resource information recorded by the Device Resource agent	User
Delete SERVICE Resources Data	Purge device resource information recorded by the Service Resource agent	User
Delete Services Configuration Data (ES)	Purge service configuration information recorded by the Service Resource agent	User
Delete Restarts Data	Internal use	SYSTEM Only
Delete Sync Import Results Data	Internal use	SYSTEM Only
Delete Objects Status Data	Internal use	SYSTEM Only
Delete Logical Tran FULL Data	Internal use	SYSTEM Only
Delete Logical Tran COMPACT Data	Internal use	SYSTEM Only
Delete APIC Data	Internal use	SYSTEM Only
Delete IIB Tran Data	Internal use	SYSTEM Only
Delete IIB Stats Data	Internal use	SYSTEM Only
Delete Services Configuration Data (DB)	Internal use	SYSTEM Only
Delete System Health Data	Internal use	SYSTEM Only
Delete Internal Operations Data	Internal use	SYSTEM Only
Delete Static Data	Internal use	SYSTEM Only

IBM DPOD v1.0.22.x