karafka-web 0.8.2 → 0.9.0.rc2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 457da6c2e847225be5d27f3a30fcf8f99a4a132f8109204315ac042e24d1bd35
-  data.tar.gz: c277f44c30a34ee2748ac4e9b56833814b522da87f6cc1841d21aca618af58be
+  metadata.gz: aa87182151f35775e4c08d82e4cebebddaf415d6893eddb4cfae32ccf061556f
+  data.tar.gz: 04b0e2c45d8086cb71bc0cfe6069cfb125f2d6694ee503e7445bca924c814d46
 SHA512:
-  metadata.gz: 9ff1df82abd7f4f9f7002ae8a9e3e4e3fef2a71fbac820ff700d52c1926a5a81bf8e141ac6b928693d6276d8c16ef496efc11cada7574da217f4fb31efe31b5b
-  data.tar.gz: 3f39b8155794c25a39464d71c35f33ee82e6b59f92b55301f20ff69f1c58bc2cdf32af976720c548c2262893e25e0f8c8d31b8c033a248feb929bd088bc46d6c
+  metadata.gz: 899a189e1c102899846826a739f21a1e4eee1ad44f828864e7a2019e395c038e69bca8dd22074da87ddab46af1f40070c70a7f2022885378aeb806cb4f7c2389
+  data.tar.gz: 66848f79f9460e42ccd45fbb9e28adbb70651356193a5c2d5826ccc214ad42e2df4b784b5872985f41c22cd5116563bc243306c5b0b1bd43da4ce9f575371a3f

data/.github/workflows/ci.yml

@@ -26,7 +26,6 @@ jobs:
           - '3.2'
           - '3.1'
           - '3.0'
-          - '2.7'
         include:
           - ruby: '3.3'
             coverage: 'true'
@@ -35,9 +34,9 @@ jobs:
       - name: Install package dependencies
         run: "[ -e $APT_DEPS ] || sudo apt-get install -y --no-install-recommends $APT_DEPS"
 
-      - name: Start Kafka with docker-compose
+      - name: Start Kafka with docker compose
         run: |
-          docker-compose up -d || (sleep 5 && docker-compose up -d)
+          docker compose up -d || (sleep 5 && docker compose up -d)
 
       - name: Set up Ruby
         uses: ruby/setup-ruby@v1
@@ -48,25 +47,15 @@ jobs:
 
       - name: Install latest bundler
         run: |
-          if [[ "$(ruby -v | awk '{print $2}')" == 2.7.8* ]]; then
-            gem install bundler -v 2.4.22 --no-document
-            gem update --system 3.4.22 --no-document
-          else
-            gem install bundler --no-document
-            gem update --system --no-document
-          fi
+          gem install bundler --no-document
+          gem update --system --no-document
 
           bundle config set without 'tools benchmarks docs'
 
       - name: Bundle install
         run: |
           bundle config set without development
-
-          if [[ "$(ruby -v | awk '{print $2}')" == 2.7.8* ]]; then
-            BUNDLER_VERSION=2.4.22 bundle install --jobs 4 --retry 3
-          else
-            bundle install --jobs 4 --retry 3
-          fi
+          bundle install --jobs 4 --retry 3
 
       - name: Wait for Kafka
         run: |

data/CHANGELOG.md

@@ -1,5 +1,45 @@
 # Karafka Web changelog
 
