MONGOC_STRUCTU...MESSAGE_STRING(3)

📦
version 2.5.6 · 13 versions
, in epel 10

okay bestie, welcome to the MONGOC_STRUCTU...MESSAGE_STRING(3) page from libmongoc ✨ it's literally all about pulling the message string off a structured log entry, no cap.

✨ SYNOPSIS ✨

          const char *
          mongoc_structured_log_entry_get_message_string (const mongoc_structured_log_entry_t *entry);

🎀 PARAMETERS 🎀

  • entry — a mongoc_structured_log_entry_t pointer. That's the structured log entry you're asking for the message string from, bestie.

💖 RETURNS 💖

You get back a string 💅 and this part is important: it's guaranteed to be valid only during the lifetime of the structured log handler. So don't get attached and don't hang onto it after that, okay? It should not be freed or modified — nope, not yours to mess with.

This return value is identical to the value of the message key in the document returned by mongoc_structured_log_entry_message_as_bson().

Also lowkey important: this is not a complete string representation of the structured log. It's a standardized identifier for a particular log event. So it's more like the event's name tag than the whole story, iykyk.

👀 SEE ALSO: Structured Logging

🌸 AUTHOR 🌸

MongoDB, Inc

2009-present, MongoDB, Inc.

okay that's the whole vibe 🫶 this page is from libmongoc version 2.5.6, dated Oct 09, 202. periodt. 💅

📦 where this page comes from