Ticketing Integration - CPNV-ES-MAS3-X/Pandora-Containerization GitHub Wiki
Pandora ITSM
Source : https://pandorafms.com/manual/!current/en/documentation/10_pandora_itsm/start
Pandora ITSM is the Integria IMS Ticketing system that just changed names.
Requirements
Requirements | Minimum | Recommended |
---|---|---|
Disk Space | 10 GB | 20 GB |
CPU | 2,4Ghz - Dual Core | Depends on use |
RAM | 1 GB | 4 GB |
Base System | CentOS 7 | - |
MySQL | 5.6 or later | |
PHP | 7.3 or later | |
Web browsers | Chrome, Edge, Firefox |
Setup VM
IP : 10.0.0.125 /24
User : cpnv ; Pa$$w0rd
Install base tools
# Install updates
sudo yum install update
# Install extra package
sudo yum install epel-release -y
# Install nano
sudo yum install -y nano
# Install SSH et config
sudo yum –y install openssh-server openssh-clients
sudo systemctl start sshd
sudo systemctl status sshd
sudo systemctl enable sshd
Install Pandora ITSM
# Install ITSM - as root
sudo curl -Ls https://pfms.me/deploy-integria | sh
# Base login
admin
integria
Config on Pandora FMS
If ITSM is not on dropdown menu, update Pandora
Pandora ITSM → People → Edit my user
Copy ID as follows
Connect Pandora FMS with Pandora ITSM
Test Alert
Create new alert with "Action" -> Create Pandora ITSM Ticket
To recheck if working as intended
Zoho - MON1
Very simple setup, just create an account and you can manage the "Desk" Service of Zoho
Interface looks like this
The ticket is generated by a Pandora FMS Alert that triggers once a module goes into critical
The ticket is generated by an email that is sent to : [[email protected]]
PandoraFMS Alert Configuration
Ticket Content
This is an auto generated ticket by Pandora because a module went CRITICAL.
Monitoring details
Data: _data_ (critical)
Agent: _agent_
IP : _address_
Module: _module_
Module Description : _moduledescription_
Timestamp: _timestamp_
Please check the issue and close this ticket when its resolved.