Camel Metrics - maintaining historical metrics

[contactreji <co...@gmail.com>]

Just one open question I had in mind while using camel-metrics from ETL jobs
perspective.

I am thinking of job level metric tracking. And jobs might happen sooner
like every 2 mins or maybe in a day. And each job is identified by some
unique id. 
Ex – A job categorized as VMM catagory running at 7 am on 10th Nov 2015 ,
probably we some generate ID as vvmjob070010112015 And metrics may be named
as

vvmjob070010112015.executionduration
vvmjob070010112015.outcome
vvmjob070010112015.volume
vvmjob070010112015.startendtimestamp


When we have graphite reporters at camel app side, the metrics get collected
up for each individual instance of job and I assume there will be increase
in count of metrics over a long course of time when metrics for each job add
up. Should we delete the historical metrics for old jobs which are already
executed and reported? Else will it add up to a level and eat on memory?

If its to be deleted, how do we achieve using the camel-metrics component?



-----
Reji Mathews
Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel & Jboss Fuse ESB | Mule ESB )
LinkedIn - http://in.linkedin.com/pub/reji-mathews/31/9a2/40a
Twitter - reji_mathews
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Metrics-maintaining-historical-metrics-tp5773553.html
Sent from the Camel - Users mailing list archive at Nabble.com.