Skip to main content

HTTP endpoint monitoring with Netdata

This module monitors one or more http servers availability and response time.

Charts#

It produces the following charts:

  • HTTP Response Time in ms
  • HTTP Check Status in boolean
  • HTTP Current State Duration in seconds
  • HTTP Response Body Length in characters

Check statuses#

StatusDescription
successNo error on HTTP request, body reading and body content checking
timeoutTimeout error on HTTP request
bad contentThe body of the response didn't match the regex (only if response_match option is set)
bad statusResponse status code not in status_accepted
no connectionAny other network error not specifically handled by the module

Configuration#

Edit the go.d/httpcheck.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/httpcheck.conf

Here is an example for 2 servers:

jobs:
- name: cool_website1
url: http://cool.website1:8080/home
- name: cool_website2
url: http://cool.website2:8080/home
status_accepted:
- 200
- 201
- 202
response_match: <title>My cool website!<\/title>

For all available options please see module configuration file.

Troubleshooting#

To troubleshoot issues with the httpcheck collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.

cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s

You can now run the go.d.plugin to debug the collector:

./go.d.plugin -d -m httpcheck

Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.

Documentation

Community

Last updated on