log1c Trainee

  • Member since May 10th 2016
  • Last Activity:
Posts
147
Likes Received
20
Points
850
Profile Hits
194
This forum was archived to /woltlab and is now in read-only mode. Please register a new account on our new community platform.

You can create a thread on the new site and link to an archived thread. This archive is available as knowledge base, safe and secured.

More details here.
  • For notification you need a user, a notification template (defines the notification in general, like what to notifiy for...) and an apply rule for where to use your notification.
    Check the documentation (it's good!) on Notifications!
  • log1c

    Replied to the thread Notifications (sometimes) not sent.
    Post
    little update:
    excluded the service (and others) from my "big" notification rule and created a new one with a one hour delay.
    As the checks were already critical for several days/hours the notification worked instantly.

    Will monitor if it works…
  • log1c

    Replied to the thread Notifications (sometimes) not sent.
    Post
    yes. It does exist
    (Quote from log1c)

  • log1c

    Replied to the thread Notifications (sometimes) not sent.
    Post
    ah, ok.
    here is what I got after adding a new notification rule for me to the service. This new rule has the same config (in director) as the Autoticketing rule:
    (Code, 14 lines)

    Untiln now there is nothing in the whole log concerning my service and the…
  • log1c

    Replied to the thread Notifications (sometimes) not sent.
    Post
    Right. But I didn't force a notification, only a re-check of the service(s).
    After updating the notification rule with a new service this new service got notified after the next check.
    I updated my last post with more logs
  • log1c

    Replied to the thread Notifications (sometimes) not sent.
    Post
    Added a new test notification rule, forced a re-check and the notification got sent ?(:/

    (Code, 13 lines)


    Output from icinga2 object list --type Notification --name *Autoticketing-xxx-Services*
    (Code, 47 lines)



    edit:
    found this in the debug log after…
  • log1c

    Replied to the thread Notifications (sometimes) not sent.
    Post
    Some more info from the api (/v1/objects/notifications)
    (Code, 5 lines)


    I don't get why the notifications don't work for the service
  • log1c

    Replied to the thread Monitoring two or more interfaces.
    Post
    I can recommend the nwc_health plugin in general. It works great and is well documented.
    It has the option to use regex for interface names. Maybe if you define the regex close enough you will be able to check just your two wanted interfaces. But I…
  • log1c

    Like (Post)
    Was Icinga Web 2 Themes und die Installation angeht hilft vielleicht auch ein Blick hier rein: https://github.com/Icinga/icingaweb2-theme-company :)
  • log1c

    Replied to the thread Notifications (sometimes) not sent.
    Post
    some additional info:

    tried sending a custom notification, but no notification was created:
    (Code, 2 lines)

    Then forced sending the custom notification and two notifications were created:
    (Code, 4 lines)


    Also found something very similar in another…
  • log1c

    Thread
    Hi all,

    I am not sure if this is an Icinga2 issue or an´Icinga Director issue, but as I used the Director to configure the notifications I'll put it here.

    I have the following notification apply rule:
    (Code, 12 lines)

    And normally the notifications…
  • Habe gerade SDK 5.5 durch SDK 6.5 ersetzt und die Meldungen sind weg!
    Dazu hab ich folgende Perl-Modulversionen installiert (weil das SDK das gerne möchte)
    ExtUtils-MakeMaker-6.96
    libwww-perl-5.837
    Module-Build-0.4205
  • May this issue be due to not automatically applied schema upgrades for 2.5.0?

    I updated another system yesterday.
    Director 1.4.2 was already installed.
    After updating Icingaweb2 to 2.5.0 I was logged in as "user" again. Logged out, logged in again as…
  • War ebenfalls als "user" angemeldet. Ab- und Anmelden hat geholfen!

    Warum ist man nach dem icingaweb2 Update auf Version 2.5.0 als "user" angemeldet? Dieser Nutzer existiert bei mir eigentlich gar nicht!
  • Hatte heute das gleiche Phänomen, nach dem Upgrade.
    Kontrolliere doch mal bitte unten links, ob du als "user" angemeldet bist.

    Bei mir hat ein abmelden und wieder anmelden geholfen, dann stand auch wieder der korrekte Benutzername im Feld.
    Sonst mal…