the md format gets confused when using the | (the pipe character) in certain situations. I have a branch request.

If it sees a pipe character and it is not included in text that associated with a paragraph, it assumes that it is a table and the pipe marks the end of the cell.

http://www.naemon.org/documentation/usersguide/objectdefinitions.html#host_definition lists check_period as a required attribute. This is not the case; if left unset the check_period for a host will be 24x7.

In looking up the documentation for what the module-conf.d directory, I found that the include_dir variable is documented in the naemon.cfg file but is missing from the website's documentation.

Hi;

I try to install naemon from (https://download.opensuse.org/repositories/home:/naemon/CentOS_8_Stream/) but this repository is empty or not exists.

I am running debian 8.x so I went to the quickstart-debian page. Part of the instructions is to use wget to retrieve a bunch of files, then use dpkg -i naemon*.deb to install them. The problem here is that you have a package named libnaemon, that isn't in the list of things to download with curl, and wouldn't be matched by the wildcard pattern used with dpkg. If you follow these steps the install fails, because it is missing libnaemon. The documentation should be updated.

Ref:

• https://github.com/naemon/naemon.github.io/blob/master/documentation/usersguide/quickstart-debian.md
• https://github.com/naemon/naemon.github.io/blame/master/documentation/usersguide/quickstart-debian.md#L45

As an alternative, you could post a set of directions similar to this in the quickstart, that would let people download the packages, and then add a local apt repo. Using the wget in recursive mode would
automatically get all the packages in the directory. Also you wouldn't need to have to instruct the users to manually pre-install the dependencies.

# update this to be the base URL for your release/arch
releaseurl='https://labs.consol.de/naemon/release/v1.0.3/debian8/amd64/'
# update this to be a local path where you want to cache the packages
packagedir='/usr/src/naemon/'
# make folder to cache packages
mkdir -p ${packagedir}
cd ${packagedir}
# download the packages
wget --recursive --timestamping \
     --no-parent --cut-dirs=2 --no-host-directories \
     $releaseurl
# build an packages file for apt
cd ${packagedir}v1.0.3/
dpkg-scanpackages . /dev/null > Packages
# add to apt
echo "deb file:${packagedir}v1.0.3/ ./" > /etc/apt/sources.list.d/99naemon.list
# install (will show up as untrusted, since this is not gpg signed)
apt-get update && apt-get install naemon

Got this mail automatically after fixing a typo on the page:

The page build completed successfully, but returned the following warning:

You are currently using the 'redcarpet' Markdown engine, which is no longer supported by GitHub Pages and may cease working at any time. To ensure your site continues to build, remove the 'markdown' setting in your site's '_config.yml' file and confirm your site renders as expected. For more information, see https://help.github.com/articles/updating-your-markdown-processor-to-kramdown.

For information on troubleshooting Jekyll see:

https://help.github.com/articles/troubleshooting-jekyll-builds

If you have any questions you can contact us by replying to this email.

I'm on it.

To the best of my knowledge, I believe that removing the CGI's was a big reason for forking, so it seems redundant to have this documented.

http://www.naemon.org/documentation/usersguide/cgis.html

It would be nice if the table of bugs is sortable and/or could be filtered by state

THX :)

On the bugs page:

http://www.naemon.org/documentation/developer/bugs/

The sort slightly covers the "Id" column header.

Also, the bugs are sorted from lowest to highest. I personally like highest to lowest. I looked at the actual markdown which looks good.

https://github.com/naemon/naemon.github.io/blob/master/documentation/developer/bugs/index.md

Not positive how to make changes to the markdown/site so the markdown works better when formatted to HTML. I can help fix but would need some direction in how.

Hi all,
I would like to add a searchable list of all available Naemon default macros to the openITCOCKPIT interface:

Can i just copy and paste the macro description from https://raw.githubusercontent.com/naemon/naemon.github.io/master/documentation/usersguide/macrolist.md? I don't want to get in trouble with you guys :)

At least for me, it looks like that the documentation of use_aggressive_host_checking is a lie.
From what I learned in naemon/naemon-core#278 this option just swaps the return codes so that a plugin designed for service checks can also be used for host checks.

I scraped real quick through the code and it is just used in one `if``:
https://github.com/naemon/naemon-core/blob/492b8f81af4f57aba69c154881730b5843835647/src/naemon/checks_host.c#L507-L508

The documentation is talking about performance impacts and other things that just looks total wrong to me.
https://www.naemon.io/documentation/usersguide/tuning.html#avoid_aggressive_host_checking
https://www.naemon.io/documentation/usersguide/configmain.html#use_agressive_host_checking

If you guys agree, I will send a pull request to fix this.

Hi,
You missed libnaemon download link in installation guide. (naemon depends on it and it requires for wheezy in my case)

It would be very helpful to have a search box on the page to be able to search the documentation without relying on external search providers such as google or duckduckgo.

Noticed the following:

Specifically this one: http://www.naemon.org/documentation/usersguide/upgrading.html

The "Upgrading From Nagios 2.x" section title is flowed into the list above.

It is rendered fine here: https://github.com/naemon/naemon.github.io/blob/master/documentation/usersguide/upgrading.md

When you scroll down on the Plugin API page eventually you get to the part where the documentation explains the contents of macros. The data is rather large and can mingle with the TOC on the side.

I'm using Chrome as my browser. Have not tested on any other browsers.

Not positive how to make changes to the markdown/site so the markdown works better when formatted to HTML. I can help fix but would need some direction in how.

The release date on naemon.io is wrong:

    You can use this repo: https://labs.consol.de/repo/stable/#_8

The OBS builds stopped working with all this centos BS.

Originally posted by @sni in #147 (comment)

http://www.naemon.org/documentation/developer/externalcommands/acknowledge_svc_problem.html

"If the ‘sticky’ option is set to two (2), the acknowledgement will remain until the service returns to an OK state"

This is incorrect in the sense that if you set this option to 1, it's still enabled, and behaves just like if it's a 2.
The correct documentation would be:
"If the ‘sticky’ option is set to anything other than zero (0), the acknowledgement will remain until the service returns to an OK state"