In the dashboard you referenced, I noticed that the oplog lag was based on mongodb_replset_oplog_head_timestamp but IMO it should use use the tail counterpart mongodb_replset_oplog_tail_timestamp no?
The head according to collector/oplog_status.go is calling GetOplogTimestamp(.., false) which will show the oldest value instead of the newest.
Btw, head should be the most recent and tail the oldest oplog entry don't you think?
It might not have it's place here but I don't know how to contact the one maintaining the dashboard and you referenced it.
In the dashboard you referenced, I noticed that the oplog lag was based on
mongodb_replset_oplog_head_timestampbut IMO it should use use the tail counterpartmongodb_replset_oplog_tail_timestampno?The head according to
collector/oplog_status.gois callingGetOplogTimestamp(.., false)which will show the oldest value instead of the newest.Btw, head should be the most recent and tail the oldest oplog entry don't you think?
It might not have it's place here but I don't know how to contact the one maintaining the dashboard and you referenced it.