+## 0.9.0 (Unreleased)
+- **[Breaking]** Drop Ruby `2.7` support.
+- **[Feature]** Provide ability to stop and quiet running consumers (Pro).
+- **[Feature]** Provide ability to probe (get backtraces) of any running consumer (Pro).
+- **[Feature]** Provide cluster lags in Health (Pro).
+- **[Feature]** Provide ability to inspect cluster nodes configuration (Pro).
+- **[Feature]** Provide ability to inspect cluster topics configuration (Pro).
+- **[Feature]** Provide messages distribution graph statistics for topics (Pro).
+- [Enhancement] Provide first offset in the OSS jobs tab.
+- [Enhancement] Support failover for custom deserialization of headers and key in the explorer (Pro).
+- [Enhancement] Support failover for custom deserialization of headers and key in the explorer (Pro).
+- [Enhancement] Limit length of `key` presented in the list view of the explorer.
+- [Enhancement] Improve responsiveness on big screens by increasing max width.
+- [Enhancement] Auto-qualify topics with dlq/dead_letter case insensitive name components to DLQ view.
+- [Enhancement] Make tables responsive.
+- [Enhancement] Provide page titles for ease of navigation.
+- [Change] Rename Cluster => Topics to Cluster => Replication to better align with what is shows.
+- [Change] Make support messages more entertaining.
+- [Change] Rename `processing.consumer_group` to `admin.group_id` for consistency with Karafka.
+- [Refactor] Normalize what is process name and process id.
+- [Refactor] Create one `pro/` namespace for all Web related sub-modules.
+- [Refactor] Extract alerts into a common component.
+- [Refactor] Generalize charts generation.
+- [Fix] Fix invalid return when paginating with offsets.
+- [Fix] Improve responsiveness of summary in the consumers view for lower resolutions.
+- [Fix] Align pages titles format.
+- [Fix] Fix missing link from lag counter to Health.
+- [Fix] Fix a case where on mobile charts would not load correctly.
+- [Fix] Fix cases where long consumer names would break UI.
+- [Fix] Explorer deserializer wrongly selected for pattern matched topics.
+- [Fix] Fix 404 error page invalid recommendation of `install` instead of `migrate`.
+- [Fix] Fix dangling `console.log`.
+- [Fix] Fix a case where consumer assignments would not be truncated on the consumers view.
+
+### Upgrade Notes
+
+This is a **major** release that brings many things to the table.
+
+This version of the Karafka Web UI should be upgraded together with Karafka. All upgrade documentation for Karafka and Web UI `0.9` can be found [here](https://karafka.io/docs/Upgrades-2.4/).
+
 ## 0.8.2 (2024-02-16)
 - [Enhancement] Defer scheduler background thread creation until needed allowing for forks.
 - [Enhancement] Tag forks with fork indication + ppid reference when operating in swarm.

data/Gemfile.lock

@@ -1,17 +1,17 @@
 PATH
   remote: .
   specs:
-    karafka-web (0.8.2)
+    karafka-web (0.9.0.rc2)
       erubi (~> 1.4)
-      karafka (>= 2.3.0, < 2.4.0)
-      karafka-core (>= 2.3.0, < 2.4.0)
+      karafka (>= 2.4.0.beta1, < 2.5.0)
+      karafka-core (>= 2.4.0.rc1, < 2.5.0)
       roda (~> 3.68, >= 3.69)
       tilt (~> 2.0)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.1.3)
+    activesupport (7.1.3.2)
       base64
       bigdecimal
       concurrent-ruby (~> 1.0, >= 1.0.2)
@@ -22,41 +22,40 @@ GEM
       mutex_m
       tzinfo (~> 2.0)
     base64 (0.2.0)
-    bigdecimal (3.1.6)
+    bigdecimal (3.1.7)
     byebug (11.1.3)
     concurrent-ruby (1.2.3)
     connection_pool (2.4.1)
     diff-lcs (1.5.1)
     docile (1.4.0)
-    drb (2.2.0)
-      ruby2_keywords
+    drb (2.2.1)
     erubi (1.12.0)
-    factory_bot (6.4.5)
+    factory_bot (6.4.6)
       activesupport (>= 5.0.0)
     ffi (1.16.3)
-    i18n (1.14.1)
+    i18n (1.14.4)
       concurrent-ruby (~> 1.0)
-    karafka (2.3.0)
-      karafka-core (>= 2.3.0, < 2.4.0)
-      waterdrop (>= 2.6.12, < 3.0.0)
+    karafka (2.4.0.beta1)
+      karafka-core (>= 2.4.0.rc1, < 2.5.0)
+      waterdrop (>= 2.7.0.rc1, < 3.0.0)
       zeitwerk (~> 2.3)
-    karafka-core (2.3.0)
-      karafka-rdkafka (>= 0.14.8, < 0.15.0)
-    karafka-rdkafka (0.14.9)
+    karafka-core (2.4.0.rc1)
+      karafka-rdkafka (>= 0.15.0.rc1, < 0.16.0)
+    karafka-rdkafka (0.15.0.rc1)
       ffi (~> 1.15)
       mini_portile2 (~> 2.6)
       rake (> 12)
     mini_portile2 (2.8.5)
-    minitest (5.22.0)
+    minitest (5.22.3)
     mutex_m (0.2.0)
