Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-28063

stream.sh monitor or traker commands don't refresh consumer groups

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.10
    • Fix Version/s: 11.1, 2021.0
    • Component/s: Streams

      Description

      When running stream.sh to monitor the lag and latency (or track them into another stream), the list of consumers for a stream is computed at launch time.

      The command will not report any metrics if it is run before consumer groups have been started (Nuxeo instances are fully initialized).

      The list of consumer groups in a Kafka cluster is dynamic and should be periodically re-evaluated in order to work even when the monitoring is started while the infra is still initializing.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.