MONGOC_APM_SE...D_SUCCEEDED_CB(3)

πŸ’… mongoc_apm_set_command_succeeded_cb β€” from the libmongoc manual, bestie 🫢

okay so picture this: you wanna know the second the driver finishes a MongoDB operation, right? like, not a vibe check later, but literally right then. that's this whole page. it's the mongoc_apm_..._command_succeeded_cb situation and it's iconic honestly.


✨ SYNOPSIS ✨

typedef void (*mongoc_apm_command_succeeded_cb_t) (
   const mongoc_apm_command_succeeded_t *event);

void
mongoc_apm_set_command_succeeded_cb (mongoc_apm_callbacks_t *callbacks,
                                     mongoc_apm_command_succeeded_cb_t cb);

so what does it do, you ask? no cap: receive an event notification whenever the driver completes a MongoDB operation. that's the whole gig πŸ’– like the driver finishing a MongoDB operation is the main character and your callback is the bestie it texts immediately.


πŸŽ€ PARAMETERS πŸŽ€

  • callbacks β€” a mongoc_apm_callbacks_t. yes queen, that's the callback container you're handing over.
  • cb β€” a function to call with a mongoc_apm_command_succeeded_t whenever the driver completes a MongoDB operation. so any time the driver wraps up a MongoDB operation, boom, your function gets summoned with that mongoc_apm_command_succeeded_t in hand πŸ”₯

🌈 SEE ALSO 🌈

  • Introduction to Application Performance Monitoring β€” go read it, iykyk πŸ¦‹

πŸ‘‘ AUTHOR πŸ‘‘

MongoDB, Inc β€” yeah, them. the ones who made this whole thing happen πŸ’œ


2009-present, MongoDB, Inc. β€” every year since 2009 and counting, no cap ⭐


fr fr bestie, that's the entire page. every flag, every type, every parameter β€” nothing skipped, nothing invented, just the facts served with a little garnish πŸ“

and that's a wrap on libmongoc version 2.5.6, dated Oct 09, 2026 β€” go forth and monitor those operations, you absolute icon πŸ’…βœ¨

πŸ“¦ where this page comes from