MONGOC_STRUCT...ALL_COMPONENTS(3)

πŸ’… MONGOC_STRUCT...ALL_COMPONENTS(3) πŸ’…

okay bestie, this one comes from libmongoc and it's lowkey iconic for getting all your structured log levels in formation. Let's get into it. 🫢

✨ SYNOPSIS ✨

          bool
          mongoc_structured_log_opts_set_max_level_for_all_components (mongoc_structured_log_opts_t *opts,
                                                                       mongoc_structured_log_level_t level);

This function sets all per-component maximum log levels to the same value. Only log messages at or below this severity level will be passed to mongoc_structured_log_func_t. It's effective even for logging components not known at compile-time β€” yes, even the surprise ones. No cap. 😭✨

πŸŽ€ PARAMETERS πŸŽ€

  • opts β€” Structured log options, allocated with mongoc_structured_log_opts_new(). This is the main character setup.
  • level β€” The max log level for all components, as a mongoc_structured_log_level_t.

πŸ”₯ RETURNS πŸ”₯

Returns true on success, or false if the supplied parameters were incorrect. That's the vibe check. periodt. πŸ’…

πŸ‘€ SEE ALSO πŸ‘€

Structured Logging β€” go read that if you want the full lore. iykyk. πŸ¦‹

πŸ’œ AUTHOR πŸ’œ

MongoDB, Inc

2009-present, MongoDB, Inc.


bestie, that's the whole page πŸ’– sourced from libmongoc, version 2.5.6, dated Oct 09, 2026. slay and stay logged βœ¨πŸ’…

πŸ“¦ where this page comes from