In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

We are using DBZ 3.0.0, and it seems that NumberOfEventsFiltered always shows 0.

The issue appears to be caused by PgOutputMessageDecoder#resolveRelation returning empty, resulting in messages being treated as NoopMessage. This occurs because table relations for excluded tables are not added in PostgresSchema#applySchemaChangesForTable. Consequently, this line skips Noop messages and fails to increment the NumberOfEventsFiltered counter, as the increment only happens during the execution of dispatcher.dispatchDataChangeEvent

What Debezium connector do you use and what version?

Postgres connector (DBZ 3.0.0)

What is the connector configuration?

N/A

What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

Postgres 13.9 (container environment)

What behavior do you expect?

NumberOfEventsFiltered counter expected to be incremented for every excluded table message is processed in streaming

What behavior do you see?

NumberOfEventsFiltered is always 0.

Do you see the same behaviour using the latest released Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

Yes. Tested against main branch on local setup.

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

N/A

How to reproduce the issue using our tutorial deployment?

1. Create connector with `table.exclude.list` and let it run in streaming mode.
2. Run DML of excluded tables.
3. Collect streaming metrics

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>