Class CloudTasksMetricNames
Each connector has one of these, and comparing them is how the repository's metric naming
convention is held across connectors — a name that means the same thing in two connectors should
be spelled the same way, and a diff of these files is what shows it. The convention itself (a
counter names the event, a gauge names the state, and neither takes Flink's num prefix)
is recorded in the base module's detailed agent guidance.
What is not here: Flink's standard sink names, which come from
SinkWriterMetricGroup accessors rather than from a name, and the subgroup leaves
base.metrics registers on this connector's behalf (errorClass.CODE.errors,
destination.QUEUE.recordsSend). The user-facing meaning of each name is on the connector's
documentation page, not duplicated here.
-
Field Details
-
IN_FLIGHT_TASKS
- See Also:
-
PARKED_TASKS
- See Also:
-
TASKS_DEDUPLICATED
- See Also:
-
RECORDS_SKIPPED
- See Also:
-