[
http://opencast.jira.com/browse/MH-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26603#comment-26603
]
Tobias Wunden commented on MH-6846:
-----------------------------------
I wonder how 2 and 3 could be completed without 1. Sebastian, could you clarify?
> As a configurer/sys admin/administrator, I want to track the details of each
> job associated with a recording
> ------------------------------------------------------------------------------------------------------------
>
> Key: MH-6846
> URL: http://opencast.jira.com/browse/MH-6846
> Project: Matterhorn Project
> Issue Type: Story Card
> Components: Administrative Tools, Architecture & Services
> Affects Versions: 1.2
> Reporter: Josh Holtzman
> Assignee: Tobias Wunden
> Fix For: 1.2, March 2011 Iteration
>
>
> The 1.1 workflow service collects runtime and queuetime statistics from the
> jobs associated with each operation, but we have no way of "drilling down" to
> see which jobs contributed to those runtimes and queue times, which servers
> handled the jobs, how many retries they took, etc. This information will
> help not only in performance reporting, but also in error handling.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________