Skip to content

Diagnostics FAQ #1514

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

Merged
merged 2 commits into from
Jun 6, 2017
Merged

Diagnostics FAQ #1514

merged 2 commits into from
Jun 6, 2017

Conversation

jseldess
Copy link
Contributor

@jseldess jseldess commented Jun 6, 2017

In response to cockroachdb/cockroach#16298:

  • Add FAQ about diagnostics reporting
  • Tweak existing language about diagnostics reporting

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@cockroach-teamcity
Copy link
Member

@jseldess jseldess merged commit db8d9b0 into gh-pages Jun 6, 2017
@jseldess jseldess deleted the diagnostics branch June 6, 2017 17:05
@@ -39,6 +39,10 @@ The timeseries data used to power the graphs in the admin UI is stored within th

As of the 1.0 release, there is no way to change the number of days before timeseries data gets truncated. As a workaround, however, you can start each node with the `COCKROACH_METRICS_SAMPLE_INTERVAL` environment variable set higher than its default of `10s` to store fewer data points. For example, you could set it to `1m` to only collect data every 1 minute, which would result in storing 6x less timeseries data than the default setting.

## Why does CockroachDB default to "opt-out" when collecting anonymized cluster usage details?
Copy link
Contributor

Choose a reason for hiding this comment

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

"default to opt-out" is a weird way to phrase it. Our policy is "opt-out", which means that the default is "in".

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 agree, Ben. Opened this PR as a fix: #1525

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.

5 participants