ctubbsii commented on issue #287: Support timely as an optional sink for metrics URL: https://github.com/apache/fluo-muchos/issues/287#issuecomment-536366134 I don't think we should do this, because the intent for the metrics is to have a quick and easy lightweight way to watch a Muchos cluster. Setting up Timely is not lightweight, and this is starting to scope creep well beyond the purpose of Muchos, which is for fast-and-easy cluster testing of Fluo (and Accumulo) during development. Is there a use case for using something like Timely for Fluo / Accumulo development? I can't imagine there would be. Remember, Muchos is *not* a general purpose cluster-deployment tool, and does not require all the features that might be useful in such a tool. It's purpose as an *internal* tool for use by Fluo (and Accumulo) developers, is very narrow, and adding more features like this dramatically increases the risk of bloating Muchos in a way that makes it more difficult for non-Ansible experts, non-EC2 experts, and non-Azure experts to maintain it for developing/testing Fluo (and Accumulo).
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
