MONGOC_APM_CO...T_COMMAND_NAME(3)

✨ MONGOC_APM_CO...T_COMMAND_NAME(3) ✨

okay bestie, welcome to the libmongoc corner of the manual πŸ’… this one's a tiny lil guy from mongoc_apm_command_succeeded_get_command_name and it's literally so simple, you're gonna eat this up.


🌸 SYNOPSIS 🌸

const char *
mongoc_apm_command_succeeded_get_command_name (
   const mongoc_apm_command_succeeded_t *event);

So like, you hand it an event, and it gives you back that event's command name. That's it. That's the whole vibe. πŸŽ€

⚠️ but bestie listen β€” the data is only valid in the scope of the callback that receives this event. So if you're gonna touch it after the callback returns, you gotta copy it. no cap. don't be out here holding a dangling pointer, that's not the main character energy we want 😭

πŸ¦‹ PARAMETERS πŸ¦‹

  • event β€” a mongoc_apm_command_succeeded_t. that's the whole parameter list. one (1) thing. slay ✨

⭐ RETURNS ⭐

A string 🌈 β€” and you should not modify it or free it. it's not yours, it's just visiting. hands off, king πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

  • Introduction to Application Performance Monitoring β€” go read it, iykyk 🫢

πŸ’œ AUTHOR πŸ’œ

MongoDB, Inc β€” iconic behavior, honestly πŸ‘‘


2009-present, MongoDB, Inc. β€” periodt πŸ’…


and that's the whole page, bestie!! no crumbs left πŸ“

🌟 this has been libmongoc 2.5.6, dated Oct 09, 2026 β€” now go forth and get that command name (within the callback scope, obviously) πŸ’–πŸ¦‹βœ¨
πŸ“¦ where this page comes from