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

Change flag behavior to introduce metric priority levels #117

Merged
merged 1 commit into from
Aug 8, 2017

Conversation

joehandzik
Copy link
Contributor

Change flags from binary to string arguments, and introduce the concept of disabled, core, and extended.

Signed-Off-By: Joe Handzik joseph.t.handzik@hpe.com

Fixes issue #116.

@joehandzik joehandzik requested a review from roclark August 4, 2017 16:55
@joehandzik
Copy link
Contributor Author

@roclark Just took a quick hack at what I thought might sit in "core" or "extended" categories. I welcome other thoughts!

Copy link
Contributor

@roclark roclark left a comment

Choose a reason for hiding this comment

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

I will take a deeper dive at this later today depending on what my schedule looks like, but I think this looks pretty good!

While looking at the testing page, something we might want to consider is testing core vs. enabled metrics. As in, run some tests and make sure we get all of the "enabled" metrics, but also make sure that when the "core" flag is set, we only get core metrics. It's not readily obvious to me what the best way would be, but there might be value... maybe.

README.md Outdated

All above flags default to the value "extended" when no argument is submitted by the user.

Example: ./lustre_exporter -collector.ost=disabled -collector.mdt=core -collector.mgs=extended
Copy link
Contributor

Choose a reason for hiding this comment

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

This might just be me, but I think it would be easier to read if the example is put in a code block.

"Example: ./lustre_exporter..."

README.md Outdated
Example: ./lustre_exporter -collector.ost=disabled -collector.mdt=core -collector.mgs=extended

The above example will result in a running instance of the Lustre Exporter with the following statuses:
collector.ost=disabled
Copy link
Contributor

Choose a reason for hiding this comment

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

This might need to be in a code block or a list since these wrap into the previous line in the README. I don't have a strong opinion for which one, so whatever you think would be best. See the README for an example.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, yes. That looks like doodoo.

Change flags from binary to string arguments, and introduce the concept of disabled, core, and extended.

Signed-Off-By: Joe Handzik <joseph.t.handzik@hpe.com>
@joehandzik
Copy link
Contributor Author

@roclark Fixed the two issues you identified. Agreed that we can expand testing to include more permutations of core vs extended, but also agree that the path to adding that is a bit complex.

Copy link
Contributor

@roclark roclark left a comment

Choose a reason for hiding this comment

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

LGTM. I will merge when you are ready!

@joehandzik
Copy link
Contributor Author

Fire away!

@roclark roclark merged commit 062d2b6 into master Aug 8, 2017
@joehandzik joehandzik deleted the wip-augment-flags branch August 8, 2017 15:08
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.

2 participants