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.

Sign up for GitHub

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

Jump to bottom

Feature request: return perfvars, even if expected value doesn't match actual #29

Open
senorsmile opened this issue May 11, 2017 · 0 comments
Open

Feature request: return perfvars, even if expected value doesn't match actual #29

senorsmile opened this issue May 11, 2017 · 0 comments

Comments

@senorsmile
Copy link

When the actual value does not match the expected value, no perfvars are in the output:

Check JSON status API CRITICAL - Expected value (224) not found. Actual: 218

However, if they match, they are in the output. It seems we prematurely exit, without calculating if the expected value does not match the actual.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@senorsmile