1.0.20 enhancement and patches
For a list of recent updates and enhancements across multiple versions, see Release-notes-and-notices.
BMC applies upgrades as described in BMC Helix Upgrade policy . BMC applies upgrades and patches during Maintenance windows .
1.0.20
Monitor the query, fetch, and indexing operations
The PATROL for Elasticsearch KM introduces the following parameters to track the number of operations performed during each data collection cycle:
- Query Operations (deltaQueryTotal)
- Fetch Operations (deltaFetchTotal)
- Indexing Operations (deltaIndexDocTotal)
These parameters are collected at the node and index levels, giving you visibility into how Elasticsearch handles search queries, retrieves documents, and processes indexing activity across your environment.
With these parameters, you can perform the following actions:
- Track query workload by counting the number of search requests executed
- Count fetch operations during searches by tracking the number of documents retrieved after each query
- Monitor indexing throughput and detect ingestion spikes by counting the number of documents added or updated in the index
Use this capability to detect workload spikes in search or indexing activity and troubleshoot performance issues faster. To learn more about the parameters, see Index (ESK_INDEX) and Node (ESK_NODE).
Monitor normalized CPU utilization at the node level
Monitor CPU load more accurately by using the new Normalized CPU Utilization (NormalizedCPUUtilization) parameter available at the node level. This parameter helps you better understand CPU usage across nodes and supports more accurate capacity planning. For more information, see Node (ESK_NODE).
1.0.19
Additional attributes in the Index and Node monitor types
You can use the following additional metrics in the Index and Node monitor types:
| Monitor type | Metrics |
|---|---|
| Index | Documents deleted (DocumentsDeleted) |
| Node |
|
For more information, see the following topics:
Documents deleted (DocumentsDeleted)
Documents deleted (DocumentsDeleted)
Process CPU Usage (ProcessCpuUsage)
Enable precise event correlation with the Elasticsearch cluster device
Leverage BMC PATROL for Elasticsearch to associate events directly with the Elasticsearch cluster device instead of the PATROL Agents. This capability improves event correlation by aligning events with relevant device names.
Accurate event-to-device mapping within Elasticsearch clusters reduces false alarms, streamlines root cause identification, and significantly enhances monitoring efficiency. For more information, see Configuring the Elasticsearch monitor profile.
Security enhancements
BMC PATROL for Elasticsearch 1.0.19 patch contains the third-party software upgrade commons3-3.0.18.jar for security enhancements.
1.0.18
Support for new global-level variables to remove unavailable nodes
To reduce operational overheads, use the following global-level variables to make the configuration changes that are required to remove unavailable nodes from the cluster:
- /ESK_TOP/removeNodeAfterNDiscCycle =number of retries
- REMOVE_NODE_AFTER_N_DISC_CYCLE =number of retries
For more information, see Configuring the removal of unavailable nodes from monitoring.
Security enhancements
BMC PATROL for Elasticsearch 1.0.18 patch contains the third-party software upgrade commons-beanutils-1.11.0.jar for security enhancements.
1.0.17
Added new metrics in the Node (ESK_NODE) application class
Added the following CPU and Memory metrics to Elasticsearch cluster nodes:
1.0.16
Security enhancements
BMC PATROL for Elasticsearch 1.0.16 patch contains the following third-party software upgrades for security enhancement:
- json-20240303.jar
- commons-collections4-4.4.jar
- commons-lang3-3.17.0.jar
For more information about the corrected issues in this version, see Known-and-corrected-issues.
1.0.15
Security enhancements
BMC PATROL for Elasticsearch 1.0.15 patch contains the following third-party software upgrade for security enhancement:
httpclient-4.5.14.jar
1.0.14
Monitor new metrics in the Cluster (ESK_CLUSTER) application class
Monitor the following attributes of the Cluster (ESK_CLUSTER) application class in PATROL for Elasticsearch:
Number of pending tasks (NumberOfPendingTasks)
1.0.13
Monitor new attributes
Monitor the following attributes in PATROL for Elasticsearch:
- Cluster (ESK_CLUSTER)
- Cluster Index Writes Blocked (ClusterIndexWritesBlocked)
- Primary Write Rejected (PrimaryWriteRejected)
- Replica Write Rejected (ReplicaWriteRejected)
- Total number of Indices (TotalIndices)
- Total number of Nodes (TotalNodes)
- Successful Nodes (SuccessfulNodes)
- Failed Nodes (FailedNodes)
- Index (ESK_INDEX)
- Cluster Index Writes Blocked (ClusterIndexWritesBlocked)
- Indexing time (IndexingTime)
- Index fields limit (IndexFieldsLimit)
- Fields Count (FieldsCount)
- Fields used percent (FieldsUsedPercent)
- Node (ESK_NODE)
- Indexing rate (IndexingRate)
- Threadpool Search Queue (ThreadpoolSearchQueue)
- Threadpool Search Rejected (ThreadpoolSearchRejected)
- Threadpool Bulk Queue ( ThreadpoolBulkQueue)
- Threadpool Bulk Rejected (ThreadpoolBulkRejected)
- Threadpool Write Queue (ThreadpoolWriteQueue)
- Threadpool Write Rejected (ThreadpoolWriteRejected)
- Primary Write Rejected (PrimaryWriteRejected)
- Replica Write Rejected (ReplicaWriteRejected)
- Elasticsearch System (ESK_CONT)
- eskConfigCollector
1.0.12
Monitor new metrics in the Cluster (ESK_CLUSTER) application class
Monitor the following attributes of the Cluster (ESK_CLUSTER) application class in PATROL for Elasticsearch.
- Shards allocated (ShardsAllocated)
- Shards utilization (ShardsUtilization)
For more information, see Cluster (ESK_CLUSTER).
1.0.11
Option to change the instance ID (SID) format
Select the following options from Elasticsearch Host Details>Instance format to change the instance ID (SID):
- Label
- Cluster ID
- Cluster Name
This helps to identify and organize the events related to Elasticsearch clusters.
For more information, see Configuring the Elasticsearch monitor profile.
1.0.10
New attribute to the Shards class
The Active-shards-percent-ActiveShardsPercent attribute is added to the Shards class that displays the percentage of active primary shards.
Option to change the instance ID format for Node instances
Configure the Node instance format field to include one of the following options in instance ID:
- ID
- Name
- Cluster Name
For more information, see elsearch1010.