[
https://issues.apache.org/jira/browse/SAMZA-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061096#comment-14061096
]
Chris Riccomini commented on SAMZA-251:
---------------------------------------
bq. So do you mean that we add metrics to both SamzaContainer and TaskInstance?
Yea, I was originally thinking along those lines. Now, I think it might be a
bit overkill. I think the more useful metrics are going to be the
SamzaContainer-level timings, since those metrics will allow us to determine
what part of a container is slow (sending messages, reading messages, or
processing messages).
What do others think?
> Add metrics for choose/process/window/commit/send time
> ------------------------------------------------------
>
> Key: SAMZA-251
> URL: https://issues.apache.org/jira/browse/SAMZA-251
> Project: Samza
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Assignee: Yan Fang
> Labels: newbie
> Fix For: 0.8.0
>
>
> We should add the following counter metrics:
> * choose-ms
> * window-ms
> * process-ms
> * commit-ms
> * send-ms
> This will allow us to see how much time is being spent (per second) in each
> block of code.
> I think all of these metrics should be added at the SamzaContainer level, and
> all except choose-ms should be done at the TaskInstance level.
--
This message was sent by Atlassian JIRA
(v6.2#6252)