Versions Compared

Old Version 6

changes.mady.by.user Unknown User (kirktrue)

Saved on

compared with

New Version 7

changes.mady.by.user Unknown User (kirktrue)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added metrics

...

As explained in the concepts section, the ClientConfigPolicy implementation may also provide logic to ensure that clients do not send sensitive configuration. Clients across the Apache Kafka ecosystem do not have a consistent naming convention. As a result, brokers cannot determine sensitivity based on the configuration key name and rely on the incoming ConfigType field. When the ClientConfigPolicy detects sensitive configuration, it includes a description of the violation in the RPC response.

Metrics

...

The following new broker metrics are added:

Name

Type

Group

Tags

Notes

instance-count

Gauge

client-config


The current number of unique client instance IDs.

NOTE: this is from KIP-714 but will likely be refactored KIP-1313.

plugin-config-count

plugin-config-rate

Meter

client-config

client_instance_id

The total number/rate of PushConfig requests being pushed to the ClientConfigPolicy plugin, regardless of success/failure.

plugin-error-count

plugin-error-rate

Meter

client-config

client_instance_id

The total number/rate of errors raised during preparation for and/or invoking the plugin’s process() method.

plugin-process-time-avg

plugin-process-time-max

Avg and Maxclient-configclient_instance_idThe length of time (in milliseconds) the broker spent invoking the plugin’s process() method.

Client Behavior

Handshake

A client that supports this configuration interface will identify a node that supports the API using ApiVersions. The client performs a handshake by collecting the values for its configuration issuing a PushConfig RPC to submit the configuration to the broker node. The client sends the RPC after authentication (if any) and before the client starts to use the connection for requests. Similar to the ApiVersions handshake, the PushConfig RPC specifies a fixed timeout of default.timeout.ms. If the RPC exhausts its retries, the client logs the error, but continues execution.

...