Class MetricNames
The constants described here represent the various names metrics can take in Jet.
- Since:
- Jet 3.2
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final StringTracks the completion time of a given execution of a specific job.static final StringTracks the start time of a given execution of a specific job.static final StringIndicates whether the job was cancelled by the user.static final StringNumber of job executions finished on the Jet cluster.static final StringNumber of job executions started on the Jet cluster.static final StringNumerical ID of the job's status.static final StringNumber of jobs successfully completed by the Jet cluster.static final StringNumber of jobs that have failed on the Jet cluster.static final StringNumber of jobs submitted to the Jet cluster.static final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final Stringstatic final StringTracks the total number of bytes written in the last snapshot by a particularVertex.static final StringTracks the total number of keys written in the last snapshot by a particularVertex.static final String -
Method Summary
-
Field Details
-
RECEIVED_COUNT
Counts incoming data items on inputEdges of particularVertexinstances running on variousProcessors. These in turn can be identified based on theMetricTags.ORDINAL,MetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
RECEIVED_BATCHES
Counts incoming data item batches on inputEdges of particularVertexinstances running on variousProcessors. These in turn can be identified based on theMetricTags.ORDINAL,MetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
QUEUES_SIZE
Tracks the total size of all input queues of a particularVertexon a particularProcessor. They both can be identified based on theMetricTags.VERTEXandMetricTags.PROCESSORtags of the metric.- See Also:
-
QUEUES_CAPACITY
Tracks the total capacity of all input queues of a particularVertexon a particularProcessor. They both can be identified based on theMetricTags.VERTEXandMetricTags.PROCESSORtags of the metric.- See Also:
-
EMITTED_COUNT
Counts the data items emitted on outgoingEdges of particularVertexinstances running on variousProcessors. These in turn can be identified based on theMetricTags.ORDINAL,MetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.When the
MetricTags.ORDINALtag contains the value "snapshot" then the count contains the number of snapshots saved by theProcessor.- See Also:
-
TOP_OBSERVED_WM
Tracks the highest coalesced watermark observed on all inputEdges of a particularVertex(i.e. the highest watermark observed on all input queues of thatVertex). TheVertexand theProcessorcan be identified based on theMetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
COALESCED_WM
Tracks the highest watermark observed on all the input queues of a particular incomingEdgeof a certainVertex. TheVertexand theProcessorcan be identified based on theMetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
LAST_FORWARDED_WM
Tracks the last watermark emitted by a particularProcessorof a particularVertex. TheVertexand theProcessorcan be identified based on theMetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
LAST_FORWARDED_WM_LATENCY
Tracks the difference between the last emitted watermark and the system time of a particularProcessorof a particularVertex. TheVertexand theProcessorcan be identified based on theMetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
SNAPSHOT_BYTES
Tracks the total number of bytes written in the last snapshot by a particularVertex. The name of the vertex can be found in theMetricTags.VERTEXtag of the metric.- Since:
- Jet 4.0
- See Also:
-
SNAPSHOT_KEYS
Tracks the total number of keys written in the last snapshot by a particularVertex. The name of the vertex can be found in theMetricTags.VERTEXtag of the metric.- Since:
- Jet 4.0
- See Also:
-
EXECUTION_START_TIME
Tracks the start time of a given execution of a specific job. The execution and the job can be identified based on theMetricTags.EXECUTION&MetricTags.JOBtags of the metric. It usesSystem.currentTimeMillis()to get the time on the job start.- Since:
- Jet 4.0
- See Also:
-
EXECUTION_COMPLETION_TIME
Tracks the completion time of a given execution of a specific job. The execution and the job can be identified based on theMetricTags.EXECUTION&MetricTags.JOBtags of the metric. It usesSystem.currentTimeMillis()to get the time on the job completion.- Since:
- Jet 4.0
- See Also:
-
DISTRIBUTED_ITEMS_IN
Counts data items coming in over the network for DISTRIBUTED inputEdges of particularVertexinstances running on variousProcessors. These in turn can be identified based on theMetricTags.ORDINAL,MetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
DISTRIBUTED_BYTES_IN
Tracks the data volume (bytes) coming in over the network for DISTRIBUTED inputEdges of particularVertexinstances running on variousProcessors. These in turn can be identified based on theMetricTags.ORDINAL,MetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
DISTRIBUTED_ITEMS_OUT
Counts data items going out over the network for DISTRIBUTED outputEdges of particularVertexinstances running on variousProcessors. These in turn can be identified based on theMetricTags.ORDINAL,MetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
DISTRIBUTED_BYTES_OUT
Tracks the data volume (bytes) going out over the network for DISTRIBUTED outputEdges of particularVertexinstances running on variousProcessors. These in turn can be identified based on theMetricTags.ORDINAL,MetricTags.VERTEX&MetricTags.PROCESSORtags of the metric.- See Also:
-
JOB_STATUS
Numerical ID of the job's status.- Since:
- 5.4
- See Also:
-
IS_USER_CANCELLED
Indicates whether the job was cancelled by the user.- Since:
- 5.4
- See Also:
-
JOBS_SUBMITTED
Number of jobs submitted to the Jet cluster.This metric is zero on non-master members. When a master fails and a new master takes over, the count is reset.
- Since:
- Jet 4.0
- See Also:
-
JOBS_COMPLETED_SUCCESSFULLY
Number of jobs successfully completed by the Jet cluster.This metric is zero on non-master members. When a master fails and a new master takes over, the count is reset.
- Since:
- Jet 4.0
- See Also:
-
JOBS_COMPLETED_WITH_FAILURE
Number of jobs that have failed on the Jet cluster.This metric is zero on non-master members. When a master fails and a new master takes over, the count is reset.
- Since:
- Jet 4.0
- See Also:
-
JOB_EXECUTIONS_STARTED
Number of job executions started on the Jet cluster. Each job can execute multiple times, for example when it's restarted or suspended and then resumed.This metric is zero on non-master members. When a master fails and a new master takes over, the count is reset.
- Since:
- Jet 4.0
- See Also:
-
JOB_EXECUTIONS_COMPLETED
Number of job executions finished on the Jet cluster. Each job can execute multiple times, for example when it's restarted or suspended and then resumed.This metric is zero on non-master members. When a master fails and a new master takes over, the count is reset.
- Since:
- Jet 4.0
- See Also:
-