Re: [icinga-users] Changing of ifDescr of SNMP of Debian Jessie and "-n" parameter of check_snmp_int.pl Manubulon plugin

On Mon, 23 Mar 2015, Daniel Bareiro wrote: # ./check_snmp_int.pl -H 10.1.0.10 -l Us3r -x passw0rd0 \ -X passwOrd1 -L md5,des -n -v Alarm at 10 + 5 SNMPv3 AuthPriv login : Us3r, md5, des Filter : OID : 1.3.6.1.2.1.2.2.1.2.2, Desc : Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast

Re: [icinga-users] Changing of ifDescr of SNMP of Debian Jessie and "-n" parameter of check_snmp_int.pl Manubulon plugin

> So I checked the equivalence between ifDescr and ifName: So what happens if you swap the ifname oid in $descr_table? jlc ___ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users

Re: [icinga-users] Notification sending using wrong user

Hmmm. Your host notification templates use the wrong state filters (Down instead of Warning, Critical). Enable debug log and check that filters don't match currently. Kind regards, Michael Von meinem iPhone gesendet Am 23.03.2015 um 20:13 schrieb Henti Smith mailto:he...@geekware.co.za>>: Hi

[icinga-users] Changing of ifDescr of SNMP of Debian Jessie and "-n" parameter of check_snmp_int.pl Manubulon plugin

Hi all! I wonder if in this mailing list is there anyone involved in the development of check_snmp_int.pl plugin or the newer version, check_snmp_netint.pl, or someone that using these plugins, have seen what I mention as an inconvenience that may have been solved by modifying the code. A few day

Re: [icinga-users] Notification sending using wrong user

Hi Michael, The host config is from the client as per the documentation. There is no host object appart from the dummy ones created in the repository. I'll mail them tomorrow as well. H On Mon, Mar 23, 2015 at 5:46 PM, Michael Friedrich < michael.friedr...@netways.de> wrote: > Am 23.03.2015 u

Re: [icinga-users] Notification sending using wrong user

Am 23.03.2015 um 14:15 schrieb Henti Smith: Hi there, All configs below: The Host object is enough, and that's not listed below. /* users.conf */ object User "infra" { import "generic-user" display_name = "Infra" groups = [ "infra" ] email= "infra@hostname" } object User "support" { i

Re: [icinga-users] Icinga web 2 and graphite

knock knock ... Am 23.03.2015 um 16:21 schrieb dja...@nausch.org: > So, why icinga-web2 generates those escaped URLs and where can I change > this? Every thing works fine! Here's nothing to see ... Clearing the browser-cache solves my problems! :/ Head to desk, head to desk ... :/ ttyl Django

[icinga-users] Icinga web 2 and graphite

Heyho, O.K. I know, icinga-web2 is still beta and graphite-support is not jet in production-state. But I'm a very curious guy. :) So I've installed icinga-web2 (2.0.0-3.beta3.el7.centos) and graphite-web (0.9.12-1.el7.centos). If I look to my defined service_check eth0_traffic icinga-web

Re: [icinga-users] Notification sending using wrong user

Hi, What is in the templates "support-host-notification" and "infra-service-notification"? I think you only need two apply Notifications - one for hosts and one for services - untested example: apply Notification to Host { import "custom-host-notification" user_groups = host.vars.notif

Re: [icinga-users] Notification sending using wrong user

Hi Jürgen, What is the problem with the states and types of notification? H On Mon, Mar 23, 2015 at 3:49 PM, Jürgen Bastigkeit wrote: > Hi Henti, > > I think, you should review the states an types of the notifications. > iirc the possible states for a host- Notification are "Up, Down" . > "War

Re: [icinga-users] Notification sending using wrong user

Hi Henti, I think, you should review the states an types of the notifications. iirc the possible states for a host- Notification are "Up, Down" . "Warning, Critical, Unknown" are used for Service States. The Custom Type ist used for Notification from the web UI and Icinga itself uses "Problem"

Re: [icinga-users] Notification sending using wrong user

Sorry hostname was just to obfuscate the actual domain. the domain names are correct. H On Mon, Mar 23, 2015 at 3:20 PM, Jürgen Bastigkeit wrote: > Try "hostname" instead of hostnmae for the support user > > Best regards > Jürgen > Am 23.03.2015 14:15, schrieb Henti Smith: > >> email = "suppo

Re: [icinga-users] Notification sending using wrong user

Try "hostname" instead of hostnmae for the support user Best regards Jürgen Am 23.03.2015 14:15, schrieb Henti Smith: email = "support@hostnmae" ___ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/i

Re: [icinga-users] Notification sending using wrong user

Hi there, All configs below: /* users.conf */ object User "infra" { import "generic-user" display_name = "Infra" groups = [ "infra" ] email= "infra@hostname" } object User "support" { import "generic-user" display_name = "Support" groups = [ "support" ] email = "support@hostnm

Re: [icinga-users] Notification sending using wrong user

Am 23.03.2015 um 13:33 schrieb Henti Smith: Good day all. I'm struggling to get my notification working as expected and getting a strange behaviour where notification mail is sent using the wrong user. The check in question (http) is from a windows client discovered from the master. The check

[icinga-users] Notification sending using wrong user

Good day all. I'm struggling to get my notification working as expected and getting a strange behaviour where notification mail is sent using the wrong user. The check in question (http) is from a windows client discovered from the master. The check is Unknown in the web interface. First off the

Re: [icinga-users] Icingaweb2 ad_auth for admins, readonly for guests

Hi, On 2015-03-23 11:35, Tobias Schürjann wrote: Hi guys, I'm currently migrating from nagios to icinga2 / icingaweb2. Everything is working fine so far. I'd like to configure Icingaweb2 to use autologin for guests and ad_auth for admins. is that possible? The autologin directive is used for d

[icinga-users] Icingaweb2 ad_auth for admins, readonly for guests

Hi guys, I'm currently migrating from nagios to icinga2 / icingaweb2. Everything is working fine so far. I'd like to configure Icingaweb2 to use autologin for guests and ad_auth for admins. is that possible? I thought about using the resource autologin for readonly access via http://icinga2.l

Re: [icinga-users] Icinga2 frontends - ability to register command/service/etc...

is much more powerful, Hoe that helps Thanks Tal, On Mon, Mar 23, 2015 at 10:16 AM, Tal Bar-Or wrote: > Hello Yarden, > > As for Elk Icinga2 itergration they have Gelf wirter > > which nativly export Icnga2 ev

Re: [icinga-users] Icinga2 frontends - ability to register command/service/etc...

Hello Yarden, As for Elk Icinga2 itergration they have Gelf wirter which nativly export Icnga2 events/metrics data to logstach format etc... Regarding frontends to configure there is Netways Lconf