-
Notifications
You must be signed in to change notification settings - Fork 289
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
new subscribe check does not restart sensu-api service #600
Comments
@jeffmccune this is similar to the other issues regarding notification of services. |
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jul 11, 2017
Without this patch changes to sensu::check and sensu::check_config resources do not automatically reload the Sensu API service. This causes the checks to not show up in the dashboard UI which is a problem for the end user. This patch adds notification relationships between sensu_check and sensu_check_config resources and Service[sensu-api]. Resolves sensu#600
jeffmccune
added a commit
to jeffmccune/sensu-puppet
that referenced
this issue
Jul 11, 2017
Without this patch changes to sensu::check and sensu::check_config resources do not automatically reload the Sensu API service. This causes the checks to not show up in the dashboard UI which is a problem for the end user. This patch adds notification relationships between sensu_check and sensu_check_config resources and Service[sensu-api]. Resolves sensu#600
ghoneycutt
added a commit
that referenced
this issue
Jul 11, 2017
(#600) Reload Sensu API when check configurations change
Thanks for reporting @giedriusramas @jeffmccune fix is in release v2.20.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem
What did you do?
Adding new check:
sensu::check { 'metrics-disk-capacity.rb':
type => 'metric',
handlers => 'relay',
command => 'metrics-disk-capacity.rb',
interval => 10,
subscribers => 'default',
standalone => false,
}
What happened?
Notice: /Stage[main]/My_sensu::Default/Sensu::Check[metrics-disk-capacity.rb]/File[/etc/sensu/conf.d/checks/metrics-disk-capacity.rb.json]/ensure: created
Notice: /Stage[main]/My_sensu::Default/Sensu::Check[metrics-disk-capacity.rb]/Sensu_check[metrics-disk-capacity.rb]/ensure: created
Info: /Stage[main]/My_sensu::Default/Sensu::Check[metrics-disk-capacity.rb]/Sensu_check[metrics-disk-capacity.rb]: Scheduling refresh of Service[sensu-client]
Info: /Stage[main]/My_sensu::Default/Sensu::Check[metrics-disk-capacity.rb]/Sensu_check[metrics-disk-capacity.rb]: Scheduling refresh of Service[sensu-server]
Notice: /Stage[main]/Sensu::Client::Service/Service[sensu-client]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Sensu::Server::Service/Service[sensu-server]: Triggered 'refresh' from 1 events
What did you expect to happen?
I expect to see new check in Uchiwa dashboard. Checks appears in Uchiwa dashborafter restarting sensu-api service.
How can someone reproduce the problem?
Command used and debugging output
Platform and version information
Anything else to add that you think will be helpful?
I think sensu-api should somehow subscribe to sensu::check
https://github.com/sensu/sensu-puppet/blob/master/manifests/api/service.pp#L34-L40
The text was updated successfully, but these errors were encountered: