[
https://issues.apache.org/jira/browse/SAMZA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589114#comment-14589114
]
Chris Riccomini commented on SAMZA-449:
---------------------------------------
I think the way we'd been thinking about this was to expose the RocksDB stats
through Samza's metrics API, rather than via trace() logging. This would allow
us to pipe RocksDB metrics into whatever reporting framework you're using,
rather than just logging the metrics to a file. Not sure how RocksDB exposes
the metrics, though. I was assuming they'd expose per-metrics information that
we could get() and just update counters/gauges appropriately.
> Expose Rocksdb stats
> --------------------
>
> Key: SAMZA-449
> URL: https://issues.apache.org/jira/browse/SAMZA-449
> Project: Samza
> Issue Type: Improvement
> Components: kv
> Affects Versions: 0.9.0
> Reporter: Naveen Somasundaram
> Assignee: Gustavo Anatoly
> Priority: Minor
> Labels: newbie++
> Fix For: 0.10.0
>
> Attachments: SAMZA-449.patch
>
>
> RocksDB java now has the option to expose stats, this can be exposed for
> graphs and monitoring purposes. We can implement this in our RocksDB kv store
> implementation to expose these metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
