Incidence Management

Go back to Pandora FMS documentation index

Pandora FMS is completely integrated with Integria IMS ticketing tool.

Integria IMS is a full on-premise incidence management software. It belongs to Pandora FMS suite and it has been designed to be multi-user and multi-group, with support for different profiles and with the possibility of internal audit.

Communication between Pandora FMS and Integria IMS is done through Integria IMS API.

To access this integration, do it through the menu Setup > Setup > Integria IMS from Pandora FMS visual console.

Click on Enable Integria IMS to enable it. Configure the following fields:

User

User registered in Integria IMS.

Password

User password.

API Hostname

IP address or Integria IMS server URL.

API Password

Integria IMS API password.

Request timeout

Maximum waiting time for API requests. Disabled with 0.

Ask Integria IMS administrator about the previous values.

Once set, and after testing connection with the button Start, you will have two different sections:

• Alert default values.
• Event custom response default values.

Alert default values

Section where default values with which the ticket will be created through alerts will be set.

Event custom response default values

It is used to set the default values that the ticket will have when you proceed to create it through the event response.

However, both Alert default values and Event custom response default values share common fields that will be applied by default. Remember that these fields and other options are obtained from Integria IMS through system APIs:

• Title and Description: Name and ticket detail.
• Group: Group registered in Integria IMS to which the ticket will be assigned ( API get_groups ).
• Priority: Ticket priority in Integria IMS ( API get_incident_priorities ). See in the reference section the normalized values.
• Owner: Usuer registered in Integria IMS the ticket will belong to ( API get_users ).
• Type: Typ of ticket registered in Integria IMS ( API get_types ).
• Status: Ticket status. See in the reference section the the normalized values.

Find more information about Pandora FMS console configuration in this section.

When using Integria IMS together with Pandora FMS you may integrate different work computers and each software will take care of avoiding duplicates without losing synchrony nor control between both applications.

Pandora FMS feeds Integria IMS though events and/or inventory, making sure to have a single follow-up. In addition, you may delete them automatically in Integria IMS, as long as they do not have incidences. Although you may see Ingria IMS summaries in Pandora FMS, all information is actually in Integria IMS. All of this is possible by using the APIs created specifically for those tasks.

As for the inventory, you are provided with a manual option that synchronizes all the required information from Pandora FMS to Integria IMS, as well as inventory alerts to set in place alert triggering for Integria IMS.

Once configuration is enabled, a new submenu is added to the menu Workspace → Issues → Integria IMS Tickets. By clicking there, Pandora FMS will look for the information in Integria IMS (you may filter it) and next the list of all tickets.

Through the search tool, you may filter and request through Integria IMS API by the following fields:

Text filter

Text field that searches through id, title and description fields.

Status

Status of the searched tickets (status list obtained through the API get_incident_status). See in the reference section the the normalized values.

Group

Group the searched ticket belongs to (groups obtained through the API get_groups).

Owner

User the searched ticket belongs to (list of users obtained through the API get_users).

Creator

User who created the searched ticket (list of users obtained through the API get_users). Enter at least two characters to see the list of matching users.

Priority

Ticket priority (list obtained through the API get_incident_priorities). See in the reference section the the normalized values.

Resolution

Searched ticket resolution (list obtained through the API get_incident_resolution). See in the reference section the the normalized values.

Date

Searched ticket creation date. You may set from a certain date to another in Created from and Created to, accordingly.

From the ticket list, click on the name of one of them to see its details.

If you have permissions, at the bottom you will see the attached file and comment management box. They can be edited by clicking on Attached files and Comments accordingly.

Click on the pencil icon to edit the ticket. Also through the icons next to ityou may go to the ticket list, configure Integria IMS (if necessary) and see the ticket again (refresh screen).

You may create tickets in Integria IMS manually and through event custom response; also automatically: through general alerts and inventory alerts.

If the users have enough permissions, they will be able to fill in the fields and create an incidence in Integria IMS.

Go to Workspace → Issues → Integria IMS Tickets and click Create.

Remember that all these fields and their options are obtained from Integria IMS through the API of that system (the incidence is created with the API create_incident).

Title

Incidence name field.

Type

Ticket type obtained (API get_types).

Group

Group the ticket will be assigned to (API get_groups).

Criticity

Ticket priority (API get_incidet_priorities).

Status

Ticket status (API get_incident_status).

Creator

Ticket creator (API get_users).

Owner

User the ticket belongs to (API get_users).

Description

Text field for comments.

Once you finish filling up the data, click Create to save the new ticket. The creation process will be performed through the API create_incident.

From the icon Show more of each event, in the tab Responses you may select a Custom response by choosing the Integria IMS option Create incident in Integria IMS from event. Click Execute and the process will be the same as that described in the previous section. The fields will be those configured in the Setup (Event custom response default values), which can be changed if necessary.

Remember to select the field Type; click Create to save.

Define the alert command specifying the name and the group the alert command belongs to. You may create as many different commands as you need. For Integria IMS, it is a special case, internal type.

Once done, go to alert correlation creation which is explained in detail in that section.

Inventory alerts are available from version NG 751. They work similarly to ticket creation through general alerts and are described in more detail in this link.

• Informative: (By default).
• Low.
• Maintenance.
• Medium.
• Serious.
• Very serious.

• Duplicate.
• Expired.
• Fixed.
• Incomplete.
• In process.
• Invalid.
• Moved.
• None.
• Won't fix.
• Works for me.

• Assigned.
• Closed.
• New(by default).
• Pending on a third person.
• Pending to be closed.
• Re-opened.
• Unconfirmed.

Go back to Pandora FMS documentation index