-    rack (3.0.9)
+    rack (3.0.10)
     rack-test (2.1.0)
       rack (>= 1.3)
     rackup (0.2.3)
       rack (>= 3.0.0.beta1)
       webrick
     rake (13.1.0)
-    roda (3.76.0)
+    roda (3.78.0)
       rack
     rspec (3.13.0)
       rspec-core (~> 3.13.0)
@@ -70,8 +69,7 @@ GEM
     rspec-mocks (3.13.0)
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.13.0)
-    rspec-support (3.13.0)
-    ruby2_keywords (0.0.5)
+    rspec-support (3.13.1)
     simplecov (0.22.0)
       docile (~> 1.1)
       simplecov-html (~> 0.11)
@@ -81,8 +79,8 @@ GEM
     tilt (2.3.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
-    waterdrop (2.6.14)
-      karafka-core (>= 2.2.3, < 3.0.0)
+    waterdrop (2.7.0.rc1)
+      karafka-core (>= 2.4.0.rc1, < 3.0.0)
       zeitwerk (~> 2.3)
     webrick (1.8.1)
     zeitwerk (2.6.13)
@@ -101,4 +99,4 @@ DEPENDENCIES
   simplecov
 
 BUNDLED WITH
-   2.5.6
+   2.5.7

data/LICENSE

@@ -4,14 +4,14 @@ Karafka Web is part of Karafka and it is an Open Source project licensed under t
 the LGPLv3 license. Please see <https://github.com/karafka/karafka/blob/master/LGPL>
 for license text.
 
-Karafka has also commercial-friendly license, commercial support and commercial components.
+Karafka and Karafka Web have also commercial-friendly license, commercial support and commercial components.
 
-All of the commercial components are present in the lib/karafka/pro and lib/karafka/web/ui/pro
+All of the commercial components are present in the lib/karafka/pro and lib/karafka/web/pro
 directory of this repository and their usage requires commercial license agreement.
 
 By sending a pull request to the pro components, you are agreeing to transfer the copyright of your
 code to Maciej Mensfeld.
 
-You can find the commercial license in LICENSE-COMM.
+You can find the commercial license in LICENSE-COMM <https://github.com/karafka/karafka/blob/master/LICENSE-COMM>.
 
 Please see https://karafka.io for purchasing options.

data/bin/rspecs

@@ -3,4 +3,4 @@
 set -e
 
 SPECS_TYPE=regular bundle exec rspec --exclude-pattern "**/pro/**/*_spec.rb"
-SPECS_TYPE=pro bundle exec rspec --pattern "**/pro/**/*_spec.rb"
+SPECS_TYPE=pro bundle exec rspec spec/lib/karafka/web/pro

data/config/locales/pro_errors.yml

@@ -0,0 +1,11 @@
+en:
+  validations:
+    config:
+      missing: needs to be present
+
+      commanding.active_format: needs to be either true or false
+      commanding.consumer_group_format: 'needs to be a string with a Kafka accepted format'
+      commanding.max_wait_time_format: needs to be an integer bigger than 0
+      commanding.pause_timeout_format: needs to be an integer bigger than 0
+      key_must_be_a_symbol: All keys under the kafka settings scope need to be symbols
+      commanding.kafka_format: needs to be a filled hash

data/config/locales/slogans.yml

@@ -0,0 +1,62 @@
+en:
+  slogans:
+    - "Unlock the full potential of Karafka with our Pro plan – Your support fuels innovation!"
+    - "Elevate your Karafka experience! Go Pro and access exclusive features today."
+    - "Support Karafka's future developments by upgrading to Pro. Together, we can achieve more!"
+    - "Maximize your productivity with Karafka Pro. Upgrade today for a seamless experience."
+    - "Be a part of something bigger. Your Pro subscription helps me innovate continuously."
+    - "Unlock premium features and dedicated support by upgrading to Karafka Pro."
+    - "Experience the best of Karafka with Pro: More features, more power."
+    - "Karafka Pro awaits with open arms. Upgrade now for a richer development experience."
+    - "Lead, innovate, and excel with Karafka Pro. Upgrade today to unlock your potential."
+    - "Your projects deserve the best. Upgrade to Karafka Pro for unmatched features."
+    - "Speed up your development timeline with Karafka's Pro advanced tools. Upgrade for efficiency!"
+    - "Get more done quickly with Karafka's Pro exclusive features. Upgrade to accelerate."
+    - "Fast-forward your projects with Karafka Pro. Efficiency is just an upgrade away."
+    - "Elevate your coding speed and project quality with Karafka Pro. Time to upgrade!"
+    - "Karafka Pro: Because your time is invaluable. Upgrade for a seamless, speedy workflow."
+    - "Your Pro upgrade powers my innovation - support Karafka's growth and OSS commitment."
+    - "Go Pro and become a pillar of the Karafka ecosystem. Support development, support OSS."
+    - "By choosing Pro, you're fueling our ability to enhance and expand the Karafka ecosystem."
+    - "Support us in shaping the future of Karafka. Your Pro subscription invests in OSS excellence."
+    - "Your support through Pro enables me to innovate and give back to the OSS community."
+    - "Enhance your impact on the OSS world. Upgrade to Karafka Pro and support our ecosystem."
+    - "Every Pro subscriber helps us invest more in Karafka and the broader OSS community."
+    - "Upgrade to Pro: Fuel Karafka's innovation and our dedication to OSS progress."
+    - "Your Pro subscription helps me reinvest in Karafka and contribute more to OSS."
+    - "Leverage Delayed Topics in Karafka Pro for precise message processing timing."
+    - "Automatically manage message lifecycles with the Expiring Messages feature in Karafka Pro."
+    - "Control consumption pace wisely with Rate Limiting, available in Karafka Pro."
+    - "Quickly access data with the Iterator API, a unique Karafka Pro feature."
+    - "Enhance throughput with Multiplexing, enabling parallel processing in Karafka Pro."
+    - "Need to process data faster? Explore Karafka Pro for parallel processing enhancements."
+    - "Struggling with data integrity? Karafka's Pro transaction features ensure reliability."
+    - "Want more control over message timing? Delayed Topics in Karafka Pro make scheduling easy."
+    - "Need to automate regular tasks? Periodic Jobs in Karafka Pro have got you covered."
+    - "Worried about message overload? Karafka's Pro Expiring Messages keep your queues clean."
+    - "Want to filter messages efficiently? Filtering API in Pro makes it simple."
+    - "Concerned about memory during batch operations? Cleaner API in Karafka Pro is the answer."
+    - "Need to increase processing speed? Karafka's Pro Multiplexing feature boosts throughput."
+    - "Looking for better message management? Enhanced Dead Letter Queue in Karafka Pro is key."
+    - "Concerned about Karafka licensing? Karafka Pro offers a commercial-friendly option."
+    - "Need coupled message operations? Transactions in Karafka Pro enhance data integrity."
+    - "Are you Concerned about managing large data flows? Virtual Partitions in Karafka Pro simplify data processing, offering unparalleled efficiency and scalability."
+    - "Looking for flexible scheduling solutions? Karafka's Pro Periodic Jobs feature allows for precise task timing and execution, enhancing your application's performance and reliability."
+    - "Need advanced routing capabilities? Routing Patterns in Karafka Pro provide dynamic message routing, improving your system's adaptability and efficiency."
+    - "Are you Seeking to control your workload? With Rate Limiting in Karafka Pro, you can manage and balance your system's load effectively, ensuring optimal performance under any conditions."
+    - "Need quick data access methods? The Iterator API in Karafka Pro provides efficient data retrieval methods."
+    - "Want more nuanced error handling? Discover Granular Backoffs in Karafka Pro, allowing for detailed control over retry mechanisms and error recovery processes."
+    - "Need a boost in data processing speed? Multiplexing in Karafka Pro enables parallel processing, significantly increasing throughput and reducing processing times."
+    - "Need advanced monitoring and management? Karafka Pro goes beyond basic features, offering comprehensive tools for detailed insight and control over your Kafka ecosystem."
+    - "Let's Build the Future of Karafka Together: Your Pro support brings next-gen features to life."
+    - "Karafka Pro: A Partnership for Progress. Your subscription drives our development."
+    - "With Karafka Pro, you're not just upgrading, you're fueling the future of efficient coding."
+    - "Dare to Support, Dare to Grow: Karafka Pro is your contribution to a boundary-pushing ecosystem."
+    - "Ivest in Karafka Pro to ensure ongoing enhancements and a dynamic, evolving platform."
+    - "Advance with us. Your Karafka Pro subscription is a stepping stone for collective innovation."
+    - "Together, we can push boundaries. Support Karafka's growth by upgrading to Pro."
+    - "Karafka's continuous improvement is powered by our community. Consider going Pro to contribute."
+    - "By choosing Karafka Pro, you're investing in a more robust, feature-rich future for your projects."
+    - "Help me help you. Karafka's future developments depend on your support through Pro."
+    - "Supporting Karafka through Pro enables me to continually enhance its features and support your business better."
+    - "Your upgrade to Karafka Pro directly fuels our capacity to innovate and improve. Let's grow together."

data/docker-compose.yml

@@ -3,7 +3,7 @@ version: '2'
 services:
   kafka:
     container_name: kafka
-    image: confluentinc/cp-kafka:7.6.0
+    image: confluentinc/cp-kafka:7.6.1
 
     ports:
       - 9092:9092

data/karafka-web.gemspec

@@ -17,13 +17,15 @@ Gem::Specification.new do |spec|
   spec.licenses    = %w[LGPL-3.0 Commercial]
 
   spec.add_dependency 'erubi', '~> 1.4'
-  spec.add_dependency 'karafka', '>= 2.3.0', '< 2.4.0'
-  spec.add_dependency 'karafka-core', '>= 2.3.0', '< 2.4.0'
+  spec.add_dependency 'karafka', '>= 2.4.0.beta1', '< 2.5.0'
+  spec.add_dependency 'karafka-core', '>= 2.4.0.rc1', '< 2.5.0'
   spec.add_dependency 'roda', '~> 3.68', '>= 3.69'
   spec.add_dependency 'tilt', '~> 2.0'
 
   spec.add_development_dependency 'rackup', '~> 0.2'
 
+  spec.required_ruby_version = '>= 3.0.0'
+
   if $PROGRAM_NAME.end_with?('gem')
     spec.signing_key = File.expand_path('~/.ssh/gem-private_key.pem')
   end

data/lib/karafka/web/app.rb

@@ -13,7 +13,7 @@ module Karafka
 
         # @return [Class] regular or pro Web engine
         def engine
-          ::Karafka.pro? ? Ui::Pro::App : Ui::App
+          ::Karafka.pro? ? Pro::Ui::App : Ui::App
         end
       end
     end

data/lib/karafka/web/config.rb

@@ -26,6 +26,12 @@ module Karafka
         lazy: true
       )
 
