[dev.icinga.com #10054] clients should send their config to master which executes checks #3350
Comments
|
Updated by ziaunys on 2015-08-31 18:52:20 +00:00 Since the check runs locally, maybe this isn't an issue. I guess the other problem I'm having is if I declare a check on the client, but I want it to run on the parent, how would I do this? |
|
Updated by ziaunys on 2015-08-31 18:56:20 +00:00 Yes. Please ignore the initial concern of my ticket. I don't believe that the parent node needs to be aware of the configuration of a check on a client if it's running from the client. What I'm trying to accomplish is having the config of a service be declared on a client, but I want to have it run on the parent node. For example, the 'ping' check should be executed on the parent node, but it would be nice if it could be declared on the client since I'm using Puppet to declare the service objects. Is this possible? I feel like I might just be missing some documentation. |
|
Updated by mfriedrich on 2015-08-31 19:34:17 +00:00
No that's currently not possible, and is not planned for 'update-config'. Though we're evaluating ideas on auto-discovery with services on a client being pushed to the master. That's not gonna happen for 2.4 I'm afraid. |
|
Updated by mfriedrich on 2015-09-25 10:12:32 +00:00
|
|
Updated by mfriedrich on 2016-02-24 23:26:39 +00:00
|
|
Updated by mfriedrich on 2016-02-24 23:27:45 +00:00
|
|
Updated by mfriedrich on 2016-03-18 17:29:41 +00:00
|
|
Updated by mfriedrich on 2016-11-18 17:11:18 +00:00
|
|
Updated by mfriedrich on 2017-01-14 13:08:06 +00:00
|
|
Updated by mfriedrich on 2017-01-14 13:08:35 +00:00
|
|
Updated by mfriedrich on 2017-01-14 13:08:47 +00:00
|
|
Updated by mfriedrich on 2017-01-14 13:08:53 +00:00
|
|
With the deprecation/future removal of the node command - is this still relevant? |
|
Closing with @gunnarbeutner approval |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10054
Created by ziaunys on 2015-08-31 18:49:55 +00:00
Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2017-01-14 13:08:53 +00:00 (in Redmine)
Maybe I am doing something wrong, but it looks like that the update-config command won't update objects where the parameters may have changed. For example, on the client config, if I update a service objects' "retry_interval" to a different value and reload the client, it will never update on the parent node after running "icinga2 node update-config" unless I completely remove the config file. This is a problem for me especially since I already have to solve the problem of automatically syncing configs from clients. If this doesn't work, I'll have to use a different solution for syncing configs such as exported resources in Puppet which are much slower. I would really love if there was an option to have configs sync automatically. I saw there was another ticket requesting that feature, but it looks like it was closed so I'm not sure if there are any plans to add it.
Parent Task: #13257
The text was updated successfully, but these errors were encountered: