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

Introduce "Core" and "Extended" as flag concepts #116

Closed
joehandzik opened this issue Aug 2, 2017 · 1 comment
Closed

Introduce "Core" and "Extended" as flag concepts #116

joehandzik opened this issue Aug 2, 2017 · 1 comment

Comments

@joehandzik
Copy link
Contributor

As we've started to create more complex dashboards from these metrics, we're learning that there are just some metrics that we're collecting today that we'll never, ever put in a dashboard. To that end, I think it makes sense to modify our flag methodology to introduce a third flag state. Each metric that we can collect will be tagged with a level of importance:

Core - Viewed as essential for performance monitoring and issue triage.
Extended - Not essential, unlikely to ever be added to a dashboard.

The default run state will likely be "Extended", which would expose everything. But for our purposes, in real customer environments we're likely to use "Core" to save storage space and minimize clutter.

Comments and thoughts welcomed!

@roclark
Copy link
Contributor

roclark commented Aug 8, 2017

Closing after the merge of #117.

@roclark roclark closed this as completed Aug 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants