[
https://issues.apache.org/jira/browse/AURORA-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377021#comment-14377021
]
Maxim Khutornenko commented on AURORA-1220:
-------------------------------------------
Perhaps cluster-level counters can fit there but I'd rather keep job-level
counters within SLA runner as it already uses untracked StatsProvider to
minimize the memory footprint. Since we need to expose other update related
counters, I'd keep everything in SLA for consistency.
> Add SLA stats tracking job updates
> ----------------------------------
>
> Key: AURORA-1220
> URL: https://issues.apache.org/jira/browse/AURORA-1220
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Maxim Khutornenko
>
> With the scheduler updater graduating from beta, we should add job update
> metrics to help job owners track update history/performance, e.g.:
> *Per Job and Per cluster:*
> - updates_created
> - updates_succeeded
> - updates_failed
> - updates_aborted
> - updates_rolled_back
> - time_spent_in_active
> - instances_added
> - instances_removed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
