You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This app includes [built-in monitors](#rabbitmq-alerts). For details on creating custom monitors, refer to the [Create monitors for RabbitMQ app](#create-monitors-for-rabbitmq-app).
20
+
:::
21
+
18
22
## Fields creation in Sumo Logic for RabbitMQ
19
23
20
24
Following are the [Fields](/docs/manage/fields/) which will be created as part of RabbitMQ App install if not already present.
@@ -230,3 +234,20 @@ The **RabbitMQ - Logs** dashboard gives you an at-a-glance view of error message
230
234
The **RabbitMQ - Metrics** dashboard gives you an at-a-glance view of your RabbitMQ deployment across brokers, queue, exchange, consumer, and messages.
|`RabbitMQ - High Consumer Count`| This alert is triggered when consumers are higher than given value (Default 10000) in a queue. | Count `>=` 10000 | Count `<` 10000 |
249
+
|`RabbitMQ - High Message Queue Size`| This alert is triggered when the number of messages in a queue exceeds a given threshold (Default 10000), indicating potential consumer issues or message processing bottlenecks. | Count `>=` 10000 | Count `<` 10000 |
250
+
|`RabbitMQ - High Messages Count`| This alert is triggered when messages are higher than given value (Default 10000) in a queue. | Count `>=` 10000 | Count `<` 10000 |
251
+
|`RabbitMQ - High Unacknowledged Messages`| This alert is triggered when there are too many unacknowledged messages (Default 5000), suggesting consumer processing issues. | Count `>=` 5000 | Count `<` 5000 |
252
+
|`RabbitMQ - Node Down`| This alert is triggered when a node in the RabbitMQ cluster is down. | Count `>=` 1 | Count `<` 1 |
253
+
|`RabbitMQ - Zero Consumers Alert`| This alert is triggered when a queue has no consumers, indicating potential service issues. | Count `<=` 0 | Count `>` 0 |
Copy file name to clipboardExpand all lines: docs/integrations/databases/opentelemetry/cassandra-opentelemetry.md
+41-27Lines changed: 41 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
id: cassandra-opentelemetry
3
3
title: Cassandra - OpenTelemetry Collector
4
4
sidebar_label: Cassandra - OTel Collector
5
-
description: Learn about the Sumo Logic OpenTelemetry App for Cassandra.
5
+
description: Learn about the Sumo Logic OpenTelemetry app for Cassandra.
6
6
---
7
7
8
8
import useBaseUrl from '@docusaurus/useBaseUrl';
@@ -15,10 +15,14 @@ The [Cassandra](https://cassandra.apache.org/_/cassandra-basics.html) app is a l
15
15
16
16
Cassandra logs are sent to Sumo Logic through OpenTelemetry [filelog receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver) and cassandra metrics are sent to Sumo Logic using [JMX opentelemetry receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/jmxreceiver) with the `target_system` set as [`cassandra`](https://github.com/open-telemetry/opentelemetry-java-contrib/blob/main/jmx-metrics/docs/target-systems/cassandra.md).
17
17
18
-
The app supports Logs from the open-source version of Cassandra. The App is tested on the 4.0.0 version of Cassandra.
18
+
The app supports logs from the open-source version of Cassandra. The app is tested on the 4.0.0 version of Cassandra.
This app includes [built-in monitors](#cassandra-alerts). For details on creating custom monitors, refer to the [Create monitors for Cassandra app](#create-monitors-for-cassandra-app).
24
+
:::
25
+
22
26
## Fields creation in Sumo Logic for Cassandra
23
27
24
28
Following are the [Fields](/docs/manage/fields/) which will be created as part of Cassandra App install if not already present:
@@ -36,17 +40,17 @@ Following are the [Fields](/docs/manage/fields/) which will be created as part o
36
40
JMX receiver collects Cassandra metrics from Cassandra server as part of the OpenTelemetry Collector (OTC).
37
41
38
42
1. Follow the instructions in [JMX - OpenTelemetry's prerequisites section](/docs/integrations/app-development/opentelemetry/jmx-opentelemetry/#prerequisites) to download the [JMX Metric Gatherer](https://github.com/open-telemetry/opentelemetry-java-contrib/blob/main/jmx-metrics/README.md). This gatherer is used by the [JMX Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/jmxreceiver#details).
39
-
40
43
2. Set the JMX port as part of `JAVA_OPTS` for Tomcat startup. Usually, it is set in the `/etc/systemd/system/cassandra.service` or `C:\Program Files\apache-tomcat\bin\tomcat.bat` file.
Cassandra has three main logs: system.log, debug.log, and gc.log which hold general logging messages, debugging logging messages, and java garbage collection logs respectively.
48
50
49
-
These logs by default live in `${CASSANDRA_HOME}/logs`, but most Linux distributions relocate logs to `/var/log/cassandra`. Operators can tune this location as well as what levels are logged using the provided logback.xml file. For more details on Cassandra logs, see[ this](https://cassandra.apache.org/doc/latest/troubleshooting/reading_logs.html) link.
51
+
Cassandra has three main logs: `system.log`, `debug.log`, and `gc.log`, which hold general logging messages, debugging logging messages, and java garbage collection logs respectively.
52
+
53
+
These logs by default live in `${CASSANDRA_HOME}/logs`, but most Linux distributions relocate logs to `/var/log/cassandra`. Operators can tune this location as well as what levels are logged using the provided logback.xml file. For more details on Cassandra logs, see [this](https://cassandra.apache.org/doc/latest/troubleshooting/reading_logs.html).
50
54
51
55
import LogsCollectionPrereqisites from '../../../reuse/apps/logs-collection-prereqisites.md';
52
56
@@ -78,7 +82,7 @@ You can add any custom fields which you want to be tagged with the data ingested
The **Cassandra - Cache Stats** dashboard provides insight into the database cache status, schedule, and items.
217
-
218
-
Use this dashboard to:
219
-
220
-
- Monitor Cache performance.
221
-
- Identify Cache usage statistics.
221
+
The **Cassandra - Cache Stats** dashboard provides insight into the database cache status, schedule, and items. Use this dashboard to monitor cache performance and identify cache usage statistics.
The **Cassandra - Resource Usage** dashboard provides details of resource utilization across Cassandra clusters.
260
-
261
-
Use this dashboard to:
262
-
263
-
- Identify resource utilization. This can help you to determine whether resources are over-allocated or under-allocated.
255
+
The **Cassandra - Resource Usage** dashboard provides details of resource utilization across Cassandra clusters. Use this dashboard to identify resource utilization. This can help you to determine whether resources are over-allocated or under-allocated.
The **Cassandra - Requests** dashboard provides insight into the number of request served, number of error request, and their distribution by status and operation. Also you can monitor the read and write latency of the cluster instance using this dashboard.
The **Cassandra - Storage** dashboard provides insight into the current value of total hints of your Cassandra cluster along with storage managed by the cluster.
|`Cassandra - Compaction Task Pending`| This alert is triggered when there are more than 15 pending Compaction tasks. | Count > = 15 | Count < 15 |
288
+
|`Cassandra - High Hints Backlog`| This alert is triggered when the number of in-progress hints exceeds the given value for 5 minutes. | Count > = 5000 | Count < 5000 |
289
+
|`Cassandra - High Memory Usage`| This alert is triggered when memory used exceeds 85% of committed memory for more than 10 minutes. | Count > = 1 | Count < 1 |
290
+
|`Cassandra - Node Down Alert`| This alert is triggered when a Cassandra node status changes to DOWN for more than 5 minutes. | Count > = 1 | Count < 1 |
291
+
|`Cassandra - Operation Error Rate High`| This alert is triggered when the error rate of operations exceeds given value (Default 5%) for 5 minutes. | Count > 5 | Count < = 5 |
292
+
|`Cassandra - Range Query Latency High (99th Percentile)`| This alert is triggered when the 99th percentile of range query latency exceeds the given value (Default 2 seconds) for 5 minutes. | Count > = 2000000 | Count < 2000000 |
293
+
|`Cassandra - Read Latency High (99th Percentile)`| This alert is triggered when the 99th percentile of read latency exceeds given value (Default 500ms) for 5 minutes. | Count > = 500000 | Count < 500000 |
294
+
|`Cassandra - Storage Growth Rate Abnormal`| This alert is triggered when the storage growth rate exceeds given value (Default 25MB/minute) for 5 minutes. | Count > = 26214400 | Count < 26214400 |
295
+
|`Cassandra - Write Latency High (99th Percentile)`| This alert is triggered when the 99th percentile of write latency exceeds given value (Default 200ms) for 5 minutes. | Count > = 200000 | Count < 200000 |
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).
24
+
:::
25
+
22
26
## Fields creation in Sumo Logic for Memcached
23
27
24
28
Following are the [Fields](/docs/manage/fields/) which will be created as part of Memcached App install if not already present.
25
29
26
30
-**`sumo.datasource`**. Has a fixed value of **memcached**.
27
-
-**`db.system`**. Has a fixed value of **memcached**
28
-
-**`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.
29
33
-**`db.cluster.name`**. User configured. Enter a name to identify this Memcached cluster. This cluster name will be shown in the Sumo Logic dashboards.
30
34
-**`db.node.name`**. This has value of the FQDN of the machine where OpenTelemetry collector is collecting logs and metrics from.
31
35
32
-
33
36
## Prerequisites
34
37
35
38
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:
@@ -221,13 +224,12 @@ Following is the query from Errors panel of Memcached app's overview Dashboard:
221
224
| sum(ERROR) as ERROR by _timeslice
222
225
```
223
226
## Sample metrics queries
224
-
**Total Get**
225
227
226
-
```
228
+
```sql title="Total Get"
227
229
sumo.datasource=memcached deployment.environment=* db.cluster.name=* db.node.name=* metric=memcached.commands command=get | sum
228
230
```
229
231
230
-
## Viewing Memcached Dashboards
232
+
## Viewing the Memcached dashboards
231
233
232
234
### Overview
233
235
@@ -237,7 +239,7 @@ The **Memcached - Overview** dashboard provides an at-a-glance view of the Memca
237
239
238
240
### Operations
239
241
240
-
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, andtable size.
| `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