Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-1040

Expose more useful metrics and improve Grafana dashboard

    XMLWordPrintable

Details

    Description

      DBZ-776 provided basic metrics for the new framework-based connectors (Oracle and SQL Server currently, Postgres following soon, see DBZ-777).

      We should add more useful metrics:

      • Lag behind master
      • Number of TX
      • Position in source log (currently part of the "event" string, but it should be a separate field; atm. we call toString() on the SourceInfo struct, which kinda works, but exposes some redundant information. Instead, there should be a dedicated method OffsetContext#asLogString() for this purpose)
      • Actual size of internal event queue (if it's constantly near to its max capacity, it indicates some issue)
      • ...

      These should also be exposed in the Grafana dashboard we provide in the examples project. Related to this, the dashboard should also be able to expose all the additional metrics specific to the MySQL connector.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-295 Add a metric to monitor unconsumed binlog

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-441 add better ag indicator for lag in debezium thank second behind master

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users DBZ-715 Extended monitoring

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users DBZ-776 Implement unified metrics across connectors

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users DBZ-978 Provide last event and captured tables in metrics

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jpechane Jiri Pechanec
              gunnar.morling Gunnar Morling
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: