# Packetbeat parsing MongoDB 5.0

**URL:** <https://discuss.elastic.co/t/packetbeat-parsing-mongodb-5-0/287490>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [October 23, 2021, 1:47pm UTC](https://discuss.elastic.co/t/packetbeat-parsing-mongodb-5-0/287490 "2021-10-23T13:47:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chinaxushi](https://avatars.discourse-cdn.com/v4/letter/c/51bf81/32.png) [@chinaxushi](https://discuss.elastic.co/u/chinaxushi)\
**Post date:** [October 23, 2021, 1:47pm UTC](https://discuss.elastic.co/t/packetbeat-parsing-mongodb-5-0/287490/1 "2021-10-23T13:47:55Z")

</div>

In version 5.0, MongoDB deprecates the following opcodes:

- `OP_REPLY`
- `OP_UPDATE`
- `OP_INSERT`
- `OP_QUERY` [[1]](https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/#footnote-op-query-footnote)
- `OP_GET_MORE`
- `OP_DELETE`
- `OP_KILL_CURSORS`

Instead of these opcodes, use [OP\_MSG](https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/#std-label-wire-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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 20, 2021, 3:48pm UTC](https://discuss.elastic.co/t/packetbeat-parsing-mongodb-5-0/287490/2 "2021-11-20T15:48:35Z")

</div>

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