thomas-gelf / icingaweb2-module-iet Goto Github PK

in the past some efforts have already been made to pass the custom-variable "ticket_owner" (related to host- or/and service-objects) to the "Create Ticket" dialog/form. The appropriate field is labeled "Ticketgroup". But it hasn't been finished during that consulting-session. This is a prerequisite for a request from the business-team to further automation of ticket-creation. So it would be great if you could take a deeper look why this doesn't work as expected.

iET has an API with customized services differing in every setup. This module is not freely configurable yet, and MinimalMonitoringTicket is a customized implementation for a specific setup. That allows for adding one more custom field: Ticketgroup

IET Module should support dark mode.

Environment
IET Module: v0.9.0
Incubator Module: v0.18.0
Icinga Web: 2.10.3

Current

host.example.com is DOWN

Expected

host.example.com (192.0.2.10) is DOWN

After deactivation of "monitoring"-module in Icingaweb2 and "ido-mysql"-feature in Icinga2 the ticket-interface-form opens with wrong/outdated data transferred from the selected event.
Example: select a CRITICAL event in hardstate for a host, click on "Actions/Create Ticket" -> the ticket-form-dialogue opens with Priority "UP" instead of "DOWN" (Service: "OK" instead of "CRITICAL") and the "Summary"-field shows the message of the "UP"/"OK"-event.

This problem doesn't appear for all events - sometimes it works, sometimes not. The interface shows the same behaviour for UNKNOWN- and WARNING-events.

Both host- and service-events are affected.

With Icinga Web 2.11.x IET Module throws the following error when creating tickets:

Evenironment
IET Module: v0.9.0
Incubator Module: v0.18.0
Icinga Web: 2.11.1