+      # What should be the consumer group name for web UI consumer
+      # Karafka Web UI uses the Admin API for many operations, but there are few
+      # (like states materialization) where a distinct consumer group is needed. In cases like that
+      # this group id will be used
+      setting :group_id, default: 'karafka_web'
+
       # Topics naming - used for processing and UI
       setting :topics do
         # All the errors encountered will be dispatched to this topic for inspection
@@ -41,6 +47,12 @@ module Karafka
 
           # Topic for storing consumers historical metrics info
           setting :metrics, default: 'karafka_consumers_metrics'
+
+          # Topic for storing commands and their results
+          # This is used only in Pro, however we do setup it in OSS in case of upgrade so the
+          # transition from one to another is smooth. Otherwise upgrade would require changes
+          # to topics (migration) which may be more complex
+          setting :commands, default: 'karafka_consumers_commands'
         end
       end
 
@@ -102,9 +114,6 @@ module Karafka
         # apps should materialize the state
         setting :active, default: true
 
-        # What should be the consumer group name for web consumer
-        setting :consumer_group, default: 'karafka_web'
-
         # How often should we report the aggregated state and metrics
         # By default we flush the states twice as often as the data reporting.
         # This will allow us to have closer to real-time reporting.
@@ -138,6 +147,11 @@ module Karafka
           # Should we display internal topics of Kafka. The once starting with `__`
           # By default we do not display them as they are not usable from regular users perspective
           setting :internal_topics, default: false
