franpola
March 13, 2019, 3:55pm
1
Hi,tutorial until the paragraph
Now that you’ve successfully installed a Windows client, please proceed to the detailed configuration modes .
Which I cannot understand. Does it mean that after installing the agent you still need to configure something else? I have not seen any changes on my dashboard after insatlling the agent, could someone tell me an easy way to complete the configuration on a windows host so that icinga starts monitoring?
Thanks!
dnsmichi
March 13, 2019, 6:13pm
2
Yep, you need to configure hosts and services for this agent, and a transport method for checks, e.g. via command endpoint mode.
franpola
March 14, 2019, 1:42pm
3
So, let’s say I want to check just the basics from the host where the agent is installed. Where do I configure that on the conf files that the agent has installed ?
This is getting complicated…
dnsmichi
March 14, 2019, 3:03pm
4
Hi,
Icinga needs to know about all monitored objects, that is why you need to configure them.
Here’s a concrete example for command endpoints in general: https://icinga.com/docs/icinga2/latest/doc/06-distributed-monitoring/#top-down-command-endpoint
In Windows specific regions, this is more focussed on e.g. using the provided plugins: https://icinga.com/docs/icinga2/latest/doc/06-distributed-monitoring/#windows-client-and-plugins
Cheers,
@franpola
You don’t need to configure as much as for Icinga.
dnsmichi
March 14, 2019, 3:24pm
6
Reaching the first success is why I’ve suggested the manual configuration. If you don’t want to configure that much, I’d suggest to use the Icinga Director and hide specific parts e.g. on agent zones and such.
https://icinga.com/docs/director/latest/
A demo is available online.
Cheers,
1 Like
franpola
March 14, 2019, 6:02pm
7
expected behavior
I am following this guideMonitoring Lab
@starflighter is not my decision, our client already has icinga and i am just trying to learn how to remove and add some hosts to their existing setup. I have already invested 2 months trying to learn Icinga. I will probably start reading the documentation in German, maybe that way i will get what this is all about…
icinga2 --version
Copyright © 2012-2015 Icinga Development Team (https://www.icinga.org )http://gnu.org/licenses/gpl2.html
Application information:
System information:
Features
Disabled features: gelf icingastatus opentsdb statusdata syslog
icinga2 daemon -C
critical/config: 1 error
/**
Icinga 2 configuration file
this is where you define settings for the Icinga application including
which hosts/services to check.
For an overview of all available configuration options please refer
to the documentation that is distributed as part of Icinga 2.
/**
The constants.conf defines global constants.
/**
The zones.conf defines zones for a cluster setup.
Not required for single instance setups.
/**
The Icinga Template Library (ITL) provides a number of useful templates
and command definitions.
Common monitoring plugin command definitions are included separately.
/**
The features-available directory contains a number of configuration
files for features which can be enabled and disabled using the
icinga2 feature enable / icinga2 feature disable CLI commands.
These commands work by creating and removing symbolic links in
the features-enabled directory./ .conf"
/**
The repository.d directory contains all configuration objects
managed by the ‘icinga2 repository’ CLI commands.
/**
Although in theory you could define all your objects in this file
the preferred way is to create separate directories and files in the conf.d
directory. Each of these files must have the file extension “.conf”.
dnsmichi
March 15, 2019, 3:21pm
8
Uhm, 2.4.1 for Icinga 2 is really old, and so is 2.1.0 for Icinga Web 2. I assume you did configure the wrong package repository and using old upstream packages from Ubuntu Xenial.
You can add it like this :
apt-get -y install apt-transport-https
wget -O - https://packages.icinga.com/icinga.key | apt-key add -
echo 'deb https://packages.icinga.com/ubuntu icinga-xenial main' >/etc/apt/sources.list.d/icinga.list
apt-get update
Then create a backup of your current configuration, purge the old icinga2 package and install it new from the official repository.
Cheers,
franpola
March 16, 2019, 1:26pm
9
Well, this is our client’s machine, not ours, it’s an old installation that’s why the versions are old. The want to update the running config, the checks and everything else hosts, services… since their network setup has changed a lot in the last months.
I am thinking it would be even better to make a fresh new Linux and icinga2 install and configuration than trying to update entirely the existing one.
What is your thinking ?
dnsmichi
March 18, 2019, 7:42am
10
It is probably the easier way, since there were also changes with certificate handling in 2.8 resulting in a minimum of that version as well. The configuration should be compatible being again put in place. You might want to test-drive that in a local VM beforehand.
Cheers,
