Build failed in Jenkins: Fluo Parent Pom #23

2016-08-08 Thread Apache Jenkins Server
See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on ubuntu3 (Ubuntu ubuntu legacy-ubuntu) in workspace

[GitHub] incubator-fluo issue #755: Fixed bug in suggested InfluxDB config

2016-08-08 Thread keith-turner
Github user keith-turner commented on the issue: https://github.com/apache/incubator-fluo/pull/755 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or

[GitHub] incubator-fluo pull request #755: Fixed bug in suggested InfluxDB config

2016-08-08 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/incubator-fluo/pull/755 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] incubator-fluo issue #755: Fixed bug in suggested InfluxDB config

2016-08-08 Thread mikewalch
Github user mikewalch commented on the issue: https://github.com/apache/incubator-fluo/pull/755 yes.. they were being stored incorrectly so dashboards did not work. Bug started when metrics prefix was renamed from `io.fluo` to `fluo` --- If your project is set up for it, you can

[GitHub] incubator-fluo issue #755: Fixed bug in suggested InfluxDB config

2016-08-08 Thread keith-turner
Github user keith-turner commented on the issue: https://github.com/apache/incubator-fluo/pull/755 did this cause metrics to not display or to display incorrect info? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] incubator-fluo pull request #755: Fixed bug in suggested InfluxDB config

2016-08-08 Thread mikewalch
GitHub user mikewalch opened a pull request: https://github.com/apache/incubator-fluo/pull/755 Fixed bug in suggested InfluxDB config * Bug was causing metrics to be stored incorrectly You can merge this pull request into a Git repository by running: $ git pull