+
+          # Should we display cluster lags only for active topics
+          # Useful for multi-app setups where the web-ui routing does not match the routing setup
+          # of micro-services and topics are not active but lags reporting should be in use
+          setting :active_topics_cluster_lags_only, default: true
         end
 
         # How many elements should we display on pages that support pagination
@@ -153,6 +167,12 @@ module Karafka
         # are dealing with
         setting :visibility_filter, default: Ui::Models::VisibilityFilter.new
 
+        # Consider any topic matching those names as a DLQ topic for the DLQ view
+        # Web UI uses auto DLQ discovery based on routing but this may not be fully operable when
+        # using a multi-app setup. This config allows to add extra topics if needed without having
+        # to explicitly define routing
+        setting :dlq_patterns, default: [/(dlq)|(dead_letter)/i]
+
         # Specific kafka settings that are tuned to operate within the Web UI interface.
         #
         # Please do not change them unless you know what you are doing as their misconfiguration

data/lib/karafka/web/contracts/config.rb

@@ -12,6 +12,7 @@ module Karafka
 
         required(:enabled) { |val| [true, false, nil].include?(val) }
         required(:ttl) { |val| val.is_a?(Numeric) && val.positive? }
+        required(:group_id) { |val| val.is_a?(String) && TOPIC_REGEXP.match?(val) }
 
         nested(:topics) do
           required(:errors) { |val| val.is_a?(String) && TOPIC_REGEXP.match?(val) }
