OSS TanbouSign in with GitHub

check hosts, services, and networks on a schedule and notify on failures and recoveries

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
2,047
Primary language
C
License
GPL-2.0
Repository last updated
Aug 7, 2026
On this page

Overview

Nagios Core is a C monitoring engine for servers, network devices, and services such as HTTP. It evaluates plugin results and combines notifications, event handlers, history, and an optional web interface into an operator-controlled monitoring system.

Features and best fit

Hands-on tested within the scope below · Content checked:

Key features

Turn plugin results into failure and recovery notifications

It can monitor network services such as SMTP, POP3, HTTP, and PING, along with host resources such as processor load and disk usage. Custom checks can be added through plugins, and notifications can be sent when problems occur and recover.

Sources: [1]

Distinguish an unreachable path from a failed host

Parent hosts define a network hierarchy, allowing the engine to distinguish a host that is down from one hidden behind a failed path. Event handlers can invoke recovery actions when state changes occur.

Sources: [1]

Best fit

Unify checks across an existing mix of devices and servers

It fits on-premises and mixed environments where each target needs tailored commands and thresholds. File-based configuration also lets a team review monitoring changes alongside other operational code.

Sources: [1][4]

Before adoption

Plan the core, plugins, notifications, and web interface together

Nagios Core does not supply every target-specific check by itself. The official quickstart installs the core and Nagios Plugins separately and configures Apache and PHP when the web interface is needed. Run nagios -v after configuration changes so errors are found before startup.

Sources: [2][4][3]

Nagios Core 4.5.14 / Docker 29.4.0 with debian:13-slim on a local arm64 host

Built the core and sample configuration in a disposable image, then ran nagios -v and observed 0 warnings, 0 errors, and a successful pre-flight check.

Official sources

  1. [1]Nagios Core 4.5.14 README(2026-10-04)
  2. [2]Nagios Core 4.5.14 installation pointer(2026-10-04)
  3. [3]Nagios Core 4.5.14 configure source(2026-10-04)
  4. [4]Nagios Core 4 Ubuntu quickstart(2026-10-04)
  5. [5]Nagios Core 4.5.14 release(2026-10-04)
  6. [6]Nagios Core 4.5.14 license(2026-10-04)
Supplemental curator note

Its plugin model and file-based configuration make it useful when checks must match an existing mix of devices and servers and remain reviewable. Plan the required plugins, notification paths, web interface, and permissions before rollout.

Try it in 3 steps

  1. 1

    Enter the 4.5.14 source tree

    On a system with Git and Docker, fetch only the published 4.5.14 tag and enter its working directory.

    git clone --depth 1 --branch nagios-4.5.14 https://github.com/NagiosEnterprises/nagioscore.git nagioscore-demo && cd nagioscore-demo
  2. 2

    Create a Dockerfile for an isolated build

    Define a Debian 13 build with the compiler, gperf, GD, OpenSSL, and other required packages, then install the core and sample configuration under /opt/nagios without installing it on the host.

    printf '%s\n' 'FROM debian:13-slim' 'RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends autoconf gcc gperf libc6-dev make libgd-dev libssl-dev perl unzip ca-certificates && rm -rf /var/lib/apt/lists/*' 'WORKDIR /src' 'COPY . .' 'RUN groupadd --system nagios && useradd --system --gid nagios nagios && ./configure --prefix=/opt/nagios --with-nagios-user=nagios --with-nagios-group=nagios --with-command-group=nagios && make -j2 all && make install && make install-config' 'CMD ["/opt/nagios/bin/nagios","-v","/opt/nagios/etc/nagios.cfg"]' > Dockerfile.quickstart
  3. 3

    Build and run the configuration preflight

    Build the isolated image and use nagios -v to load the sample configuration. Confirm Total Errors: 0 and a successful pre-flight check; the verification container then exits and is removed.

    docker build --file Dockerfile.quickstart --tag nagioscore-demo:4.5.14 . && docker run --rm nagioscore-demo:4.5.14
Check the official README

Growth

Growth trends · Last 30 days

2,047 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
0
Open PRs
5

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data
Stars
2,047
Forks
482
Watchers
109
Open issues
204
Contributors
110
Owner type
Organization
Primary language
C
License
GPL-2.0
Repository last updated
Aug 7, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?