[
https://issues.apache.org/jira/browse/S4-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592384#comment-13592384
]
Matthieu Morel commented on S4-86:
----------------------------------
Thanks for the comments! The extra find() comes from a last minute change
before I uploaded the patch, to refactor some code in S4Metrics... bad idea!
I also enabled the pe processing time with an option to disable it.
Updated patch in branch S4-86, commit d6b89c3074082c5cbe1a7bec7169d5c63ebfcd5c
> Metrics
> -------
>
> Key: S4-86
> URL: https://issues.apache.org/jira/browse/S4-86
> Project: Apache S4
> Issue Type: New Feature
> Affects Versions: 0.6
> Reporter: Matthieu Morel
> Fix For: 0.6
>
>
> Improving performance of S4 applications requires metrics that can be
> analyzed.
> Some metrics suggested in S4-65 are:
> * event rate
> * average/median event processing time
> * event queue sizes
> * number of PE instances
> * number of processed events ( maybe within a sliding window)
> * exceptions during event processing
> We'd also add things like:
> * shedding stats
> * memory usage
> * CPU load
> * checkpointing: effective checkpoints, rejected ones
> * etc...
> Ideally, we'd be able to have different kinds of metrics, including
> historical ones.
> We also want to be able to expose those metrics through JMX, and probably
> through other monitoring systems such as nagios.
> A library that could be useful here is codahale's metrics
> http://metrics.codahale.com/ , but there are alternatives that could be
> evaluated as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
