Use LM_DBG instead of LM_WARN for full table scan messages in db_redis #### Pre-Submission Checklist
- [X] Commit message has the format required by CONTRIBUTING guide - [X] Commits are split per component (core, individual modules, libs, utils, ...) - [X] Each component has a single commit (if not, squash them into one commit) - [X] Code is formatted with `clang-format` using the config file `.clang-format` from source code folder - [X] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [X] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist: - [ ] PR should be backported to stable branches - [X] Tested changes locally #### Description ull table scans in db_redis are currently logged using LM_WARN, even during normal operation. In environments where these scans are expected, the warning messages can generate excessive log noise and make real issues harder to spot. This change switches the log level to LM_DBG so the messages remain available for troubleshooting while avoiding unnecessary warning spam. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4748 -- Commit Summary -- * db_redis: Adjust log level in Redis dbase from warning to debug -- File Changes -- M src/modules/db_redis/redis_dbase.c (10) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4748.patchhttps://github.com/kamailio/kamailio/pull/4748.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4748 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/[email protected]>
_______________________________________________ Kamailio - Development Mailing List -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
