Debezium streaming
label:
Podstawowe metryki
Dostępne dla wszystkich obsługiwanych baz (postgres, oracle, sqlserver)
Nazwa | Typ | Opis | Używane | Dashboard |
---|---|---|---|---|
|
| The last streaming event that the connector has read. | ||
|
| The number of milliseconds since the connector has read and processed the most recent event. | ||
|
| The total number of events that this connector has seen since the last start or metrics reset. | ||
|
| The total number of create events that this connector has seen since the last start or metrics reset. | ||
|
| The total number of update events that this connector has seen since the last start or metrics reset. | ||
|
| The total number of delete events that this connector has seen since the last start or metrics reset. | ||
|
| The number of events that have been filtered by include/exclude list filtering rules configured on the connector. | ||
|
| The list of tables that are captured by the connector. | ||
|
| The length the queue used to pass events between the streamer and the main Kafka Connect loop. | ||
|
| The free capacity of the queue used to pass events between the streamer and the main Kafka Connect loop. | ||
|
| Flag that denotes whether the connector is currently connected to the database server. | ||
|
| The number of milliseconds between the last change event’s timestamp and the connector processing it. The values will incoporate any differences between the clocks on the machines where the database server and the connector are running. | ||
|
| The number of processed transactions that were committed. | ||
|
| The coordinates of the last received event. | ||
|
| Transaction identifier of the last processed transaction. | ||
|
| The maximum buffer of the queue in bytes. This metric is available if | ||
|
| The current volume, in bytes, of records in the queue. |
Oracle
Dodatkowe metryki dostępne dla oracle
Nazwa | Typ | Opis | Używane |
---|---|---|---|
|
| The most recent system change number that has been processed. | |
|
| The oldest system change number in the transaction buffer. | |
|
| The oldest system change number’s age in milliseconds. If the buffer is empty, the value will be | |
|
| The last committed system change number from the transaction buffer. | |
|
| The system change number currently written to the connector’s offsets. | |
|
| Array of the log files that are currently mined. | |
|
| The minimum number of logs specified for any LogMiner session. | |
|
| The maximum number of logs specified for any LogMiner session. | |
|
| Array of the current state for each mined logfile with the format | |
|
| The number of times the database has performed a log switch for the last day. | |
|
| The number of DML operations observed in the last LogMiner session query. | |
|
| The maximum number of DML operations observed while processing a single LogMiner session query. | |
|
| The total number of DML operations observed. | |
|
| The total number of LogMiner session query (aka batches) performed. | |
|
| The duration of the last LogMiner session query’s fetch in milliseconds. | |
|
| The maximum duration of any LogMiner session query’s fetch in milliseconds. | |
|
| The duration for processing the last LogMiner query batch results in milliseconds. | |
|
| The time in milliseconds spent parsing DML event SQL statements. | |
|
| The duration in milliseconds to start the last LogMiner session. | |
|
| The longest duration in milliseconds to start a LogMiner session. | |
|
| The total duration in milliseconds spent by the connector starting LogMiner sessions. | |
|
| The minimum duration in milliseconds spent processing results from a single LogMiner session. | |
|
| The maximum duration in milliseconds spent processing results from a single LogMiner session. | |
|
| The total duration in milliseconds spent processing results from LogMiner sessions. | |
|
| The total duration in milliseconds spent by the JDBC driver fetching the next row to be processed from the log mining view. | |
|
| The total number of rows processed from the log mining view across all sessions. | |
|
| The number of entries fetched by the log mining query per database round-trip. | |
|
| The number of milliseconds the connector sleeps before fetching another batch of results from the log mining view. | |
|
| The maximum number of rows/second processed from the log mining view. | |
|
| The average number of rows/second processed from the log mining. | |
|
| The average number of rows/second processed from the log mining view for the last batch. | |
|
| The number of connection problems detected. | |
|
| The number of hours that transactions are retained by the connector’s in-memory buffer without being committed or rolled back before being discarded. For more information, see | |
|
| The number of current active transactions in the transaction buffer. | |
|
| The number of committed transactions in the transaction buffer. | |
|
| The number of transactions that were discarded because their size exceeded | |
|
| The number of rolled back transactions in the transaction buffer. | |
|
| The average number of committed transactions per second in the transaction buffer. | |
|
| The number of registered DML operations in the transaction buffer. | |
|
| The time difference in milliseconds between when a change occurred in the transaction logs and when its added to the transaction buffer. | |
|
| The maximum time difference in milliseconds between when a change occurred in the transaction logs and when its added to the transaction buffer. | |
|
| The minimum time difference in milliseconds between when a change occurred in the transaction logs and when its added to the transaction buffer. | |
|
| An array of the most recent abandoned transaction identifiers removed from the transaction buffer due to their age. See | |
|
| An array of the most recent transaction identifiers that have been mined and rolled back in the transaction buffer. | |
|
| The duration of the last transaction buffer commit operation in milliseconds. | |
|
| The duration of the longest transaction buffer commit operation in milliseconds. | |
|
| The number of errors detected. | |
|
| The number of warnings detected. | |
|
| The number of times that the system change number was checked for advancement and remains unchanged. A high value can indicate that a long-running transactions is ongoing and is preventing the connector from flushing the most recently processed system change number to the connector’s offsets. When conditions are optimal, the value should be close to or equal to | |
|
| The number of DDL records that have been detected but could not be parsed by the DDL parser. This should always be | |
|
| The current mining session’s user global area (UGA) memory consumption in bytes. | |
|
| The maximum mining session’s user global area (UGA) memory consumption in bytes across all mining sessions. | |
|
| The current mining session’s process global area (PGA) memory consumption in bytes. | |
|
| The maximum mining session’s process global area (PGA) memory consumption in bytes across all mining sessions. |
Last updated