Icinga

The typical implementation process for Icinga software involves:

1. Installing the core Icinga 2 software.

2. Setting up the database backend (e.g. MySQL).

3. Installing and configuring Icinga Web 2 interface.

4. Defining hosts and services to monitor.

5. Configuring notifications.

The implementation time can vary depending on the environment complexity, but a basic setup can be completed in a few hours to a few days. The documentation provides step-by-step installation guides to assist with the process.

Yes, Icinga can be extensively customized to fit specific business needs:

• Flexible configuration language allows defining custom objects and rules.

• Modular architecture supports developing custom plugins and extensions.

• API enables integration with other systems and tools.

• Customizable web interface and dashboards.

• Support for custom variables to add business-specific attributes.

• Ability to create custom check commands and notification methods.

• Option to develop custom modules to extend functionality.

Additional costs may include:

• Repository Subscription for enterprise Linux distributions (starts at $5,000/year).

• Support Subscriptions (Basic plan starts at $15,000/year).

• Training courses (pricing not publicly listed).

• Consulting services for complex implementations (custom pricing).

The core open-source software remains free for community distributions.

Icinga offers the following training and support options:

• Official documentation and guides.

• Community forums for peer support.

• Official training courses (Fundamentals and Advanced levels).

• Basic, Premium and Enterprise support plans with varying SLAs.

• Consulting services for implementation assistance.

• Webinars and blog posts with tips and best practices.

Security measures in Icinga include:

• TLS/SSL encryption for communication between nodes.

• Role-based access control for web interface.

• API authentication and authorization.

• Regular security updates and patches.

• Option to run in isolated network segments.

• Ability to mask sensitive data in logs and outputs.

Icinga typically releases:

• Major versions: Every 1-2 years.

• Minor versions: Every few months.

• Patch releases: As needed for bug fixes and security updates.

Updates can be managed through package managers or manual upgrades. The project maintains multiple supported versions simultaneously.

Icinga's policy on data ownership and portability:

• As an on-premises solution, customers retain full ownership of their monitoring data.

• Data is stored in standard database formats (e.g. MySQL) allowing for export.

• APIs enable programmatic access to configuration and monitoring data.

• Open-source nature allows full access to all data structures.

However, I could not find an explicit data ownership policy statement from Icinga.

Terms for scaling:

• Icinga architecture supports horizontal scaling by adding nodes.

• No hard limits on number of monitored objects.

• Repository Subscription may require adjustment for additional servers.

• Support plans have different limits on number of supported Icinga servers.

Detailed scaling terms are not publicly available and may require contacting sales.

Contract renewal and cancellation terms:

• Repository Subscriptions are typically annual.

• Support Subscriptions renew automatically unless cancelled.

• 30-day notice required for non-renewal of support contracts.

• No long-term commitments required for open-source usage.

Specific terms may vary based on contract type and are not fully detailed in public documentation.

Icinga software complies with:

• GDPR requirements for data protection.

• PCI DSS for organizations handling credit card data.

• HIPAA for healthcare organizations (when properly configured).

However, Icinga itself is not explicitly certified for specific compliance standards. Compliance is largely dependent on how the software is implemented and operated within an organization's environment.