MONGOC_APM_COM...EDED_GET_REPLY(3)

📦
version 2.5.6 · 16 versions
, in epel 10

💅 MONGOC_APM_COMMAND_SUCCEEDED_GET_REPLY(3) — libmongoc

okay bestie, so the header up top got tragically truncated to MONGOC_APM_COM...EDED_GET_REPLY(3) (the ellipsis is doing main character work, honestly), but the real name is mongoc_apm_command_succeeded_get_reply, and it lives in libmongoc. She's a little accessor function, she has one job, and she ate. 🎀

✨ SYNOPSIS ✨

const bson_t *
mongoc_apm_command_succeeded_get_reply (
   const mongoc_apm_command_succeeded_t *event);

So you hand her a command-succeeded event, and she hands you back that event's reply. That's it. That's the whole vibe. 🦋

⚠️ read this twice, bestie, fr fr: the data is only valid in the scope of the callback that receives this event. Like, the pointer is literally not yours after that. If you're gonna touch it after the callback returns, copy it. No cap. Hold onto the raw pointer and you're gonna have a bad time. 💀

🌸 PARAMETERS 🌸

  • event — a mongoc_apm_command_succeeded_t. That's the one. That's the whole list. 🫶

⭐ RETURNS ⭐

A bson_t that should not be modified or freed. Like, look at her, don't touch her. You did not birth that bson_t, so you do not get to free that bson_t. 🙈

👑 SEE ALSO 👑

Introduction to Application Performance Monitoring — go read it, iykyk, it's the whole context for why these APM events exist in the first place. ✨

💜 AUTHOR 💜

MongoDB, Inc — slay.

2009-present, MongoDB, Inc. — periodt.

cute little sign-off: this page is from libmongoc version 2.5.6, dated Oct 09, 202… (the footer got clipped mid-date by the truncation gremlin, we love that for us 😭). anyway bestie go copy that bson_t, ily, bye! 💖🧚‍♀️

📦 where this page comes from