mynameborat commented on a change in pull request #1455:
URL: https://github.com/apache/samza/pull/1455#discussion_r553553944
##########
File path: docs/learn/documentation/versioned/container/metrics-table.html
##########
@@ -977,6 +983,57 @@ <h1>Samza Metrics Reference</h1>
<td>single-barrier-rebalancing-time</td>
<td><a href="#average-time">Average time</a> taken for all the
processors to get the latest version of the job model after single processor
change (without the occurence of a barrier timeout)</td>
</tr>
+ <tr>
+ <th colspan="2" class="section"
id="job-coordinator-metadata-manager-metrics">org.apache.samza.coordinator.JobCoordinatorMetadataManager.JobCoordinatorMetadataManagerMetrics<br><span
style="font-weight: normal;margin-left:40px;"><b>Note</b>: The following
metrics are applicable when Application Master High Availability is
enabled</span></th>
+ </tr>
+ <tr>
+ <td>application-attempt-count</td>
+ <td>Denotes the application attempt count within the scope of a single
deployment</td>
+ </tr>
+ <tr>
+ <td>config-changed</td>
+ <td>Denotes configuration changed across attempts within the scope of
a single deployment</td>
+ </tr>
+ <tr>
+ <td>job-model-changed</td>
+ <td>Denotes job model changed across attempts within the scope of a
single deployment</td>
+ </tr>
+ <tr>
+ <td>metadata-read-failed-count</td>
+ <td>Read failure count from the underlying metadata store</td>
+ </tr>
+ <tr>
+ <td>metadata-write-failed-count</td>
+ <td>Write failure count to the underlying metadata store</td>
+ </tr>
+ <tr>
+ <td>metadata-generation-failed-count</td>
+ <td>Number of times the metadata generation failed</td>
+ </tr>
+ <tr>
+ <td>new-deployment</td>
+ <td>Denotes a new deployment due to changes in metadata either
attributed to config or job model</td>
+ </tr>
+ </tbody>
+ <tr>
+ <th colspan="2" class="section"
id="container-heartbeat-monitor-metrics">org.apache.samza.container.ContainerHeartbeatMonitor.ContainerHeartbeatMetrics<br><span
style="font-weight: normal;margin-left:40px;"><b>Note</b>: The following
metrics are applicable when Application Master High Availability is
enabled</span></th>
+ </tr>
+ <tr>
+ <td>heartbeat-discovery-time-ms</td>
+ <td>Time taken in millis for the container to discover new AM in the
event AM changes for heartbeat establishment</td>
+ </tr>
+ <tr>
+ <td>heartbeat-established-failure-count</td>
+ <td>Number of times failed to establish heartbeat in the event of AM
changes</td>
+ </tr>
+ <tr>
+ <td>heartbeat-established-with-new-am-count</td>
+ <td>Number of times heartbeat is established with the new AM in the
event of AM changes</td>
+ </tr>
+ <tr>
+ <td>heartbeat-expired-count</td>
+ <td>Number of times heartbeat expired with the active AM</td>
Review comment:
these are container heartbeat metrics and hence container level metrics.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
