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…)
Stability and user experience were the main goals for this release. Please read the full Changelog for all the details and the Upgrading instructions to be on the safe side. Spoiler: as always, upgrade is safe and super easy. (more…)
Flapping detection is a feature many monitoring suites offer. It is mainly used to detect unfortunately chosen thresholds, but can also help in detecting network issues or similar. In most cases two thresholds are used, high and low. If the flapping value, which is the percentage of state changes over a set time, gets higher than the high threshold, it is considered flapping. It will then stay flapping until the value drops below the low threshold.
I’m super excited for next week already – third time flying to the US joining community members at an Icinga Camp, this time San Diego after Portland and San Francisco.
“The Unrealized Role of Monitoring & Alerting” – Jason Hand from VictorOps takes the challenge to dive deep into metrics, alerts and learning from failures. We’ve seen such discussions at Devopsdays Amsterdam in June too and are super excited that Jason joins us in San Diego.
Blerim is also all about metrics – monitor all the things, retrieve metrics and present them in beautiful graphs on your dashboard. Be it Graphite or InfluxDB natively integrated with Icinga 2 or the all new shiny Grafana dashboard we’ve shared on grafana.net.
Rumors do tell that Icinga Web 2 added support for sending commands using the Icinga 2 REST API. Eric will prove that in his talk about new features coming with Icinga Web 2 v2.4.
Yet you’ve been eagerly awaiting a new Icinga Director release. Tom is busy coding and improving it and will showcase the latest and greatest additions – probably firing the last git commit and then starting the talk, as always 😉
Anything else all around the Icinga 2 API including live demos of existing tools and a revamped Dashing interface are waiting for you in Michael’s presentation.
Last but not least we’ll also have the latest project news and future outlooks with us – Bernd will kick off the Icinga Camp as always.
Still not convinced? We’ll be sharing the venue with PuppetConf 2016 on next Tuesday. If you love automation, you’ll surely want to learn about Icinga and Puppet all week long 🙂
Take a peek into all talks and make sure to join us – it is free, a full day of #monitoringlove in lovely San Diego.
The Icinga 2 API release is near – and so is OSMC where we will have demo setups with us. Users keep asking about how to already play and test-drive the Icinga 2 REST API, the answer is fairly simple:
- Read the snapshot docs (we update them frequently, so make sure to check for changes)
- Install Vagrant, Docker or fetch the snapshot packages directly
The benefit of using the Docker Container or the Vagrant Boxes – you’ll get everything pre-installed and pre-configured already to play with.
docker run -d -ti --name icinga2-api -p 4080:80 -p 4665:5665 icinga/icinga2
The container initialisation takes ~1 minute.
Example for Docker on OSX (change the IP address to your localhost):
curl -k -s -u root:icinga 'https://192.168.99.100:4665/v1/objects/hosts' | python -m json.tool
The container sources are located here, if you prefer to build it locally.
Both boxes icinga2x and icinga2x-cluster come with pre-configured Icinga 2 API.
git clone https://github.com/Icinga/icinga-vagrant.git cd icinga-vagrant/icinga2x vagrant up
curl -k -s -u root:icinga 'https://192.168.33.5:5665/v1/objects/hosts' | python -m json.tool
In case you have everything up and running (Packages, Vagrant or Docker) clone the Dashing demo and edit the icinga2 job API credentials here.
git clone https://github.com/Icinga/dashing-icinga2 cd dashing-icinga2
The following example uses the Docker IP address on OSX and the mapped port to 4665.
vim jobs/icinga2.rb $api_url_base = "https://192.168.99.100:4665/v1" $api_username = "dashing" $api_password = "icinga2ondashingr0xx"