Providing visibility into the server's goings on


These notes provide information on how to monitor the server for both usual and unusual communication patterns.


Real time monitoring with simple counters

This note describes the counter module, how to enable it, how to retrieve real-time server statistics, its limitations, and security implications.
RWSERVE, counters module, method, user-agent, content-type, content-length, status-code, logging, router, RBAC, devops, real-time insight, website traffic

Custom Errors

Helping the user to understand what went wrong

This note describes how to configure the server to show custom error messages when an HTTP request fails.
custom-errors, status codes, GRAVE-ACCENT, 404

Information Headers

Adding helpful context to the response

This note describes the information-headers module and how it can provide contextual information to make standard HTTP status codes more meaningful.
information header, status codes, troubleshoot, content, rw- prefix, V1, V2


Monitoring and capturing what's going on

This note describes the options available for fine-grain control over the server's logging operations.
logging, systemd, config, request, staging, information, response, error, filtering, abbreviations, formatting

Status Codes

Explaining the conditions that trigger status codes

An explanation of what conditions trigger each status code in an HTTP/2 response.
status codes, http2, OK, created, no content, partial content, found, see other, not modified, bad request, forbidden, not found, method not allowed, not acceptable, conflict, length required, precondition failes, URI too long, unsuppoerted media type, range not satisfiable, internal server error, not implemented

Providing visibility into the server's goings on

🔗 🔎