Skip to content

Commit 25cb810

Browse files
authored
Update memcached-opentelemetry.md
1 parent ba035b0 commit 25cb810

File tree

1 file changed

+10
-14
lines changed

1 file changed

+10
-14
lines changed

docs/integrations/databases/opentelemetry/memcached-opentelemetry.md

Lines changed: 10 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,6 @@ Memcached logs are sent to Sumo Logic through the OpenTelemetry [filelog receive
1919

2020
<img src='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Memcached-OpenTelemetry/Memcached-Schematics.png' alt="Schematics" />
2121

22-
2322
:::info
2423
This app includes [built-in monitors](#memcached-alerts). For details on creating custom monitors, refer to the [Create monitors for Memcached app](#create-monitors-for-memcached-app).
2524
:::
@@ -29,12 +28,11 @@ This app includes [built-in monitors](#memcached-alerts). For details on creatin
2928
Following are the [Fields](/docs/manage/fields/) which will be created as part of Memcached App install if not already present.
3029

3130
- **`sumo.datasource`**. Has a fixed value of **memcached**.
32-
- **`db.system`**. Has a fixed value of **memcached**
33-
- **`deployment.environment`**. User configured. This is the deployment environment where the Memcache cluster resides. For example: dev, prod or qa.
31+
- **`db.system`**. Has a fixed value of **memcached**.
32+
- **`deployment.environment`**. User configured. This is the deployment environment where the Memcache cluster resides. For example: dev, prod, or qa.
3433
- **`db.cluster.name`**. User configured. Enter a name to identify this Memcached cluster. This cluster name will be shown in the Sumo Logic dashboards.
3534
- **`db.node.name`**. This has value of the FQDN of the machine where OpenTelemetry collector is collecting logs and metrics from.
3635

37-
3836
## Prerequisites
3937

4038
1. Configure logging in Memcached: By default, the installation of Memcached will not write any request logs to disk. To add a log file for Memcached, you can use the following syntax:
@@ -226,13 +224,12 @@ Following is the query from Errors panel of Memcached app's overview Dashboard:
226224
| sum(ERROR) as ERROR by _timeslice
227225
```
228226
## Sample metrics queries
229-
**Total Get**
230227

231-
```
228+
```sql title="Total Get"
232229
sumo.datasource=memcached deployment.environment=* db.cluster.name=* db.node.name=* metric=memcached.commands command=get | sum
233230
```
234231

235-
## Viewing Memcached Dashboards
232+
## Viewing the Memcached dashboards
236233

237234
### Overview
238235

@@ -242,7 +239,7 @@ The **Memcached - Overview** dashboard provides an at-a-glance view of the Memca
242239

243240
### Operations
244241

245-
The **Memcached - Operations** Dashboard provides detailed analysis on connections, thread requested, network bytes, table size.
242+
The **Memcached - Operations** Dashboard provides detailed analysis on connections, thread requested, network bytes, and table size.
246243

247244
<img src='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Memcached-OpenTelemetry/Memcached-Operations.png' alt="Memcached dashboards" />
248245

@@ -252,7 +249,6 @@ The **Memcached - Command Stats** dashboard provides detailed insights into the
252249

253250
<img src='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Memcached-OpenTelemetry/Memcached-Command-Stats.png' alt="Memcached dashboards" />
254251

255-
256252
### Cache Information
257253

258254
The **Memcached - Cache Information** dashboard provides insight into cache states, cache hit, and miss rate over time.
@@ -276,8 +272,8 @@ import CreateMonitors from '../../../reuse/apps/create-monitors.md';
276272

277273
| Name | Description | Alert Condition | Recover Condition |
278274
|:--|:--|:--|:--|
279-
| `Memcached - Cache Hit Ratio` | The hit rate is one of the most important indicators of Memcached performance. A high hit rate means faster responses to your users. If the hit rate is falling, you need quick visibility into why. This alert is triggered when low cache hit ratio is less than 50% | Count `<=` 50 | Count `>` 50 |
280-
| `Memcached - Commands Error` | This alert is triggered when Memcached has error commands. | Count `>` 0 | Count `<=` 0 |
281-
| `Memcached - Current Connections` | This alert is triggered when current connections to Memcached are zero. | Count `<=` 0 | Count `>` 0 |
282-
| `Memcached - High Memory Usage` | This alert is triggered when the memcached exceed given threshold memory usage (in GB) | Count `>` 5 | Count `<=` 5 |
283-
| `Memcached - High Number of Connections` | This alert is triggered when the number of current connection for memcached exceed given threshold. | Count `>=` 1000 | Count `<` 1000 |
275+
| `Memcached - Cache Hit Ratio` | This alert is triggered when low cache hit ratio is less than 50%. The hit rate is one of the most important indicators of Memcached performance. A high hit rate means faster responses to your users. If the hit rate is falling, you need quick visibility into why. | Count < = 50% | Count > 50% |
276+
| `Memcached - Commands Error` | This alert is triggered when Memcached has error commands. | Count > 0 | Count < = 0 |
277+
| `Memcached - Current Connections` | This alert is triggered when current connections to Memcached are zero. | Count < = 0 | Count > 0 |
278+
| `Memcached - High Memory Usage` | This alert is triggered when the Memcached exceed given threshold memory usage (in GB). | Count > 5 | Count < = 5 |
279+
| `Memcached - High Number of Connections` | This alert is triggered when the number of current connection for Memcached exceed given threshold. | Count > = 1000 | Count < 1000 |

0 commit comments

Comments
 (0)