Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make prometheus monitoring optional #29

Merged
merged 3 commits into from
Jul 19, 2018
Merged

Make prometheus monitoring optional #29

merged 3 commits into from
Jul 19, 2018

Conversation

andrehp
Copy link
Contributor

@andrehp andrehp commented Jul 19, 2018

No description provided.

@andrehp andrehp requested a review from felipejfc July 19, 2018 03:09
@coveralls
Copy link

coveralls commented Jul 19, 2018

Pull Request Test Coverage Report for Build 293

  • 8 of 9 (88.89%) changed or added relevant lines in 4 files are covered.
  • 21 unchanged lines in 3 files lost coverage.
  • Overall coverage increased (+0.4%) to 75.789%

Changes Missing Coverage Covered Lines Changed/Added Lines %
metrics/prometheus_reporter.go 0 1 0.0%
Files with Coverage Reduction New Missed Lines %
agent/agent.go 2 81.25%
util/util.go 5 65.88%
service/remote.go 14 65.38%
Totals Coverage Status
Change from base Build 286: 0.4%
Covered Lines: 3531
Relevant Lines: 4659

💛 - Coveralls

config/config.go Outdated
@@ -89,6 +89,7 @@ func (c *Config) fillDefaultValues() {
"pitaya.metrics.statsd.rate": 1,
"pitaya.metrics.prometheus.port": 9090,
"pitaya.metrics.tags": map[string]string{},
"pitaya.metrics.prometheus.enabled": true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm thinking of changing this default value to false and logging that monitoring is disabled... this would make development easier IMO

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left it enabled by default to avoid breaking existing applications, but I agree that leaving it disabled by default would avoid some pain when running locally

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we just need to ensure to add the env var to turn it on on the current production applications and then it will be safe to turn it off by default :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disabled it by default now

@andrehp andrehp merged commit 4f8d259 into master Jul 19, 2018
@andrehp andrehp deleted the fix/prometheus branch July 19, 2018 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants