chore(bridges): increase log level for bridge buffer overflow reports

Co-authored-by: Andrew Mayorov <encube.ul@gmail.com>

apps/emqx_conf/src/emqx_conf_schema.erl

@@ -85,7 +85,8 @@
     cannot_publish_to_topic_due_to_quota_exceeded,
     connection_rejected_due_to_license_limit_reached,
     dropped_msg_due_to_mqueue_is_full,
-    socket_receive_paused_by_rate_limit
+    socket_receive_paused_by_rate_limit,
+    data_bridge_buffer_overflow
 ]).
 
 %% Callback to upgrade config after loaded from config file but before validation.

apps/emqx_resource/src/emqx_resource.app.src

@@ -1,7 +1,7 @@
 %% -*- mode: erlang -*-
 {application, emqx_resource, [
     {description, "Manager for all external resources"},
-    {vsn, "0.1.29"},
+    {vsn, "0.1.30"},
     {registered, []},
     {mod, {emqx_resource_app, []}},
     {applications, [

apps/emqx_resource/src/emqx_resource_buffer_worker.erl

@@ -1777,8 +1777,8 @@ append_queue(Id, Index, Q, Queries) ->
                 ok = replayq:ack(Q1, QAckRef),
                 Dropped = length(Items2),
                 Counters = #{dropped_queue_full => Dropped},
-                ?SLOG(info, #{
-                    msg => "buffer_worker_overflow",
+                ?SLOG_THROTTLE(warning, #{
+                    msg => data_bridge_buffer_overflow,
                     resource_id => Id,
                     worker_index => Index,
                     dropped => Dropped

changes/ce/feat-13144.en.md

@@ -0,0 +1 @@
+Emit a `warning` level throttled log when bridge buffers are overflown and messages get dropped. Previously, the log events had `info` level and were not visible with the default log level.