Packetbeat parsing MongoDB 5.0

Elastic Stack Beats
1

In version 5.0, MongoDB deprecates the following opcodes:

  • OP_REPLY
  • OP_UPDATE
  • OP_INSERT
  • OP_QUERY [1]
  • OP_GET_MORE
  • OP_DELETE
  • OP_KILL_CURSORS

Instead of these opcodes, use OP_MSG.

Now op_ MSG information cannot be parsed. In the mongodb output of packetbeat, there is only MSG type, but the detailed information is empty.

This problem should have existed in mongodb4. X before. Haven't you encountered it. But now 5.0 completely abandons other ops_ XXX. All the data can't be seen

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.