[GOBBLIN-112] Metrics hard to enable when run as standalone mode

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: gobblin-metrics
• Labels: Bug:Generic Documentation Framework:Configuration Framework:Metrics
• External issue URL: https://github.com/linkedin/gobblin/issues/916
• Assignee: Issac Buenrostro
• Reporter: Issac Buenrostro
• Created: 19/Jul/17 07:40
• Updated: 19/Jul/17 10:26

Description

When Gobblin is launched as standalone, `SchedulerDaemon` starts all Gobblin services (including Gobblin metrics) using the system and custom configurations, but not the job configurations. Usually, users will specify their metrics config in the job configuration, but this means that for standalone, those configurations will be skipped.
Users must specify metrics configurations using the `--conffile` flag. This needs to be fixed or at least documented.

Github Url : https://github.com/linkedin/gobblin/issues/916
Github Reporter : ibuenros
Github Created At : 2016-04-06T22:05:14Z
Github Updated At : 2017-01-12T04:52:47Z

Comments

---

stakiar wrote on 2016-04-21T19:41:06Z : When launching in stand-alone mode, users can just add the metrics configs to `conf/gobblin-standalone.properties`, there is no need to use `--conffile`.

Given the current way Gobblin Metrics works, I think it makes more sense for metrics to be placed in the `.properties` file rather than the `.job` files, and I think we should change the documentation to reflect that. This issue documents the problems with Gobblin Metrics before the Metrics-as-a-Service feature was added: https://github.com/linkedin/gobblin/issues/792

Github Url : https://github.com/linkedin/gobblin/issues/916#issuecomment-213084108