System health
CPU, memory, storage, processes and other technical states can be monitored.
Managed monitoring
Icinga 2 monitoring as a service from your IT company.
Monitor customer infrastructure, services and availability centrally. infrahost operates the monitoring platform; together we define the relevant checks and response paths.
Visibility before an incident
Detect problems before the customer has to report them.
Professional monitoring is not about producing as many green dots as possible. What matters are meaningful checks, understandable alerts, clear responsibilities and a process for incidents outside normal business hours.
infrahost provides a centrally operated Icinga 2 platform. Together with your IT company, we define which systems and services are monitored and who is notified at each level of criticality.
Scope of service
Monitoring that fits your operating model.
Checks and escalations are designed around the services you actually operate rather than applied as a generic template.
Services & availability
Websites, ports, certificates, DNS and other services are checked for availability.
Meaningful checks
Thresholds and check intervals are chosen so alerts remain actionable.
Alert paths
Notifications can be sent by email or passed to agreed integrations.
Ticketing integration
Alerts can be passed into a support system such as Zammad and handled in a traceable workflow.
Customer structure
Hosts and services are organised cleanly by partner, customer, site and criticality.
White-label delivery
Your monitoring service uses your senders and contact channels.
Dashboard, domain and alert communication can be adapted to your IT company’s brand. This keeps it clear to customers who provides the service and who is responsible when an incident occurs.
infrahost operates the technical platform and assists with complex checks, scaling and platform incidents.
- Monitoring domain under your corporate domain
- Customer and site structures aligned with your model
- Notifications with coordinated senders
- Role-based access for staff and customers
- Integration into existing support processes
Operations
Not every alert is an emergency — but every alert needs an owner.
Together we define which events are recorded only, which are handled during business hours and which require immediate escalation.
Check design
We define check scope, thresholds and dependencies to match the service.
Onboarding
Hosts, services, customers and contacts are onboarded into the platform in a structured way.
Alerting
Notifications are controlled by criticality, time window and responsibility.
Maintenance
Checks and the platform are adapted as systems, services or requirements change.
Transparency
Monitoring does not replace an agreed on-call service.
A platform can check systems around the clock, but that does not automatically mean a 24/7 human response. Support windows, escalation coverage and response targets are therefore agreed explicitly as service levels.
Frequently asked questions
Questions about managed monitoring with Icinga 2.
For binding details on architecture, scope and service levels, we discuss your specific environment.
Ask a technical questionWhich systems can be monitored?
A wide range of servers, network devices, services, certificates and applications can be monitored. The key requirement is a technically meaningful and stable check.
Can each customer have their own dashboard?
Customer-specific views and access are possible. Permissions and visible information are configured to match the user’s role.
Who responds to alerts at night?
That depends on the agreed service level. Without an explicit 24/7 agreement, alerts are recorded but are not automatically handled outside the defined support hours.
Can monitoring create Zammad tickets?
Yes. Integration into ticketing and notification processes is possible and is configured according to the partner setup.
Next step
Would you like to offer proactive monitoring to your customers?
Together we define checks, customer structure, alerting and responsibilities.