@@ -44,7 +45,6 @@ module Karafka
 
         nested(:processing) do
           required(:active) { |val| [true, false].include?(val) }
-          required(:consumer_group) { |val| val.is_a?(String) && TOPIC_REGEXP.match?(val) }
           # Do not update data more often not to overload and not to generate too much data
           required(:interval) { |val| val.is_a?(Integer) && val >= 1_000 }
         end
@@ -58,9 +58,15 @@ module Karafka
           required(:cache) { |val| !val.nil? }
           required(:per_page) { |val| val.is_a?(Integer) && val >= 1 && val <= 100 }
 
+          required(:dlq_patterns) do |val|
+            val.is_a?(Array) &&
+              val.all? { |attr| attr.is_a?(String) || attr.is_a?(Regexp) }
+          end
+
           nested(:visibility) do
             required(:filter) { |val| !val.nil? }
             required(:internal_topics) { |val| [true, false].include?(val) }
+            required(:active_topics_cluster_lags_only) { |val| [true, false].include?(val) }
           end
         end
       end

data/lib/karafka/web/management/actions/create_topics.rb

@@ -20,6 +20,7 @@ module Karafka
             consumers_states_topic = ::Karafka::Web.config.topics.consumers.states
             consumers_metrics_topic = ::Karafka::Web.config.topics.consumers.metrics
             consumers_reports_topic = ::Karafka::Web.config.topics.consumers.reports
+            consumers_commands_topic = ::Karafka::Web.config.topics.consumers.commands
             errors_topic = ::Karafka::Web.config.topics.errors
 
             if existing_topics_names.include?(errors_topic)
@@ -88,6 +89,26 @@ module Karafka
               created(consumers_metrics_topic)
             end
 
+            if existing_topics_names.include?(consumers_commands_topic)
+              exists(consumers_commands_topic)
+            else
+              creating(consumers_commands_topic)
+              # Commands are suppose to live short and be used for controlling processes and some
+              # debug. Their data can be removed safely fast.
+              ::Karafka::Admin.create_topic(
+                consumers_commands_topic,
+                1,
+                replication_factor,
+                {
+                  'cleanup.policy': 'delete',
+                  'retention.ms': 7 * 24 * 60 * 60 * 1_000, # 7 days
+                  'segment.ms': 12 * 60 * 60 * 1_000, # 24h
+                  'segment.bytes': 104_857_600 # 100MB
+                }
+              )
+              created(consumers_commands_topic)
+            end
+
             # Create only if needed
             if existing_topics_names.include?(consumers_states_topic)
               exists(consumers_states_topic)

data/lib/karafka/web/management/actions/delete_topics.rb

@@ -12,6 +12,7 @@ module Karafka
               ::Karafka::Web.config.topics.consumers.states,
               ::Karafka::Web.config.topics.consumers.reports,
               ::Karafka::Web.config.topics.consumers.metrics,
+              ::Karafka::Web.config.topics.consumers.commands,
               ::Karafka::Web.config.topics.errors
             ].each do |topic_name|
               if existing_topics_names.include?(topic_name.to_s)

data/lib/karafka/web/management/actions/enable.rb

@@ -37,9 +37,9 @@ module Karafka
           # Enables all the needed routes
           def extend_routing
             ::Karafka::App.routes.draw do
-              web_deserializer = ::Karafka::Web::Deserializer.new
+              payload_deserializer = ::Karafka::Web::Deserializer.new
 
