Skip to content

Commit 69cc132

Browse files
committed
adding suggestions in
1 parent aa6ae67 commit 69cc132

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

content/news/articles/2025-06-09-metrics-opensearch.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,16 +18,19 @@ Cloud.gov has introduced comprehensive Elasticsearch/OpenSearch domain metrics t
1818
### System Resource Metrics
1919

2020
#### CPU Utilization
21+
These metrics help identify processing load and potential performance bottlenecks.
22+
2123
- Overall domain CPU usage, metric name: `CPUUtilization`
2224
- Master node CPU usage, metric name: `MasterCPUUtilization`
23-
- Helps identify processing load and potential performance bottlenecks
25+
2426

2527
#### Memory Pressure
28+
These metrics monitor memory consumption and other potential memory-related issues.
29+
2630
- JVM Memory Pressure, metric name: `JVMMemoryPressure`
2731
- Old Generation JVM Memory Pressure, metric name: `OldGenJVMMemoryPressure`
2832
- Master Node Memory Pressure, metric name: `MasterJVMMemoryPressure`
2933
- Old Generation Master Node Memory Pressure, metric name: `MasterOldGenJVMMemoryPressure`
30-
- Monitors memory consumption and potential memory-related issues
3134

3235
### Storage and Capacity Metrics
3336

@@ -43,9 +46,10 @@ This metric helps track storage capacity and plan for scaling.
4346
- Write Queue Rejected Requests, metric name: `ThreadpoolWriteRejected`
4447

4548
#### Search Queue Metrics
49+
These metrics monitor background processing and potential system overload:
50+
4651
- Search Queue Count, metric name: `ThreadpoolSearchQueue`
4752
- Search Queue Rejected Requests, metric name: `ThreadpoolSearchRejected`
48-
- Monitors background processing and potential system overload
4953

5054
## Using the Services - S3 Dashboard
5155
A quick way to view domain metrics is to:
@@ -94,8 +98,11 @@ An automated job runs every 10 minutes to pull metric events from the platform a
9498
Metric events are retained in the logging system for 12 months and in offline storage for an additional 18 months in accordance with [M-21-31 guidelines][m-21-31].
9599

96100
## Benefits
101+
97102
1. Domain monitoring
103+
98104
2. Early detection of resource constraints
105+
99106
3. Access to S3 bucket sizes
100107

101108
[logs]: https://logs.fr.cloud.gov

0 commit comments

Comments
 (0)