As a little introduction for everyone who has not heard about the cube yet:
The cube module is there to show statistics grouped by the custom variables that have been set for the hosts and services. They are then displayed in up to three dimensions for a quick overview to show the relations.
The services are going cubin’!
The most prominent change is the addition of services:
While it used to be only possible to have the hosts in a cube, the module has now been extended to provide full functionality with services as well.
You can easily switch between hosts and services, while we keep the filters of your cube in place!
No more SQL dump crashes! (or at least fewer)
PostgreSQL rollup syntax errors are now smoothed out and will work as intended – also including the documentation for the requirements.
Having custom variables names like SQL keywords also no longer break the cube!
- Fix SQL keywords breaking the queries #38
- Fix rollup syntax for PostgreSQL databases #29 + #24
Restrictions are in place
Adds a filter that considers protected custom variables.
The cube now polls the restrictions set in the monitoring module and only shows the hosts that the user has permission to view.
- Apply monitoring restrictions #33
- Respect protected custom vars #25
And just a pinch of UX
Removed the possibility to add more than three dimensions to the cube – we live in a three dimensional world after all.
When the name of a cube tile is too long to fit, it will no longer push everything else downwards but be shortened with an ellipsis instead!
- Limit to 3 dimensions #36
- Truncate long headers #35
Fixed pröblems with ümlauts
The URL encoding has been adapted so that both white spaces and umlauts are now supported!
Name your vars however you like!
- Fix Slices with whitespace or umlaut in data field #17
This release fixes a regression introduced with namespaces in 2.10 where advanced permission filters could result in a crash with many concurrent requests. It also fixes the problem that permission filters are sometimes not applied correctly. Thanks VSHN for sponsoring the development time!
Another problem hidden in the dark was introduced in 2.9 with changed reload signals. This caused the reload shutdown handler to deactivate host and hostgroup objects in the IDO database backend, with later activating them on startup reconnect. Large scale environments would suffer from seconds to minutes not seeing objects in Icinga Web 2 then.
Last but not least, our road to better code quality unveiled that certain compilers don’t treat us well with shared pointers references and resulting crashes. This release fixes crashes with logrotate signals and other timer related problems, e.g. state file handling.
We’ve also added some documentation improvements for the REST API, object types, feature overview and technical concepts with JSON-RPC cluster messages – inspired by the feedback from our Icinga Discourse 🙂
Checkout the full changelog for 2.10.5 here. Please note that SLES11 and Ubuntu14 packages are not available anymore.
Special thanks goes out to Elias Ohm from novomind AG 🙂 He’s been debugging and fixing the many issues with us together, magnificent team work!
Note: API and cluster/agent related problems will be fixed in 2.11, requiring us to rewrite large parts of the code base. You can help test the snapshot packages and provide feedback. Thanks in advance!
We are happy to announce a new bugfix release for Icinga Web 2. Official packages are available on packages.icinga.com. Community repositories might need a while to catch up.
You can find issues related to this release on our Roadmap.
LDAP – Community contributions, that’s the spirit
With the help of our users we’ve finally fixed the issue that defining multiple hostnames and enabling STARTTLS has never properly worked. Also, they’ve identified that defining multiple hostnames caused a customized port not being utilized and fixed it themselves.
There has also a rare case been fixed that caused no group members being found in case object classes had a different casing than what we expected. (Good news for all the non-OpenLdap and non-MSActiveDirectory users)
- LDAP connection fails with multiple servers using STARTTLS #3639
- LDAPS authentication ignores custom port setting #3713
- LDAP group members not found #3650
We take care about your data even better now
With this are newlines and HTML entities (such as ) in plugin output and custom variables meant. Sorry if I’ve teased some data security folks now.
- Newlines in plugin output disappear #3662
- Windows path separators are converted to newlines in custom variables #3636
- HTML entities in plugin output are not resolved if no other HTML is there #3707
You’ve wondered how you got into a famous blue police box?
Don’t worry, not only you and the european union are sometimes unsure what’s the correct time.
- Set client timezone on DB connection #3525
- Ensure a valid default timezone is set in any case #3747
- Fix that the event detail view is not showing times in correct timezone #3660
UI – The portal to your monitoring environment, improved
The collapsible sidebar introduced with v2.5 has been plagued by some issues since then. They’re now fixed. Also, the UI should now flicker less and properly preserve the scroll position when interacting with action links. (This also allows the business process module to behave more stable when using drag and drop in large configurations.)
- Collapsible Sidebar Issues #3187
- Fix title when closing right column #3654
- Preserve scroll position upon form submits #3661
Corrected things we’ve broke recently
That’s due to preemptive changes to protect you from bad individuals. Unfortunately this meant that some unforeseen side-effects appeared after the release of v2.6.2. These are now fixed.
- Multiline values in ini files broken #3705
- PHP ini parser doesn’t strip trailing whitespace #3733
- Escaped characters in INI values are not unescaped #3648
Though, if you’ve faced issue #3705 you still need to take manual action (if not already done) as the provided fix does only prevent further occurrences of the resulting error. The required changes involve the transformation of all real newlines in Icinga Web 2’s INI files to literal \n or \r\n sequences. (Files likely having such are the roles.ini and announcements.ini)
We’re happy to announce that we released an early version of Icinga Reporting today! With this release we create the foundation for an overall reporting functionality for Icinga by introducing a new way to work with collected data. At the same time we are also publishing the first use case of Icinga Reporting which enables you to calculate, display and export SLA reports for your hosts and services.
Icinga Reporting is the framework and foundation we created to handle data collected by Icinga 2 and other data providers. By definition Icinga Reporting does not collect or calculate any data. The framework processes usable data from data providers such as Icinga’s IDO or Icinga Web 2 modules and makes them available in different formats. The first version can display the data directly within the Icinga web interface or export it to PDF, JSON or CSV format. With scheduled reports you can receive the prepared data periodically via email.
Create Host Report
Create Scheduled Report
The IDO is the database where Icinga 2 stores all the status data it collects. It is also the first data provider for Icinga Reporting. We calculate the availability of your hosts and services over a certain amount of time and return a percentage value. This allows you to evaluate and compare the accessibility of you applications and network devices. You can use the data to check if you’re meeting your SLA (Service-Level-Agreement) and share it with your team and managers.
Open Source Projects
Icinga Reporting consists of multiple projects. We’re continuously working on updating and extending our existing Modules to provide data for Icinga Reporting. This release is at a very early stage and your feedback is very welcome and appreciated.
Join our community on community.icinga.com and have a chat with us about your reporting use cases and challenges! We will discuss Icinga Reporting on our upcoming Icinga Camps as well. The CfP for Stockholm, Milan and Zürich is still open for those who are interested in speaking at these events.
This release provides fixes for the InfluxDB and Elasticsearch metric writers. If you’re using TLS connections, the latter were not closed correctly. In addition to these fixes, we’ve also backported fixes for delayed and one-time notifications. Special thanks to mdetrano for being patient and testing this one.
Additionally, the Windows wizard has been updated and check_perfmon now supports non-localized performance counters. One of our customers sponsored improving mass-creation of downtimes via the REST API in HA enabled clusters, thank you.
Official packages are available on packages.icinga.com, have been pushed to Chocolatey and Raspbian will follow soon. Meanwhile check the changelog for v2.10.4.
Gut Ding will Weile haben. Or, Rome wasn’t built in a day. Though, I like the German version more because it’s not that quite a stretch.
Well, what this is all about you ask? It’s been the first quarter of 2017 when the first version of the Icinga Business Process Module had the chance to impress its audience. It’s gone rather quiet since then. But don’t worry, just two years later there is the solution to the so-called order it imposed on us: Chaos.
Okay, okay, straight to the point:
Previously it wasn’t possible to disable the automatically applied alphabetical order of nodes. It is now possible to simply grab a node and move it wherever you want it to. Or, to be the master of chaos, so to speak.
Ever wanted to re-use a process you defined within a different configuration? Without duplicating it? This has been an undocumented feature but is now fully integrated into the UI and documented.
Usability and Visualization
Additionally the breadcrumbs and the tree view were adjusted and got a lighter design to help those with epilepsy. Well, not quite correct, we just thought a change is due. Besides, the navigation has been enhanced by allowing you to jump to the overview using the breadcrumbs and letting external info URLs open in a new browser tab.
The full changelog can be found here.
All issues and features related to this release can be found on our roadmap.