chore: refresh automatic content (#418)

Author: mensfeld

Development/Karafka-Integration-Tests-Catalog.md

@@ -355,6 +355,7 @@
 | `instrumentation/vendors/appsignal/errors_flow_spec.rb` | Here we ensure that our error tracker works as expected |
 | `instrumentation/vendors/appsignal/metrics_flow_spec.rb` | Here we subscribe to our listener and make sure nothing breaks during the notifications We use a dummy client that will intercept calls that should go to Appsignal and check basic metrics presence |
 | `instrumentation/vendors/appsignal/with_original_client_pristine/with_proper_tracing_spec.rb` | This spec ensures, we do not use by accident ActiveSupport methods when working with listeners @see https://github.com/karafka/karafka/pull/1624 |
+| `instrumentation/vendors/datadog/custom_listener_with_empty_rd_kafka_metrics_spec.rb` | This test demonstrates that when rd_kafka_metrics is set to an empty array, no statistics-derived metrics will be published even though on_statistics_emitted is still being called. This test was created to help diagnose a user-reported issue where statistics metrics were not appearing in DataDog. The root cause was setting rd_kafka_metrics = [] in the listener configuration. |
 | `instrumentation/vendors/datadog/custom_listener_with_overridden_methods_spec.rb` | This test verifies that statistics.emitted events are properly propagated to custom listeners that inherit from the DataDog MetricsListener and override some (but not all) event handlers. This is a regression test for a user-reported issue where a custom listener that overrode methods like on_connection_listener_fetch_loop_received, on_consumer_revoked, etc. appeared to not receive statistics.emitted events. The test mimics the user's setup: - Custom listener inheriting from Karafka::Instrumentation::Vendors::Datadog::MetricsListener - Overrides several methods with no-op implementations to suppress unwanted metrics - Does NOT override on_statistics_emitted, relying on parent implementation |
 | `instrumentation/vendors/datadog/logger_flow_spec.rb` | Here we subscribe to our listener and make sure nothing breaks during the notifications We use a dummy client that will intercept calls that should go to DataDog |
 | `instrumentation/vendors/datadog/metrics_flow_spec.rb` | Here we subscribe to our listener and make sure nothing breaks during the notifications We use a dummy client that will intercept calls that should go to DataDog and check basic metrics presence |