[
https://issues.apache.org/jira/browse/FALCON-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216789#comment-14216789
]
Balu Vellanki commented on FALCON-676:
--------------------------------------
After applying patch and running end2end, the generated metrics in
falcon.application.log looks like this.
{code}
2014-11-18 20:53:48,192 INFO - [metrics-logger-reporter-thread-1:] ~
type=TIMER, name=com.thinkaurelius.titan.stores.getSlice.time, count=9,
min=0.347985, max=1.3848669999999998, mean=0.8925124444444444,
stddev=0.4509201914402678, median=0.828805, p75=1.334384,
p95=1.3848669999999998, p98=1.3848669999999998, p999=1.3848669999999998,
mean_rate=1.3848669999999998, m1=0.030051778950274975, m5=0.01692641259269143,
m15=0.7078332975634773, rate_unit=1.3187384419305865,
duration_unit=events/second (metrics:108)
{code}
[~ajayyadava] I recommend formatting this log a bit and recommend writing the
logs into a separate file. It should not be going into falcon.application.log
> Enable metrics for Titan
> ------------------------
>
> Key: FALCON-676
> URL: https://issues.apache.org/jira/browse/FALCON-676
> Project: Falcon
> Issue Type: Sub-task
> Components: metrics
> Affects Versions: 0.6
> Reporter: Venkatesh Seetharam
> Assignee: Ajay Yadav
> Attachments: FALCON-676.patch
>
>
> http://s3.thinkaurelius.com/docs/titan/0.5.0/monitoring.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
