[DOCS-7354] What is the exact word used to refer to components in the mongod.log file? Created: 07/Mar/16  Updated: 11/Jan/17  Resolved: 20/Apr/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-3.2
Fix Version/s: 01112017-cleanup

Type: Task Priority: Major - P3
Reporter: SungGyun Im Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

Hi,

I have question about mongod.log components.

Different mongod.log components name and db.getLogComponents() components name.

What is the exact word used to refer to components in the mongod.log file?
Customer Alert system need exact word used to refer to components in the mongod.log file.
Please provide the exact word to refer to components.

https://docs.mongodb.org/manual/reference/log-messages/
Changed in version 3.0.

Starting in MongoDB 3.0, MongoDB includes the severity level and the component associated with each log message. The log messages have the form:

<timestamp> <severity> <component> [<context>] <message>

-------------------------
mongod.log : db.getLogComponents()

ACCESS : accessControl
COMMAND : command
CONTROL : control
??? : executor
??? : geo
INDEX : index
NETWORK : network
QUERY : query
REPL : replication
??? : sharding
STORAGE : storage
WRITE :write
FTDC :ftdc
ASIO : ???

2016-03-06T20:40:47.482+0900 I ACCESS   [conn18295] Successfully authenticated as principal mms-automation on admin
2016-03-07T10:53:40.663+0900 I COMMAND  [conn19233] command isgtest.foo command: insert { insert: "foo", documents: [ { _id: ObjectId('56dcdf240acbbdb4807e83a4'), x: 0.0, y: 3.0, z: "test" } ], ordered: true } ntoreturn:1 ntoskip:0 ninserted:1 keyUpdates:0 writeConflicts:0 numYields:0 reslen:85 locks:{ Global: { acquireCount: { r: 4, w: 4 } }, Database: { acquireCount: { w: 3, W: 1 } }, Collection: { acquireCount: { w: 1, W: 1 } }, Metadata: { acquireCount: { w: 2 } }, oplog: { acquireCount: { w: 2 } } } protocol:op_command 147ms
2016-03-06T20:37:25.438+0900 I CONTROL  [conn18289] modules: enterprise
2016-03-06T20:40:47.449+0900 I NETWORK  [initandlisten] connection accepted from 192.168.102.16:55434 #18295 (18 connections now open)
2016-03-07T13:48:16.009+0900 I QUERY    [conn13651] getmore local.oplog.rs query: { ts: { $gte: Timestamp 1457009877000|1 } } cursorid:34374520195 ntoreturn:0 keyUpdates:0 writeConflicts:0 exception: operation was interrupted code:11601 numYields:0 nreturned:1 reslen:71 locks:{ Global: { acquireCount: { r: 6 } }, Database: { acquireCount: { r: 3 } }, oplog: { acquireCount: { r: 3 } } } 1000ms
 
2016-03-07T12:23:32.326+0900 W NETWORK  [ReplicaSetMonitorWatcher] Failed to connect to 172.16.100.40:27017, reason: errno:113 No route to host
 
2016-03-07T13:48:26.351+0900 I FTDC     [conn19459] Shutting down full-time diagnostic data capture
2016-03-07T13:48:26.358+0900 I REPL     [conn19459] Stopping replication applier threads
2016-03-07T13:48:26.386+0900 I STORAGE  [conn19458] got request after shutdown()
2016-03-07T14:04:04.529+0900 I ASIO     [NetworkInterfaceASIO-BGSync-0] Successfully connected to 172.16.100.20:27017
`:

db.getLogComponents()
MongoDB Enterprise isgrepl:PRIMARY> db.getLogComponents()
{
	"verbosity" : 0,
	"accessControl" : {
		"verbosity" : -1
	},
	"command" : {
		"verbosity" : -1
	},
	"control" : {
		"verbosity" : -1
	},
	"executor" : {
		"verbosity" : -1
	},
	"geo" : {
		"verbosity" : -1
	},
	"index" : {
		"verbosity" : -1
	},
	"network" : {
		"verbosity" : -1,
		"asio" : {
			"verbosity" : -1
		},
		"bridge" : {
			"verbosity" : -1
		}
	},
	"query" : {
		"verbosity" : -1
	},
	"replication" : {
		"verbosity" : -1
	},
	"sharding" : {
		"verbosity" : -1
	},
	"storage" : {
		"verbosity" : -1,
		"journal" : {
			"verbosity" : -1
		}
	},
	"write" : {
		"verbosity" : -1
	},
	"ftdc" : {
		"verbosity" : -1
	}
}

Regards,
Sung Gyun



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Comment by Eric Milkie [ 15/Apr/16 ]

ACCESS : accessControl
COMMAND : command
CONTROL : control
EXECUTOR : executor
GEO : geo
INDEX : index
NETWORK : network
QUERY : query
REPL : replication
SHARDING : sharding
STORAGE : storage
JOURNAL : journal
WRITE : write
FTDC :ftdc
ASIO : asio

Comment by Stennie Steneker (Inactive) [ 07/Mar/16 ]

Hi,

I have moved this issue from the SERVER project to a documentation request, as it looks like some of the new log components in MongoDB 3.2 are not described yet.

You can find the full list of log component short names in the MongoDB source code: src/mongo/logger/log_component.cpp.

Regards,
Stephen

Generated at Thu Feb 08 07:54:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.