-              consumer_group ::Karafka::Web.config.processing.consumer_group do
+              consumer_group ::Karafka::Web.config.group_id do
                 # Topic we listen on to materialize the states
                 topic ::Karafka::Web.config.topics.consumers.reports do
                   config(active: false)
@@ -52,7 +52,7 @@ module Karafka
                   # This needs to be true in order not to reload the consumer in dev. This consumer
                   # should not be affected by the end user development process
                   consumer_persistence true
-                  deserializer web_deserializer
+                  deserializers(payload: payload_deserializer)
                   manual_offset_management true
                   # Start from the most recent data, do not materialize historical states
                   # This prevents us from dealing with cases, where client id would be changed and
@@ -66,19 +66,25 @@ module Karafka
                 topic ::Karafka::Web.config.topics.consumers.states do
                   config(active: false)
                   active false
-                  deserializer web_deserializer
+                  deserializers(payload: payload_deserializer)
                 end
 
                 topic ::Karafka::Web.config.topics.consumers.metrics do
                   config(active: false)
                   active false
-                  deserializer web_deserializer
+                  deserializers(payload: payload_deserializer)
+                end
+
+                topic ::Karafka::Web.config.topics.consumers.commands do
+                  config(active: false)
+                  active false
+                  deserializers(payload: payload_deserializer)
                 end
 
                 topic ::Karafka::Web.config.topics.errors do
                   config(active: false)
                   active false
-                  deserializer web_deserializer
+                  deserializers(payload: payload_deserializer)
                 end
               end
             end

data/lib/karafka/web/management/migrations/0_base.rb

@@ -47,7 +47,7 @@ module Karafka
             def sorted_descendants
               ObjectSpace
                 .each_object(Class)
-                .select { |klass| klass < self }
+                .select { |klass| klass != self && klass.ancestors.include?(self) }
                 .sort_by(&:index)
             end
           end

data/lib/karafka/web/pro/commanding/commands/base.rb

@@ -0,0 +1,33 @@
+# frozen_string_literal: true
+
+# This Karafka component is a Pro component under a commercial license.
+# This Karafka component is NOT licensed under LGPL.
+#
+# All of the commercial components are present in the lib/karafka/pro directory of this
+# repository and their usage requires commercial license agreement.
+#
+# Karafka has also commercial-friendly license, commercial support and commercial components.
+#
+# By sending a pull request to the pro components, you are agreeing to transfer the copyright of
+# your code to Maciej Mensfeld.
+
+module Karafka
+  module Web
+    module Pro
+      module Commanding
+        # Namespace for commands the process can react to
+        module Commands
+          # Base for all the commands
+          class Base
+            private
+
+            # @return [String] current process id
+            def process_id
+              @process_id ||= ::Karafka::Web.config.tracking.consumers.sampler.process_id
+            end
+          end
+        end
+      end
+    end
+  end
+end

data/lib/karafka/web/pro/commanding/commands/probe.rb

@@ -0,0 +1,41 @@
+# frozen_string_literal: true
+
+# This Karafka component is a Pro component under a commercial license.
+# This Karafka component is NOT licensed under LGPL.
+#
+# All of the commercial components are present in the lib/karafka/pro directory of this
+# repository and their usage requires commercial license agreement.
+#
+# Karafka has also commercial-friendly license, commercial support and commercial components.
+#
+# By sending a pull request to the pro components, you are agreeing to transfer the copyright of
+# your code to Maciej Mensfeld.
+
+module Karafka
+  module Web
+    module Pro
+      module Commanding
+        # Namespace for commands the process can react to
+        module Commands
+          # Collects all backtraces from the available Ruby threads and publishes their details
+          #   back to Kafka for debug.
+          class Probe < Base
+            # Runs probing and publishes result back to Kafka
+            def call
+              threads = {}
+
+              Thread.list.each do |thread|
+                tid = (thread.object_id ^ ::Process.pid).to_s(36)
+                t_d = threads[tid] = {}
+                t_d[:label] = "Thread TID-#{tid} #{thread.name}"
+                t_d[:backtrace] = (thread.backtrace || ['<no backtrace available>']).join("\n")
+              end
+
+              Dispatcher.result(threads, process_id, 'probe')
+            end
+          end
+        end
+      end
+    end
+  end
+end