easyNag
Version 3.7
easyNag for iPhone & iPad
easyNag is the most innovative, fastest and simplest app to interact with your Nagios, Icinga, OP5 Monitor, OpsView, Thruk/Naemon, Centreon or checkmk monitoring system.
New in Version 3.7
- Displays if a host or service is currently in downtime
- Parent & child support for checkmk, Thruk, Icinga Web2 and Icinga API
Features
- Nagios 3.x / 4.x Support
- Nagios XI API Support
- Icinga API Support
- Icinga Web 2 Support
- Icinga Classic Support
- checkmk Multisite Support
- OP5 API Support
- OpsView API Support
- Centreon API Support
- Thruk Support
- Naemon Support
- Save multiple instances
- Connect to multiple instances at once
- HTTP Basic / Digest Authentication Support
- PNP Graphs
- URL scheme (easynag://)
- Customizable swipe actions
- Master Control for checkmk
- Problems Overview
- Filter Options (all or only unhandled problems, filter critical/warning/unknown problems)
- Hosts Overview
- Regex keyword filter to hide specific services or hosts
- Service-Detail Overview
- Host-Detail Overview (with services of host)
- Downtime Overview
- Remove scheduled downtime
- Acknowledge service or host problem
- Acknowledge with expire time (Icinga / CMC only)
- Show author/comment of acknowledgement
- Force recheck service or host
- Disable / Enable notifications of service or host
- Disable / Enable ALL notifications of an instance
- Actions for multiple problems or hosts
- Schedule downtime for service or host
- Schedule downtime for all services of a host
- Instant acknowledge problem
- Instant force recheck problem
- Instant disable notifications
- US / EURO / ISO8601 / STRICT-ISO8601 date-format support
- iPad Support
- Dark Mode Support
Screenshots
FAQ
easyNag currently supports:
Centreon
checkmk Multisite
Icinga Classic
Icinga Web 2
Icinga API
Nagios 3.x / 4.x
Nagios XI API
OP5 API
OpsView API
Thruk 2.x
Thruk API
Setup is easy - just add a new instance with the URL to your monitoring system, your username and password. No server-side modification needed.
Centreon Example: https://example.com/centreon
checkmk Example: https://example.com/sitename/check_mk
Nagios Example: https://example.com/nagios/cgi-bin
Nagios XI Example: https://example.com/nagiosxi
Icinga API Example: https://example.com:5665
Icinga Web 2 Example: https://example.com/icingaweb2
Icinga Classic Example: https://example.com/icinga/cgi-bin
OP5 API Example: https://op5.example.com
OpsView API Example: https://opsview.example.com
Thruk 2.x Example: https://example.com/thruk/cgi-bin
Thruk API Example: https://example.com/thruk
You can choose between US (Default), EURO, ISO8601 and STRICT-ISO8601 date format, dependent on your monitoring configuration.
At instance setup you can also set a "default ack" message, which will be used for instant acknowledge.
Centreon Example: https://example.com/centreon
checkmk Example: https://example.com/sitename/check_mk
Nagios Example: https://example.com/nagios/cgi-bin
Nagios XI Example: https://example.com/nagiosxi
Icinga API Example: https://example.com:5665
Icinga Web 2 Example: https://example.com/icingaweb2
Icinga Classic Example: https://example.com/icinga/cgi-bin
OP5 API Example: https://op5.example.com
OpsView API Example: https://opsview.example.com
Thruk 2.x Example: https://example.com/thruk/cgi-bin
Thruk API Example: https://example.com/thruk
You can choose between US (Default), EURO, ISO8601 and STRICT-ISO8601 date format, dependent on your monitoring configuration.
At instance setup you can also set a "default ack" message, which will be used for instant acknowledge.
The date format depends on your monitoring setup. If you use Nagios Core, Icinga Classic or Thruk, look at the "date_format" setting in your main configuration file.
For other monitoring systems (e.g. Centreon, checkmk, Icinga API / Web 2) the correct format is already preselected.
US (Default): 12-24-2014 20:00:00
EURO: 24-12-2014 20:00:00
ISO8601: 2014-12-24 20:00:00
STRICT-ISO8601: 2014-12-24T20:00:00
For other monitoring systems (e.g. Centreon, checkmk, Icinga API / Web 2) the correct format is already preselected.
US (Default): 12-24-2014 20:00:00
EURO: 24-12-2014 20:00:00
ISO8601: 2014-12-24 20:00:00
STRICT-ISO8601: 2014-12-24T20:00:00
With instant ack you can quickly ack service or host problems. Just swipe the problem far to the right, and the problem will be acknowledged with your default ack message.
With the easynag:// URL scheme you can open or acknowledge a service or a host directly from a notification (e.g. Pushover/Mail/Prowl etc.).
Open host: easynag://?host=HOST&instance=EASYNAG_INSTANCE_NAME
Open service: easynag://?host=HOST&service=SERVICE&instance=EASYNAG_INSTANCE_NAME
Acknowledge host: easynag://?host=HOST&instance=EASYNAG_INSTANCE_NAME&action=ack
Acknowledge service: easynag://?host=HOST&service=SERVICE&instance=EASYNAG_INSTANCE_NAME&action=ack
Open host: easynag://?host=HOST&instance=EASYNAG_INSTANCE_NAME
Open service: easynag://?host=HOST&service=SERVICE&instance=EASYNAG_INSTANCE_NAME
Acknowledge host: easynag://?host=HOST&instance=EASYNAG_INSTANCE_NAME&action=ack
Acknowledge service: easynag://?host=HOST&service=SERVICE&instance=EASYNAG_INSTANCE_NAME&action=ack
No internet connection: Your iPhone is not connected to mobile network or WiFi. Please check your connection settings.
Can't connect to host: A connection to the given host isn't possible, maybe you have entered a wrong URL.
Unsupported URL: Your URL isn't supported or invalid.
Request timed out: The connection request timed out.
SSL connection failed: An error occured while attempting to establish a SSL connection.
SSL verification error: The SSL certificate of the given URL isn't trusted. Make sure your certificate is valid, otherwise activate "Accept any SSL Certificate" in the settings of the instance (not recommended).
Error: got status code 401: (Unauthorized). The authentication failed. Make sure you have entered the correct username and password.
Error: got status code 404: (Not found). Check if your URL is correct and valid.
Error: Login failed Login to your instance failed. Check your credentials and your webserver logfile.
Parsing Error: An error occured while parsing your instance. Maybe your version is unsupported.
Can't connect to host: A connection to the given host isn't possible, maybe you have entered a wrong URL.
Unsupported URL: Your URL isn't supported or invalid.
Request timed out: The connection request timed out.
SSL connection failed: An error occured while attempting to establish a SSL connection.
SSL verification error: The SSL certificate of the given URL isn't trusted. Make sure your certificate is valid, otherwise activate "Accept any SSL Certificate" in the settings of the instance (not recommended).
Error: got status code 401: (Unauthorized). The authentication failed. Make sure you have entered the correct username and password.
Error: got status code 404: (Not found). Check if your URL is correct and valid.
Error: Login failed Login to your instance failed. Check your credentials and your webserver logfile.
Parsing Error: An error occured while parsing your instance. Maybe your version is unsupported.