Our journey of Icinga integrations continues – we’re announcing the general availability of the Icinga Module for Jira v1.0 today! Jira is a ticketing system created by Atlassian and it’s one of the most popular ones of its kind. Jira is used by a very diverse audience: Developers, Managers, SREs, Systems Engineers and everyone else who needs to keep track of issues and projects. The Icinga Module for Jira extends Icinga with multiple functionalities to create seamless workflows between Icinga and Jira.
Create Issues on Problems
When Icinga detects a problem in your infrastructure, be it a host that is down or a service that is critical, this module helps you by creating an issue for each problem automatically in Jira. This system comes in handy when multiple people work on problems or need to keep track of those.
The Icinga Module for Jira also keeps track of reoccurring problems, so you won’t create multiple issues for the same problem. Additionally, acknowledgements will be set automatically. If you don’t want to create issues automatically, you may create them manually through the Icinga Web interface.
To keep track of all existing issues created by this module, there’s a dedicated history overview. Further, a direct link to Jira is embedded at the host and service detail view leading you directly to related Jira issues.
Integrating with Jira Workflows
For those of you who are using customised workflows in Jira, this module brings a functionally to map those with the module. The highly configurable templates allow you to set custom values based on your existing workflow. You may set your team automatically or tag different problems with different tags.
Integrating with Director
The Icinga Module for Jira works based on a notification command that is included in ‘icingacli’ once the module is installed.
Users of the Director can simply just synchronise the related configuration and deploy it through Director to Icinga. This provides a hassle-free installation path where you don’t have to take care about creating custom Icinga configurations.
The documentation with a introduction is available on our website: Get started with Icinga Module for JIRA
We are proud to announce that icinga.com is now also hosting integrations of hardware for monitoring environmental sensors and alerting via text message. The devices from the manufacturers listed on Icinga Integrations can easily be implemented into your Icinga monitoring by using plugins provided on Icinga Exchange.
Alerts via Text Message
Basically, there are two types of devices, which are most suitable for integration with Icinga. First group of them are gateways for sending SMS as alert messages. These gateways work with standard SIM cards and can run on bands in 4G, 3G and 2G networks. These devices also provide more functionality than only sending messages, they are also capable of converting SMS to E-Mail or the other way round or using filters and routing for sending messages only to a certain person or group of persons (phonebook listing). Furthermore, the gateways have their own monitoring server which means that they can automatically send notifications for example in case of loosing connection to the network.
In order to smoothly add these gateways into one’s productive processes, there exist for example plugins for directly connecting to your Microsoft Exchange for full usage of E-Mail to SMS conversion. Integrated with Icinga 2 you cannot only monitor the device itself but also use it in order to forward notifications generated by Icinga. The two main manufacturers of these gateways are Braintower located in Germany and SMSEagle with their headquarters in Poland.
Second type of integratable devices are mainly meant for measuring and surveillance. These consist most of the time of a base unit and several ports for connecting sensors. The base units can either directly communicate via LAN or via GSM in case of remote locations. For full environmental monitoring, there are plenty of sensor types that can be attached:
- combination of temperature and humidity
- air pressure
- air flow
- water and leakage
- smoke and Gas
- levels of liquids like pertrol
- movement, vibration and opening of doors
The main manufacturers for measuring devices are currently AKCP, GUDE, HW group and Tinkerforge. For all these you can find monitoring plugins on Icinga Exchange. The manufacturer GUDE also offers power supplies that cannot only monitor voltage, but are also capable of remote controlling plugs and devices.
Integrating Tinkerforge with Icinga
In order to have a closer look at how these devices can be integrated with Icinga 2, Tinkerforge is one of the best examples. The whole plugin project can be found at https://exchange.icinga.com/netways/check_tinkerforge and shows not only the integration but also offers an insight into the functionalities of the device.
For using the check_tinkerforge plugin it is required to run Python 2.7+ and to have the tinkerforge Python library from Pypi installed. After this, installation is done with
pip install tinkerforge and moving the plugin into the Icinga
Now let’s have a look at the options of the plugin:
$ ./check_tinkerforge.py --help
usage: check_tinkerforge.py [-h] [-V] [-v] -H HOST [-P PORT] [-S SECRET]
[-u UID] -T TYPE [-w WARNING] [-c CRITICAL]
-h, --help show this help message and exit
-V, --version show program's version number and exit
-H HOST, --host HOST The host address of the Tinkerforge device
-P PORT, --port PORT Port (default=4223)
-S SECRET, --secret SECRET Authentication secret
-u UID, --uid UID UID from Bricklet
-T TYPE, --type TYPE Bricklet type. Supported: 'temperature', 'humidity', 'ambient_light', 'ptc'
-w WARNING, --warning WARNING Warning threshold. Single value or range, e.g. '20:50'.
-c CRITICAL, --critical CRITICAL Critical threshold. Single vluae or range, e.g. '25:45'.
-t TIMEOUT, --timeout TIMEOUT Timeout in seconds
As the TinkerForge device supports sensors like temperature or humidity as well as other types, we need to indicate what sensor should be checked by using the
check_tinkerforge.py -H 10.0.10.163 -T temperature -w 23
WARNING - Tinkerforge: Temperature is 24.75 degrees celcius|'temperature'=24.75
In case you have more multiple sensors of one type, you are required to indicate the UID with the
--uid operator in order to correctly identify the sensor in question. Furthermore, thresholds can either be indicated as single values or value ranges and by using the usual operators for warning and critical.
For integration of the sensors into your Icinga 2 configuration, you need to create a
CheckCommand object like for other check plugins. The device itself will be created as
Host object and all sensors should be covered with an
apply Service. For your comfort you can find an example config for TinkerForge here. This example can directly be used, it is only necessary to change the parameters and in case you have multiple sensors of one type, to add the UIDs.
All manufacturers mentioned in this blog post can be found on the Icinga integrations website including information on the companies, the devices and the links to the corresponding monitoring plugins.
It’s been a while since the last Vagrant box update and release, so here are the highlights of the past months combined into a new shiny 2.0 release 🙂
New provider: OpenStack
In the past week I’ve been playing with OpenStack. Johan was so kind to send a PR nearly 2 years ago, now the NETWAYS NWS cloud is ready for OpenStack and my tests. Small things were needed to adopt the box provisioning with floating IPs. If you are an experienced OpenStack user, you’ll know how to source everything into your environment. Everyone else just can follow the newly written docs 🙂
Huge shout-out to Johan from CSC for his contribution!
Building your monitoring landscape can be a hard task. The main reason for this is the sheer amount of available solutions. Even though, each of them has their own reason for existence. One challenge during the discovery phase is to find out if the tools you selected can work together. If they have integrations for each other or if they can use the same storage backend. OpenAPM aims to help you find out which parts can work together and how you may use them in combination. Further, it gives you some inspiration on what you can change to get your perfect monitoring stack. (more…)
One of the biggest advantages of Icinga is its capability to interact with other tools. Integrations of Icinga cover notification mechanisms, visualisations or automatic deployment. Especially our REST API allows users to easily connect with Icinga, be it for read access or the creation of new objects.The possibility to automate allows Icinga users to monitor highly dynamical infrastructure in private and public clouds. (more…)
Icinga2 is an open source IT infrastructure monitoring tool that shines with its performant and highly configurable monitoring solution. It has built-in notification scripts such as e-mail, SMS, and Twitter to send notifications when an alert is triggered. These scripts, combined with configuration files, give you basic alerting capabilities such as notifying a team. Often teams need more advanced workflows and alerting needs.
In this blog post, you’ll learn five different ways OpsGenie helps Icinga users. Before starting, let’s talk a little bit about OpsGenie. (more…)