Good morning,
I have also some questions:
I want to switch to the director module and was able to configure what
is needed. I've chosen as Query type "Nodes" and also tried "Resources"
and looks fine in the preview (also with the facts). But If I try to
synchronize the objects (@@Icinga::Host
On Mon, 2017-05-29 at 18:09 +0200, Thomas Gelf wrote:
> Did you try to define an import source fetching apache::vhost? I'd
> then
> create a sync rule creating single services from that source. When
> doing
> so please follow the host!service convention when defining the "key"
> column. I have no
Hello Thomas,
I hope you are enjoying diner.
Quoting Thomas Gelf , Mon, 29 May 2017:
Did you try to define an import source fetching apache::vhost? I'd then
create a sync rule creating single services from that source. When doing
so please follow the host!service convention when defining the "
Am 29.05.2017 um 17:34 schrieb Rudy Gevaert:
Ofcourse it depends how much node specific information one wants to put
in $monitor::host::vars. Maybe this should be kept to generic things?
::vars could be a nice addition. Would require some hack in your Puppet
manifests (or a custom type/functio
Quoting Thomas Gelf , Mon, 29 May 2017:
Am 29.05.2017 um 17:01 schrieb Rudy Gevaert:
If I understand you correctly you advise to specify which facts to
export. (Not export all of them).
Absolutely. Otherwise volatile facts like free memory and similar would
trigger imports again and again, g
Am 29.05.2017 um 17:01 schrieb Rudy Gevaert:
If I understand you correctly you advise to specify which facts to
export. (Not export all of them).
Absolutely. Otherwise volatile facts like free memory and similar would
trigger imports again and again, generating too much noise. IMHO it
would hav
Hello Thomas,
Quoting Thomas Gelf , Fri, 26 May 2017:
That's the way to go, I'm also doing so. A customer I work with from
time to time is running it that way, exporting 2,5k hosts with quite
some properties and custom vars (mostly from facts) and additionally
exporting 10-20k single services
Am 29.05.2017 um 13:01 schrieb Jayapandian Ponraj:
I do understand that the initial loading can be huge but i have seen
director get unresponsive
even after the inital load, like when defining sync properties.
I would like to have atleast the basic hostalive check across all boxes.
In order to a
Thanks for the response..
My reply inline...
On 26 May 2017 at 17:32, Thomas Gelf wrote:
> Hi,
>
> Director/PuppetDB module author here - so I might be biased ;-)
>
> Am 26.05.2017 um 13:19 schrieb Jayapandian Ponraj:
>
>> * setup 1: I see that the import of all nodes from puppetdb (1K+) in our
Hi,
Director/PuppetDB module author here - so I might be biased ;-)
Am 26.05.2017 um 13:19 schrieb Jayapandian Ponraj:
* setup 1: I see that the import of all nodes from puppetdb (1K+) in our
setup takes a huge amount of time and works only when php is given
insane amount of memory(1G+). Is thi
On Fri, 2017-05-26 at 16:49 +0530, Jayapandian Ponraj wrote:
> Hi
>
> I have a couple of questions with Icinga2 + director + puppetdb
> module combination
>
> * setup 1: I see that the import of all nodes from puppetdb (1K+) in
> our setup takes a huge amount of time and works only when php is
>
Hi
I have a couple of questions with Icinga2 + director + puppetdb module
combination
* setup 1: I see that the import of all nodes from puppetdb (1K+) in our
setup takes a huge amount of time and works only when php is given insane
amount of memory(1G+). Is this normal ? has anyone tried it?
*
12 matches
Mail list logo
