Class MetricNames
The constants described here represent the various names metrics can take in Jet.
- Since:
- Jet 3.2
-
Field Summary
Modifier and TypeFieldDescriptionstatic final String
static final String
static final String
static final String
static final String
static final String
static final String
Tracks the completion time of a given execution of a specific job.static final String
Tracks the start time of a given execution of a specific job.static final String
Indicates whether the job was cancelled by the user.static final String
Number of job executions finished on the Jet cluster.static final String
Number of job executions started on the Jet cluster.static final String
Numerical ID of the job's status.static final String
Number of jobs successfully completed by the Jet cluster.static final String
Number of jobs that have failed on the Jet cluster.static final String
Number of jobs submitted to the Jet cluster.static final String
static final String
static final String
static final String
static final String
static final String
static final String
Tracks the total number of bytes written in the last snapshot by a particularVertex
.static final String
Tracks 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 inputEdge
s of particularVertex
instances running on variousProcessor
s. These in turn can be identified based on theMetricTags.ORDINAL
,MetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.- See Also:
-
RECEIVED_BATCHES
Counts incoming data item batches on inputEdge
s of particularVertex
instances running on variousProcessor
s. These in turn can be identified based on theMetricTags.ORDINAL
,MetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.- See Also:
-
QUEUES_SIZE
Tracks the total size of all input queues of a particularVertex
on a particularProcessor
. They both can be identified based on theMetricTags.VERTEX
andMetricTags.PROCESSOR
tags of the metric.- See Also:
-
QUEUES_CAPACITY
Tracks the total capacity of all input queues of a particularVertex
on a particularProcessor
. They both can be identified based on theMetricTags.VERTEX
andMetricTags.PROCESSOR
tags of the metric.- See Also:
-
EMITTED_COUNT
Counts the data items emitted on outgoingEdge
s of particularVertex
instances running on variousProcessor
s. These in turn can be identified based on theMetricTags.ORDINAL
,MetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.When the
MetricTags.ORDINAL
tag 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 inputEdge
s of a particularVertex
(ie. the highest watermark observed on all input queues of thatVertex
). TheVertex
and theProcessor
can be identified based on theMetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.- See Also:
-
COALESCED_WM
Tracks the highest watermark observed on all the input queues of a particular incomingEdge
of a certainVertex
. TheVertex
and theProcessor
can be identified based on theMetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.- See Also:
-
LAST_FORWARDED_WM
Tracks the last watermark emitted by a particularProcessor
of a particularVertex
. TheVertex
and theProcessor
can be identified based on theMetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.- See Also:
-
LAST_FORWARDED_WM_LATENCY
Tracks the difference between the last emitted watermark and the system time of a particularProcessor
of a particularVertex
. TheVertex
and theProcessor
can be identified based on theMetricTags.VERTEX
&MetricTags.PROCESSOR
tags 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.VERTEX
tag 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.VERTEX
tag 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.JOB
tags 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.JOB
tags 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 inputEdge
s of particularVertex
instances running on variousProcessor
s. These in turn can be identified based on theMetricTags.ORDINAL
,MetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.- See Also:
-
DISTRIBUTED_BYTES_IN
Tracks the data volume (bytes) coming in over the network for DISTRIBUTED inputEdge
s of particularVertex
instances running on variousProcessor
s. These in turn can be identified based on theMetricTags.ORDINAL
,MetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.- See Also:
-
DISTRIBUTED_ITEMS_OUT
Counts data items going out over the network for DISTRIBUTED outputEdge
s of particularVertex
instances running on variousProcessor
s. These in turn can be identified based on theMetricTags.ORDINAL
,MetricTags.VERTEX
&MetricTags.PROCESSOR
tags of the metric.- See Also:
-
DISTRIBUTED_BYTES_OUT
Tracks the data volume (bytes) going out over the network for DISTRIBUTED outputEdge
s of particularVertex
instances running on variousProcessor
s. These in turn can be identified based on theMetricTags.ORDINAL
,MetricTags.VERTEX
&MetricTags.PROCESSOR
tags 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:
-