The Store screen is accessible by logging into the Web Console and navigating to [Manage→Internal Manage→DPOD Health→Store].
DPOD's Big Data s Store is where all of DPOD's data is stored.
This screen display consist consists of 5 6 widgets, each allowing access to view data or perform Store-related tasks. They are described below and in the following pages:
| Child pages (Children Display) |
|---|
...
Cluster Status
| Detail | Description | Desired State | |
|---|---|---|---|
| ex-raw-trans | The general state of the Big Data store.
Note: During the first 10-20 minutes following a system startup, a value of YELLOW or RED is normal. | GREEN (but RED and YELLOW acceptable during startup)
| |
| Shards | Details of the allocation of logical data to physical storage in the Big Data Store. 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 under troubleshooting. | 0 Unassigned shards .( but aA larger than 0 value acceptable during startup) | |
| Buttons | Two buttons are available to the far right of the cluster status widget. Both the ES-head and ES-Visualize buttons are for DPOD support troubleshooting tasks. Store Button | The Store button may be used for troubleshooting by DPOD support team. When required, DPOD support team will guide you through the usage of these buttonsthis button. |
Index Sets
Data This list displays the data sets that store monitoring DPOD data received from monitored devices.
| Detail | Description | Desired State |
|---|---|---|
| Name | Index set name |
| . | |
| Indices Count |
The number of |
The indices count should therefore be no more than twice that value.
When the Indices count is higher, query performance may be affected. See Increase Storage for Index Sets for ways to resolve this.sue.
of days stored in data set.
All data sets starting with “wdp-“ should have a document count larger than 0.
A value of 0 for a wdp-* data set points to problems receiving data from monitored devices.
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 | 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 Storage for Index Sets. |
| As per your |
requirements
| requirements. | |
| Newest Document Time | Newest record in the index set. Verify that this fits your requirements, and if not – you may need to Increase Storage for Index Sets. |
| As per |
| your requirements. |
DPOD uses index sets to manage different data types in the Big Data store.:
| Index |
| Set Name | Description |
| 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. |
Contains data collected by the device resources agent, e.g. monitored devices CPU, memory, hardware state, etc.
wdp-service-resources
Contains data collected by the service resources agent, e.g. memory consumption by monitored services, etc.
Other index sets are restricted and are for internal use only.These indexes are self-managed from a disk storage perspective. Each index set is divided into multiple indexes and when the allocated space for that index set is exhausted, the oldest index set is deleted and new one is created.
This operation is done by the retention housekeeping process
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 the data nodes which the store Store uses for its internal processing.
| 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), |
|
Nodes Health
The Nodes Health table contains additional information about the ElasticSearch Store nodes (for example, the amount of swap space used, average time to index documents, etc)
Hover over the data to get additional information.
These metrics are for DPOD support troubleshooting. When required, DPOD support will guide you through the usage of these metrics.