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

The check-marathon-task plugin does not use the Marathon API correctly #9

Closed
andrelaszlo opened this issue Jul 20, 2016 · 2 comments
Closed

Comments

@andrelaszlo
Copy link
Contributor

The check-marathon-task plugin is using the wrong name for the status parameter. The current code is using state=running, which returns all tasks - even those that are not running. The correct way to call this API is to use status=running, which only returns tasks that are in their running state.

This means that a task that is not running (it might be staged) will count as a running task. The expected behavior is that only running tasks are counted.

Additionally, the plugin description says:

This plugin checks that the given Mesos/Marathon task is running properly

In my opinion, the plugin should also check the healthCheckResults for each task and report running but unhealthy tasks as failures. Currently, the health check results are ignored, only the state is considered.

@majormoses
Copy link
Member

@andrelaszlo this should be released and fixed: https://rubygems.org/gems/sensu-plugins-mesos/versions/1.0.0 assuming all is well we can close this out?

@andrelaszlo
Copy link
Contributor Author

@majormoses Sounds good, closing!

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

No branches or pull requests

2 participants