Be informed of the latest product updates, and more importantly security patches!
A new update for Centreon web 21.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-21.10.11
A new update for Centreon web 21.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-21.04.19
A new update for Centreon web 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-22.04.6
A new update to Centreon Web 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-22.04.6
It's been close to 5 months now since we released Centreon 22.04.Thousands of platforms around the world have been upgraded and there have been some minor updates to address early adopter findings. We will be releasing 22.10 in a few weeks, but if you prefer staying on the n-1 version, now is the right time to consider an upgrade to 22.04. 22.04 brings many improvements, as well as important security and functional fixes. Key fixes in Service Pack 1 include:Centreon Web Fixed some security vulnerabilities Several fixes in Resources Status (export graphs, detail panel) Added OpenID Connect auto-import and OpenID Connect roles management Improved database storage to avoid blocking Broker when maximum values are reached MBI Fixed an issue related to the new password policy that would prevent reports from being generated. BAM Fixed failure at module installation when 24x7 timeperiod is missing MAP Services not accessible in desktop client in case of high number of notifications Complete release notes as well as upgrade procedure are available in the Centreon Documentation. If you are using a commercial edition of Centreon, please check the maintenance table below to ensure you remain fully supported: Version End of support State Centreon 22.04 05/2024 Supported Centreon 21.10 11/2023 Supported Centreon 21.04 10/2022 Will soon be unsupported Centreon 20.10 04/2022 No longer supported Centreon 20.04 10/2021 No longer supported Centreon 19.10 04/2021 No longer supported Centreon 19.04 10/2020 No longer supported Centreon 18.10 04/2020 No longer supported If you have already deployed 22.04, please check the table below for versions of individual components included in Service Pack 1. Component Minimum version in SP1 Centreon Web 22.04.6 Centreon Collect 22.04.1 Centreon Gorgone 22.04.1 Centreon MAP 22.04.1 Centreon BAM 22.04.2 Centreon MBI 22.04.1 Centreon Autodiscovery 22.04.1 Centreon Plugin Pack Manager 22.04.0 Centreon License Manager 22.04.0 Centreon anomaly Detection 22.04.0 Centreon High availability 22.04.0 Centreon DSM 22.04.0 Centreon Open Tickets 22.04.0
A new update for Centreon collect 21.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-collect-21.10.3
A new update for Centreon gorgone 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-gorgone-22.04.1
A new update for Centreon gorgone 21.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-gorgone-21.10.3
Always with the intent to provide the most flexible monitoring possible and let the user choose what kind of monitoring fits its needs in terms of deployment, customization, and security, we continue to leverage Prometheus & Node Exporter capabilities. What’s new? Target Discovery When working with DevOps teams, they often set up a Prometheus to watch over metrics generated by their applications and orchestrators instrumenting it during the whole deployment lifecycle. The Prometheus targets can now be discovered and mapped to a host in Centreon, and you can leverage labels to apply the right template or organize your configuration (Groups, Categories) thanks to the Host Discovery mappers. Windows Monitoring The Prometheus community is maintaining a Windows Exporter that let you easily deploy a lightweight exporter to monitor basic and more advanced Windows systems and apps’ metrics.When comparing this solution against existing NSClient++ or WSMan, here is what you should keep in mind: doesn’t allow to run of custom scripts enable user-friendly Windows network interface monitoring is easier to deploy leverage Windows performance counters by design, therefore, could provide code-level monitoring of .NET applications The Pack comes with service discovery rules to make your deployment faster. Regarding metrics, we only implemented the default ones:If you’re interested in some more specific metrics from this list, just drop a comment below and we’ll add them to our backlog.
A new update for Centreon web 21.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-21.04.18
A new update for Centreon web 21.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-21.10.10
A new update for Centreon web 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-22.04.5
Centreon Amazon Web Services monitoring is made of tens of Monitoring Packs to constantly discover and monitor your Cloud infrastructure and services. As a monitoring administrator, you need to embrace the dynamic nature of cloud assets and make sure that getting a 360 view of the health of these assets doesn’t imply making concessions on the security. That’s why we introduced two major enhancements to the way we discover and monitor AWS Cloud services. Amazon Secure Token Service With the Amazon STS feature, use temporary credentials by making deploying a poller as an EC2 instance a poller inheriting privileges from its associated IAM role. You don’t need to store sensitive access and secret key anymore to scrape metrics from Cloudwatch, temporary ones are created upon request when a check is performed. From now, all AWS Packs support the AWSASSUMEROLE macro allowing you to comply with AWS security recommendations and get rid of hardcoded AK/SK pairs. Note that your host discovery module must be up to date to use this new capability. Amazon Unified discovery Until today, if you used 11 AWS services across three regions, you have to create 33 separate discovery job definitions… Say goodbye to all this pain and time wasted: you can now only stay at the region level and create only 3 definitions thanks to the new AWS Cloudwatch Discover Pack! Indeed, you can leverage the STS mechanism through the provider as access and secret key are not mandatory when using this meta-provider. Discover hundreds of assets in seconds: Exhaustive documentation is available here and we’re open to any feedback or comment!
A new update for Centreon bam 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-bam-22.04.2
New metadata available within your discovery rules How to set it up Leverage Tags to filter the discovery resultA few months ago, we added the capability to use VMWare Custom Attributes metadata as attributes when discovering ESX and Virtual Machines using the VMWare daemon and plugins. These Custom Attributes generally help vCenter administrators to logically group and organize their resources within the vCenter. One specific thing about these attributes is that they are user-defined, which means that every user can set their own key/value pairs. As an admin, you need complete control over a resource metadata value so that it can be a piece of reliable information to organize your CMDB, manage permissions, or provision your monitoring efficiently! New metadata available within your discovery rules Based on your feedback, we decided to make available new metadata commonly defined at your ESX/vCenter level: Tags indeed! The goal behind it is to align Centreon capabilities with those of the standard automation tools like Ansible and make your life easier by adding some magic to your operations: Provision your VMWare resources using your favorite automation tools, tag your resources with any key/value that is relevant to your use case Discover these resources thanks to Host Discovery Leverage associated metadata to organize your monitoring (groups, categories) or apply different templates (apply OS or Application template to each resource associated with a given tag). You can read more about Tags and Custom Attributes on the VMWare blog. Let’s see how it appears in the VMWare UI from a user perspective (it may differ depending on your version). We will focus on the centreon-central-vm. Those tags will help apply a template, filter out some results, or assign a specific dimension. Categories aren’t managed (yet), but we would love to hear from you in the comment section if you have such a need. How to set it up You must have a Centreon version > 21.04 and Centreon VMWare daemon > 3.2.5 to use this feature. To benefit from tags management, you will have to perform several actions. It will not take you more than five minutes! Update your VMWare daemon, and restart it On poller(s) executing the centreon-vmware daemon, update the package: RPM Distributions: yum update centreon-plugin-Virtualization-VMWare-daemon Debian 11: apt upgrade centreon-plugin-virtualization-vmware-daemon Restart the daemon: systemctl restart centreon_vmware Update your Monitoring Pack(s) Upgrade your VMWare Monitoring Packs on your central server, providing Host discovery rules. If you are using an offline license, upgrade packages first: RPM Distributions: yum update centreon-pack-virtualization-vmware2-vm centreon-pack-virtualization-vmware2-esx Debian 11apt upgrade centreon-pack-virtualization-vmware2-vm centreon-pack-virtualization-vmware2-esx > If you want to monitor VMWare resource for the first time, substitute update/upgrade by install in the commands above. Go to the ‘Configuration > Plugin Packs” menu and click on the VMWare ESX and VMWare VM Packs to install. Create or update your Host Discovery job definition Go to “Configuration > Hosts > Discovery”. If you create a discovery job for the first time, check out this documentation before going further. If you update an existing one, just click on your current job definition and add --tags within the ‘Extra Options’ field: Note that we increased the timeout to 30 seconds as the API for tags differs from the one used for monitoring, and calling it for each of the discovered assets introduces some extra processing. Leverage Tags to filter the discovery result Once your job successfully runs, you should see the result of the discovery on the right. Here I discovered 136 virtual machines: To leverage tags on my ‘centreon-central-vm,’ we can use three kinds of mappers: Exclusion, to exclude all VM with a tag with monitoring as a tag description and for which the tag name doesn’t match enabled. Template, to apply the OS-Linux-SNMP-custom template to VM having OS as a tag description and linux as a tag name. Host group, to create/assign the prod host group to every VM having the tag name prod: The final result before hitting save will be similar to: From 136 results, I was able to filter on the very specific VM interesting me: Enjoy! As usual, share your feedback in the comments to help us continuously improve this feature.
Monitoring Packs refactoring 🔧 Enhancements 💡 New Monitoring Packs - Community powered 🚀Monitoring your Azure deployments is key to observing how your cloud migration goes and/or how Microsoft IaaS/PaaS platforms behave over time while running your applications. This summer, we’ve brought several enhancements to Azure monitoring to align all probes and packs to the latest best practices. That might impact your current configuration so be careful when updating your Monitoring Packs to avoid false positives. We’ve also added some minor improvements to existing Packs our customers expected to have a better vision of what’s going on in detail. Monitoring Packs refactoring 🔧 Here is the list of the Packs that benefit from the latest code optimization and documentation layout: Azure Virtual Machine Azure Express Route Azure SQL Database Azure SQL Server Azure Virtual Network Azure VPN Gateway Enhancements 💡 Last month, we released new tenant discovery host discovery rules to reduce the number of jobs to configure to discover all your Azure assets (Azure Discover Tenant Discovery). To deal with a huge number of assets (more than 20k), we introduced a new –select-type option to reduce the scope of the discovery and ignore resource types that are irrelevant. A new lookback option in the existing Items check has been added. It allows you to define how far in the past the plugin will look for failed VM/Vault backup allowing you to get rid of very old failed backups for which an alarm became irrelevant A new Replication mode is added to add broader support for recovery points. You can monitor your site/vaults' replication and failover health. New Monitoring Packs - Community powered 🚀 Thanks to an open-source contributor, two news packs have been added, and we love it! They will enable you to watch over your Azure objects allocation and financial spending carefully. Azure Active Directory: leveraging the Microsoft Graph API and helping you track the evolution and quota usage of objects configured on your Cloud Azure Directory. An explanation of how important it is can be found here. Azure Management Costs: connect to the consumption APIs provided by Microsoft to track down the financial spending for a given subscription or resource group. Very helpful to control and optimize your cloud costs over time! Use the embedded service discovery rule to add services without effort easily! All these enhancements and new capabilities are our this September. Make sure to check it out!
Hello Watchers, the holiday season is behind us.We took some rest and chose to group Monitoring Packs features and enhancements from August and September in a single release. A lot of thrilling features and ideas have been implemented during this period. All the centreon-plugins team hopes you’ll enjoy it. We also got exciting contributions from the community, and we love it! Shortly, some dedicated posts will appear on your favorite community platform to focus on some of this release’s highlights. Continue reading to get a quick overview of what you can expect from this release, and indeed if you want to deep dive into all the technical details, make sure to check the release note. New Monitoring Packs available Cloud MonitoringFrom major players like AWS or Azure to a more specific one like Informatica and its data integration service, discover new Packs to deploy a complete, intelligent and cost-controlled cloud monitoring as efficiently as possible. You can find all monitorable assets from an AWS region in minutes! Flexible IT-MonitoringNode Exporter Windows Metrics & Fortinet Fortigate Rest API brings new capabilities to monitor your Windows systems and network devices. Check out these new Packs assets on the documentation to know how to use them to enhance your existing monitoring setup. Hardware and appliancesWe released some new Packs for various hardware, including network devices (Netgear S-Series), appliances (Cisco Umbrella), and HCI (Dell EMC VxRail Manager). Enhancements Discovery Tag management with VMWare Discovery rules, SNMP Discovery customization, Prometheus Targets, EC2 platform details discovery … A bunch of enhancements to make your life easier and reduce the time-to-monitoring. Up-to-date monitoring We’ve updated a lot of probes to make them compliant with the latest firmwares and APIs versions. We also added some new modes and metrics to many of them. Check out the release note to know everything (don’t stay like Jon Snow)! Enhancements impacting current configurations Heads-up! We reworked all legacy Azure Packs. It requires you to be careful in your upgrade operation to ensure that both Pack and Plugin use the same version. Have a doubt? Take advantage of the ‘Automatic plugin installation’ feature! Bugfixes If you use one of the Packs above, you should consider upgrading. Fixed bugs might have more or less impact depending on how you use these Packs. If you want to know if you’re in a situation requiring a quick upgrade, the simple thing is to check the release note.
A new update for Centreon map 21.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-21.04.7
A new update for Centreon collect 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-collect-22.04.1
A new update for Centreon web 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-22.04.4
A new update for Centreon web 21.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-21.10.9
A new update for Centreon web 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-22.04.3
A new update for Centreon web 21.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-21.04.17
A new update for Centreon autodiscovery 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-autodiscovery-22.04.1
A new update for Centreon web 22.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-22.04.2
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK