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

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

2.0.0

What is the connector configuration?

N/A

What is the captured database version and mode of depoyment?

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

N/A

What behaviour do you expect?

We wanted add additional logs after each Connector's poll method. 

What behaviour do you see?

Visibility of BaseSourceTask#logStatistics is default and doesn't allow adding additional logging/functionality post polling of source records in a custom connector.  

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

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

Yes

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?

N/A

Feature request or enhancement

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

Currently, PostgresConnectorTask logging record count and recorded offset after each poll by using calling  BaseSourceTask#logStatistics method inside BaseSourceTask#poll method. This is great.

Provide ability to inject custom logging/functionality post BaseSourceTask#poll

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

Add customer specific observability functionality.

Implementation ideas (optional)

Change visibility of BaseSourceTask#logStatistics method to protected so that a custom connector can inject additional logs/functionality.