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
[MongoDB](https://www.mongodb.com/why-use-mongodb#:~:text=MongoDB%20is%20a%20document%20database,development%20teams%20using%20agile%20methodologies.) is a source-available cross-platform document-oriented database program. The Sumo Logic app for MongoDB supports logs and metrics from the open source version of MongoDB. The App is tested on the 4.4.4 version of MongoDB.
14
+
[MongoDB](https://www.mongodb.com/why-use-mongodb#:~:text=MongoDB%20is%20a%20document%20database,development%20teams%20using%20agile%20methodologies.) is a source-available cross-platform document-oriented database program. The Sumo Logic app for MongoDB supports logs and metrics from the open source version of MongoDB. The app is tested on the 7.0.14 version of MongoDB.
15
15
16
-
MongoDB logs are sent to Sumo Logic through OpenTelemetry [filelog receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver).
16
+
MongoDB logs are sent to Sumo Logic through OpenTelemetry [filelog receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver). The OpenTelemetry collector runs on the same host as MongoDB and uses the [MongoDB Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/mongodbreceiver) and the [Sumo Logic OpenTelemetry Exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/sumologicexporter) to send the metrics to Sumo Logic.
The MongoDB logs are generated in files as configured in the configuration file `/var/log/mongodb/mongodb.log`. For more details on MongoDB logs, see [this](https://docs.mongodb.com/manual/reference/log-messages/) link.
22
+
This app supports logs and metrics for MongoDB instance. The MongoDB logs are generated in files as configured in this configuration file `/var/log/mongodb/mongodb.log`. For more details on MongoDB logs, refer to the [MongoDB documentation](https://docs.mongodb.com/manual/reference/log-messages/).
23
+
24
+
The app supports metrics generated by the [MongoDB Receiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/mongodbreceiver/documentation.md).
23
25
24
26
## Fields creation in Sumo Logic for MongoDB
25
27
@@ -29,19 +31,28 @@ Following are the [Fields](/docs/manage/fields/) which will be created as part o
29
31
-**`db.system`**. Has fixed value of **mongodb**.
30
32
-**`deployment.environment`**. User configured. This is the deployment environment where the Mongodb cluster resides. For example: dev, prod or qa.
31
33
-**`sumo.datasource`**. has a fixed value of **mongodb**.
34
+
***`db.node.name`**. Has the value of host name of the machine which is being monitored.
32
35
33
36
## Prerequisites
34
37
38
+
### For metrics collection
39
+
40
+
The MongoDB receiver fetches stats from a MongoDB instance using the [golang mongo driver](https://github.com/mongodb/mongo-go-driver). Stats are collected via MongoDB's `dbStats` and `serverStatus` commands. The MongoDB receiver extracts values from the result and converts them to OpenTelemetry metrics.
41
+
42
+
### For logs collection
43
+
35
44
By default, MongoDB logs are stored in a log file.
36
45
37
-
1. Configure logging verbosity in MongoDB : MongoDB logs have six levels of verbosity. All logging settings are located in [MongoDB.conf](https://docs.mongodb.com/manual/reference/method/db.setLogLevel/). To select a level, set loglevel to one of:
46
+
1. Configure logging verbosity in MongoDB.<br/>MongoDB logs have six levels of verbosity. All logging settings are located in [MongoDB.conf](https://docs.mongodb.com/manual/reference/method/db.setLogLevel/). To select a level, set loglevel to one of:
38
47
- 0 is the MongoDB's default log verbosity level, to include [Informational](https://docs.mongodb.com/manual/reference/log-messages/#std-label-log-severity-levels) messages.
39
48
- 1 to 5 increases the verbosity level to include[ Debug](https://docs.mongodb.com/manual/reference/log-messages/#std-label-log-severity-levels) messages.
40
-
2. Configure MongoDB to log to a Local file: Configuring MongoDB logs to go to log files. By default, MongoDB logs are stored in `/var/log/mongodb/mongodb.log`. The default directory for log files is listed in the MongoDB.conf file. To configure the log output destination to a log file, use one of the following settings, either in the [configuration file](https://docs.mongodb.com/manual/reference/configuration-options/) or command-line:
49
+
2. You need to set the [profiling_level](https://www.mongodb.com/docs/manual/reference/method/db.setProfilingLevel/) to a value of 1. <br/>But by default it is set to 0. You can also configure the value of [slowms](https://www.mongodb.com/docs/manual/reference/method/db.setProfilingLevel/#std-label-set-profiling-level-options-slowms) to a value greater than or equal to 100. Thus can be done using the below command in mongosh:
50
+
`db.setProfilingLevel(1,100)`
51
+
3. Configure MongoDB to log to a local file. <br/>By default, MongoDB logs are stored in `/var/log/mongodb/mongodb.log`. The default directory for log files is listed in the `MongoDB.conf` file. To configure the log output destination to a log file, use one of the following settings, either in the [configuration file](https://docs.mongodb.com/manual/reference/configuration-options/) or command-line:
41
52
- Configuration file: The [systemLog.destination](https://docs.mongodb.com/manual/reference/configuration-options/#mongodb-setting-systemLog.destination) option for file.
42
-
- Command-line:
43
-
- The [--logpath](https://docs.mongodb.com/manual/reference/program/mongod/#std-option-mongod.--logpath) option for [mongod](https://docs.mongodb.com/manual/reference/program/mongod/#mongodb-binary-bin.mongod) for file.
44
-
- The [--logpath](https://docs.mongodb.com/manual/reference/program/mongos/#std-option-mongos.--logpath) option for [mongos](https://docs.mongodb.com/manual/reference/program/mongos/#mongodb-binary-bin.mongos) for file.
53
+
- Command-line:
54
+
- The [--logpath](https://docs.mongodb.com/manual/reference/program/mongod/#std-option-mongod.--logpath) option for [mongod](https://docs.mongodb.com/manual/reference/program/mongod/#mongodb-binary-bin.mongod) for file.
55
+
- The [--logpath](https://docs.mongodb.com/manual/reference/program/mongos/#std-option-mongos.--logpath) option for [mongos](https://docs.mongodb.com/manual/reference/program/mongos/#mongodb-binary-bin.mongos) for file.
45
56
46
57
import LogsCollectionPrereqisites from '../../../reuse/apps/logs-collection-prereqisites.md';
47
58
@@ -79,9 +90,22 @@ import SetupColl from '../../../reuse/apps/opentelemetry/set-up-collector.md';
79
90
80
91
### Step 2: Configure integration
81
92
82
-
In this step the user needs to provide the path to the mongo db log file configured as part of above steps. Typically the logs are located at the location: `/var/log/mongodb/mongodb.log`.
93
+
OpenTelemetry works with a [configuration](https://opentelemetry.io/docs/collector/configuration/) YAML file with all the details concerning the data that needs to be collected. For example, it specifies the location of a log file that is read and sent to the Sumo Logic platform.
94
+
95
+
In this step, you will configure the YAML file required for MongoDB collection.
96
+
97
+
Below are the inputs required:
98
+
99
+
-**`Endpoint (no default)`**. The hostname and port of the MognoDB instance, separated by a colon. (For example: `localhost:27017`.)
100
+
-**`Logs Path`**. Provide the path to the mongo db log file configured as part of above steps. Typically the logs are located at the location: `/var/log/mongodb/mongodb.log`.
101
+
-**`username (optional)`**. If authentication is required, the user can with clusterMonitor permissions can be provided here.
102
+
-**`password (optional)`**. If authentication is required, the password can be provided here.
103
+
104
+
You can add any custom fields which you want to tag along with the data ingested in Sumo. Click on the **Download YAML File** button to get the YAML file.
83
105
84
-
You can add any custom fields which you want to tag along with the data ingested in Sumo. Click on the **Download YAML File** button to get the yaml file.
106
+
Click on the **Download YAML File** button to get the YAML file.
107
+
108
+
For Linux platform, click **Download Environment Variables File** to get the file with the password which is supposed to be set as environment variable.
@@ -241,8 +269,8 @@ The **MongoDB - Logins and Connections** dashboard shows geo location of client
241
269
242
270
Use this dashboard to:
243
271
244
-
-Determine potential hacking attempts.
245
-
-Determine location of attacks.
272
+
- Determine potential hacking attempts.
273
+
- Determine location of attacks.
246
274
247
275
<imgsrc='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/MongoDB-OpenTelemetry/MongoDB-Logins-and-Connections.png'alt="Logins and Connections" />
248
276
@@ -252,29 +280,59 @@ The **MongoDB - Query Logs** dashboard shows read and write query trends.
252
280
253
281
Use this dashboard to:
254
282
255
-
-Monitor abnormal spikes in Query volume.
256
-
-Identify the read versus write ratio of your application queries. Adjusting indexes to improve query performance.
283
+
- Monitor abnormal spikes in query volume.
284
+
- Identify read versus write ratio of your application queries. This helps you to adjust indexes to improve query performance.
Copy file name to clipboardExpand all lines: docs/integrations/databases/opentelemetry/redis-opentelemetry.md
+20-12Lines changed: 20 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,9 +75,9 @@ import SetupColl from '../../../reuse/apps/opentelemetry/set-up-collector.md';
75
75
76
76
### Step 2: Configure integration
77
77
78
-
OpenTelemetry works with a [configuration](https://opentelemetry.io/docs/collector/configuration/)yaml file with all the details concerning the data that needs to be collected. For example, it specifies the location of a log file that is read and sent to the Sumo Logic platform.
78
+
OpenTelemetry works with a [configuration](https://opentelemetry.io/docs/collector/configuration/)YAML file with all the details concerning the data that needs to be collected. For example, it specifies the location of a log file that is read and sent to the Sumo Logic platform.
79
79
80
-
In this step, you will configure the yaml file required for Redis Collection.
80
+
In this step, you will configure the YAML file required for Redis Collection.
81
81
82
82
Below are the inputs required:
83
83
@@ -86,7 +86,11 @@ Below are the inputs required:
86
86
87
87
The log file path configured to capture redis logs must be given here. The files are typically located in `/var/log/redis/redis-server.log`. If you are using a customized path, check the [`redis.conf`](https://download.redis.io/redis-stable/redis.conf) file for this information.
88
88
89
-
You can add any custom fields which you want to tag along with the data ingested in Sumo. Click on the **Download YAML File** button to get the yaml file.
89
+
You can add any custom fields which you want to tag along with the data ingested in Sumo. Click on the **Download YAML File** button to get the YAML file.
90
+
91
+
Click on the **Download YAML File** button to get the YAML file.
92
+
93
+
For Linux platform, click **Download Environment Variables File** to get the file with the password which is supposed to be set as environment variable.
0 commit comments