Custom Monitoring Stack - Revision history

Admin at 21:18, 4 February 2026

2026-02-04T21:18:02Z

← Older revision		Revision as of 21:18, 4 February 2026
Line 1:		Line 1:
	= About Custom Monitoring Stack =		= About Custom Monitoring Stack =

	'''A lightweight, Prometheus-native monitoring system designed for small environments:'''		'''A lightweight, Prometheus-native monitoring system designed for small environments'''<br><br>
			'''Highlights:'''
	* '''Quick to set up''' – requires little more than a Prometheus container		* '''Quick to set up''' – requires little more than a Prometheus container or a local Python Setup
	* '''Custom exporter mode''' – exposes metrics in native Prometheus format		* '''Custom exporter mode''' – exposes metrics in native Prometheus format
	* '''Extensible plugin framework''' – simple, stateless checks (ping, port, process, http, cert)		* '''Extensible plugin framework''' – simple, stateless checks (ping, port, process, http, cert)
Line 47:		Line 47:
	----		----

	==== A: Direct ~~Execution~~ via ~~System Scheduler~~ (e.g. crontab) ====		==== A: Direct execution via system scheduler (e.g. crontab) ====

	In this model, plugins are executed directly by the ~~local~~ system scheduler,		In this model, plugins are executed directly by the system scheduler.
	~~typically via~~ crontab. ~~No Scheduler or JobRunner components are involved~~.		In this way the local system crontab is in use.
			<br>[[image:Custom-setup01.png]]<br><br>

	[[image:Custom-~~setup01~~.png]]		Check Plugins are also able to write from remote hosts via the network to the Custom-Exporter
			<br><br>[[image:Custom-exporter01a.png]]<br>

	~~In addition, check_plugins are capable of sending metric payloads directly~~
	~~to the Custom Exporter over the network from remote hosts.~~

	~~This capability is provided to demonstrate plugin flexibility and is not~~
	~~intended as the primary or recommended execution model.~~

	~~[[image:Custom-exporter01a.png]]~~

	Typical use cases:		Typical use cases:
			* Simple hosts
	* Simple ~~or standalone~~ hosts
	* Minimal dependencies		* Minimal dependencies
	* One-off, legacy~~, or transitional~~ checks		* One-off or legacy checks

	----		----
Line 82:		Line 76:
	----		----

	==== C: Remote ~~Execution Using~~ Scheduler and JobRunner ====		==== C: Remote execution using Scheduler and JobRunner ====

	~~In this model, the Custom Scheduler coordinates execution and dispatches~~
	~~requests to one or more JobRunner instances. The JobRunner executes plugins~~
	~~on remote hosts and returns the results to the Scheduler for evaluation.~~

	~~After processing the results~~, the ~~Custom~~ Scheduler ~~forwards metric payloads~~		In this model, the Scheduler coordinates execution and sends requests to the
	to the ~~Custom Exporter~~. The ~~Custom Exporter is not part of~~ the ~~execution chain~~		JobRunner. The JobRunner executes plugins on remote hosts and returns the
	~~and operates independently from plugin execution~~.		results back to the Scheduler.

	~~[[image:~~Custom-~~setup03~~.~~png]]~~		The Custom-Scheduler then forwards metric payloads to the Custom-Exporter.
			The Custom-Exporter is not part of the execution chain and operates independently.

	~~The following diagram illustrates an alternative execution capability where~~		<br>[[image:Custom-setup03.png]]<br>
	~~check_plugins can write metrics directly to the~~ Custom ~~Exporter over the network~~.

	~~This mode exists to demonstrate plugin capabilities~~ only ~~and is not intended~~		Another sample which is a bit odd and should only display the capabilties of
	as the ~~preferred or recommended execution model~~.		the check_plugins as they can write dierectly to the custom exporter via network.

	[[image:Custom-setup3a.png]]		<br>[[image:Custom-setup3a.png]]<br>

	=== Combined Local and Remote Execution ===		=== Combined Local and Remote Execution ===
Line 215:		Line 205:

	If the custom exporter is exposed beyond localhost or a trusted internal network,		If the custom exporter is exposed beyond localhost or a trusted internal network,
	it must be placed behind a reverse proxy such as nginx.		it '''must''' be placed behind a reverse proxy such as nginx.

	Direct internet exposure of the custom exporter service is discouraged.		Direct internet exposure of the custom exporter service is discouraged.
Line 234:		Line 224:
	=== Custom Exporter Startup Arguments ===		=== Custom Exporter Startup Arguments ===

	The custom exporter is configured exclusively via command-line arguments.		The custom exporter is configured '''exclusively via command-line arguments'''.
	There is no static configuration file.		There is no static configuration file.

Admin: /* A: Direct execution via system scheduler (e.g. crontab) */

2026-01-03T21:09:11Z

A: Direct execution via system scheduler (e.g. crontab)

← Older revision		Revision as of 21:09, 3 January 2026
Line 47:		Line 47:
	----		----

	==== A: Direct ~~execution~~ via ~~system scheduler~~ (e.g. crontab) ====		==== A: Direct Execution via System Scheduler (e.g. crontab) ====

	In this model, plugins are executed directly by the system scheduler.		In this model, plugins are executed directly by the local system scheduler,
	~~In this way the local system~~ crontab ~~is in use~~.		typically via crontab. No Scheduler or JobRunner components are involved.
	~~<br>[[image:Custom-setup01~~.~~png]]<br><br>~~

	~~Check Plugins are also able to write from remote hosts via the network to the Custom-Exporter~~		[[image:Custom-setup01.png]]
	~~<br><br>~~[[image:Custom-~~exporter01a~~.png]]~~<br>~~

			In addition, check_plugins are capable of sending metric payloads directly
			to the Custom Exporter over the network from remote hosts.

			This capability is provided to demonstrate plugin flexibility and is not
			intended as the primary or recommended execution model.

			[[image:Custom-exporter01a.png]]

	Typical use cases:		Typical use cases:
	* Simple hosts
			* Simple or standalone hosts
	* Minimal dependencies		* Minimal dependencies
	* One-off or ~~legacy~~ checks		* One-off, legacy, or transitional checks

	----		----

Admin: /* C: Remote execution using Scheduler and JobRunner */

2026-01-03T21:06:33Z

C: Remote execution using Scheduler and JobRunner

← Older revision		Revision as of 21:06, 3 January 2026
Line 76:		Line 76:
	----		----

	==== C: Remote ~~execution using~~ Scheduler and JobRunner ====		==== C: Remote Execution Using Scheduler and JobRunner ====

	In this model, the Scheduler coordinates execution and ~~sends~~ requests to ~~the~~		In this model, the Custom Scheduler coordinates execution and dispatches
	JobRunner. The JobRunner executes plugins on remote hosts and returns the		requests to one or more JobRunner instances. The JobRunner executes plugins
	results ~~back~~ to the Scheduler.		on remote hosts and returns the results to the Scheduler for evaluation.

	~~The~~ Custom-Scheduler ~~then~~ forwards metric payloads to the Custom-Exporter.		After processing the results, the Custom Scheduler forwards metric payloads
	The Custom-Exporter is not part of the execution chain and operates independently.		to the Custom Exporter. The Custom Exporter is not part of the execution chain
			and operates independently from plugin execution.

	~~<br>~~[[image:Custom-setup03.png]]~~<br>~~		[[image:Custom-setup03.png]]

	~~Another sample which is a bit odd and should only display the capabilties of~~		The following diagram illustrates an alternative execution capability where
	~~the~~ check_plugins ~~as they~~ can write ~~dierectly~~ to the ~~custom exporter via~~ network.		check_plugins can write metrics directly to the Custom Exporter over the network.

	~~<br>~~[[image:Custom-setup3a.png]]~~<br>~~		This mode exists to demonstrate plugin capabilities only and is not intended
			as the preferred or recommended execution model.

			[[image:Custom-setup3a.png]]

	=== Combined Local and Remote Execution ===		=== Combined Local and Remote Execution ===

Admin at 21:00, 3 January 2026

2026-01-03T21:00:58Z

← Older revision		Revision as of 21:00, 3 January 2026
Line 1:		Line 1:
	= Custom Monitoring Stack =		= About Custom Monitoring Stack =
	~~'''<br/>A lightweight Prometheus-native monitoring system with a custom exporter,<br/>'''~~
	~~'''a custom plugin framework, a highly flexible custom scheduler for local and remote execution,<br/>'''~~
	~~'''and a minimal custom job runner for remote plugin execution'''~~

			'''A lightweight, Prometheus-native monitoring system designed for small environments:'''

			* '''Quick to set up''' – requires little more than a Prometheus container
			* '''Custom exporter mode''' – exposes metrics in native Prometheus format
			* '''Extensible plugin framework''' – simple, stateless checks (ping, port, process, http, cert)
			* '''Highly flexible custom scheduler''' – orchestrates both local and remote plugin execution
			* '''Minimal custom job runner''' – executes plugins remotely on behalf of the scheduler
			* '''Grafana-ready by design''' – dashboards and alerting via Grafana and Grafana Alertmanager follow standard Prometheus workflows
			* '''Mobile-friendly interface''' – optional mobile phone app available, view integrated with Grafana Alertmanager for basic alert monitoring and management
	<p></p>		<p></p>

Line 88:		Line 94:
	=== Combined Local and Remote Execution ===		=== Combined Local and Remote Execution ===

	~~Remote~~ execution ~~using JobRunner is not mutually exclusive with local~~		'''The preferred execution model.'''
	~~execution using the Scheduler~~.

	~~A single~~ Scheduler ~~instance may:~~		As illustrated in the diagram below, the Custom Scheduler acts as the central
			execution authority between local plugins, remote JobRunner instances,
			and the Prometheus Custom Exporter.

	* Execute some checks locally on the same host		<br/>[[image:Custom-setup04a.png]]<br/><br/>
	* Execute other checks remotely via one or more JobRunner instances

	~~<br>[[image~~:~~Custom-setup04a.png]]<br>~~		A single Scheduler instance can:

			* Execute selected checks locally or via remote
			* Dispatch other checks to one or more remote JobRunner instances
			* Collect and evaluate all plugin results centrally
			* Forward processed results to the Custom Exporter only after evaluation

	~~This allows mixed deployments where local services~~ are ~~checked directly~~,		Local and remote execution paths are selected per check by scheduler
	~~while remote or restricted hosts are checked via JobRunner~~.		configuration, not by a global operating mode.

	~~The execution method is selected per check based on scheduler configuration~~,		This enables mixed deployments where local services are checked directly,
	~~not as a global operating mode~~.		while remote, firewalled, or restricted hosts are monitored via JobRunner,
			without duplicating exporters or schedulers.

	=== Key characteristics ===		=== Key characteristics ===
Line 111:		Line 122:
	* Upward flow represents returned plugin results		* Upward flow represents returned plugin results
	* Custom-Scheduler receives and evaluates results		* Custom-Scheduler receives and evaluates results
	* Custom-Exporter is triggered only after ~~results are processed~~		* Custom-Exporter is triggered only after result processing
	* No direct plugin-to-exporter communication		* No direct plugin-to-exporter communication

	Typical use cases:		Typical use cases:

	* Remote hosts		* Remote hosts
	* No SSH access		* Environments without SSH access
	* Firewalled or segmented ~~environments~~		* Firewalled or segmented networks
	* Centralized orchestration		* Centralized orchestration

Admin at 20:07, 3 January 2026

2026-01-03T20:07:57Z

← Older revision		Revision as of 20:07, 3 January 2026
Line 1:		Line 1:
	= Custom Monitoring Stack =		= Custom Monitoring Stack =
	''~~Modular~~ monitoring with exporter, ~~plugins~~, ~~jobrunner~~ and ~~scheduler bases on the Prometheus Architecture~~''		'''<br/>A lightweight Prometheus-native monitoring system with a custom exporter,<br/>'''
			'''a custom plugin framework, a highly flexible custom scheduler for local and remote execution,<br/>'''
			'''and a minimal custom job runner for remote plugin execution'''

			<p></p>


	__TOC__		__TOC__
Line 11:		Line 16:
	! Component !! Purpose		! Component !! Purpose
	\|-		\|-
	\| Exporter \|\| Receives metrics and exposes Prometheus format		\| Custom-Exporter \|\| Receives metrics and exposes Prometheus format
	\|-		\|-
	\| Plugins \|\| Perform individual checks (ping, port, HTTP, cert, process)		\| Plugins \|\| Perform individual checks (ping, port, HTTP, cert, process)
	\|-		\|-
	\| JobRunner (optional) \|\| Executes plugins remotely via HTTP		\| Custom-JobRunner (optional) \|\| Executes plugins remotely via HTTP
	\|-		\|-
	\| Scheduler (optional) \|\| Orchestrates execution and intervals		\| Custom-Scheduler (optional) \|\| Orchestrates execution and intervals
	\|}		\|}

Line 39:		Line 44:

	In this model, plugins are executed directly by the system scheduler.		In this model, plugins are executed directly by the system scheduler.
	~~No scheduler daemon or remote execution~~ is ~~involved~~.		In this way the local system crontab is in use.
	<br>[[image:Custom-setup01.png]]<br><br>		<br>[[image:Custom-setup01.png]]<br><br>

	Check Plugins are able to write from remote hosts via the network to the ~~exporter~~		Check Plugins are also able to write from remote hosts via the network to the Custom-Exporter
	<br><br>[[image:Custom-exporter01a.png]]<br>		<br><br>[[image:Custom-exporter01a.png]]<br>

Line 55:		Line 60:
	==== B: Local execution using the Scheduler ====		==== B: Local execution using the Scheduler ====

	The Scheduler runs locally and executes plugins directly on the same system.		The Scheduler runs and orchestors locally and executes plugins directly on the same system.
	<br>[[image:Custom-setup02.png]]<br>		<br>[[image:Custom-setup02.png]]<br>

Line 71:		Line 76:
	results back to the Scheduler.		results back to the Scheduler.

	The Scheduler then forwards metric payloads to the Exporter.		The Custom-Scheduler then forwards metric payloads to the Custom-Exporter.
	The Exporter is not part of the execution chain and operates independently.		The Custom-Exporter is not part of the execution chain and operates independently.

	<br>[[image:Custom-setup03.png]]<br>		<br>[[image:Custom-setup03.png]]<br>
Line 91:		Line 96:
	* Execute other checks remotely via one or more JobRunner instances		* Execute other checks remotely via one or more JobRunner instances

	<br>[[image:Custom-~~setup04~~.png]]<br>		<br>[[image:Custom-setup04a.png]]<br>


Line 105:		Line 110:
	* Downward flow represents execution requests		* Downward flow represents execution requests
	* Upward flow represents returned plugin results		* Upward flow represents returned plugin results
	* Scheduler receives and evaluates results		* Custom-Scheduler receives and evaluates results
	* Exporter is triggered only after results are processed		* Custom-Exporter is triggered only after results are processed
	* No direct plugin-to-exporter communication		* No direct plugin-to-exporter communication

Line 117:		Line 122:
	----		----

	== Exporter ==		== Custom-Exporter ==

	=== Purpose ===		=== Purpose ===
Line 187:		Line 192:
	=== Security and Exposure ===		=== Security and Exposure ===

	If the exporter is exposed beyond localhost or a trusted internal network,		If the custom exporter is exposed beyond localhost or a trusted internal network,
	it must be placed behind a reverse proxy such as nginx.		it must be placed behind a reverse proxy such as nginx.

	Direct internet exposure of the exporter service is discouraged.		Direct internet exposure of the custom exporter service is discouraged.

	The reverse proxy is responsible for:		The reverse proxy is responsible for:
Line 200:		Line 205:
	* Request size limits		* Request size limits

	The exporter itself intentionally remains simple and does not replace		The custom exporter itself intentionally remains simple and does not replace
	an edge security layer.		an edge security layer.

	----		----

	=== Exporter Startup Arguments ===		=== Custom Exporter Startup Arguments ===

	The exporter is configured exclusively via command-line arguments.		The custom exporter is configured exclusively via command-line arguments.
	There is no static configuration file.		There is no static configuration file.

Line 321:		Line 326:
	----		----

	== JobRunner (Optional) ==		== Custom JobRunner (Optional) ==

	=== Purpose ===		=== Purpose ===
Line 380:		Line 385:
	----		----

	== Scheduler (Optional) ==		== Custom Scheduler (Optional) ==

	=== Purpose ===		=== Purpose ===
Line 448:		Line 453:
	----		----

	=== Exporter ===		=== Custom Exporter ===

	<pre>		<pre>

Admin: /* A: Direct execution via system scheduler (e.g. crontab) */

2026-01-03T19:07:32Z

A: Direct execution via system scheduler (e.g. crontab)

← Older revision		Revision as of 19:07, 3 January 2026
Line 42:		Line 42:
	<br>[[image:Custom-setup01.png]]<br><br>		<br>[[image:Custom-setup01.png]]<br><br>

	Check Plugins are able to write from ~~host~~ via the network to the exporter		Check Plugins are able to write from remote hosts via the network to the exporter
	<br><br>[[image:Custom-exporter01a.png]]<br>		<br><br>[[image:Custom-exporter01a.png]]<br>

Admin: /* Combined Local and Remote Execution */

2026-01-03T19:00:19Z

Combined Local and Remote Execution

← Older revision		Revision as of 19:00, 3 January 2026
Line 90:		Line 90:
	* Execute some checks locally on the same host		* Execute some checks locally on the same host
	* Execute other checks remotely via one or more JobRunner instances		* Execute other checks remotely via one or more JobRunner instances

			<br>[[image:Custom-setup04.png]]<br>


	This allows mixed deployments where local services are checked directly,		This allows mixed deployments where local services are checked directly,

Admin: /* A: Direct execution via system scheduler (e.g. crontab) */

2026-01-03T18:57:45Z

A: Direct execution via system scheduler (e.g. crontab)

← Older revision		Revision as of 18:57, 3 January 2026
Line 40:		Line 40:
	In this model, plugins are executed directly by the system scheduler.		In this model, plugins are executed directly by the system scheduler.
	No scheduler daemon or remote execution is involved.		No scheduler daemon or remote execution is involved.
	<br>[[image:Custom-setup01.png]]<br>		<br>[[image:Custom-setup01.png]]<br><br>

			Check Plugins are able to write from host via the network to the exporter
			<br><br>[[image:Custom-exporter01a.png]]<br>


	Typical use cases:		Typical use cases:

Admin: /* C: Remote execution using Scheduler and JobRunner */

2026-01-03T18:36:05Z

C: Remote execution using Scheduler and JobRunner

← Older revision		Revision as of 18:36, 3 January 2026
Line 75:		Line 75:
	the check_plugins as they can write dierectly to the custom exporter via network.		the check_plugins as they can write dierectly to the custom exporter via network.

	<br>[[image:Custom-~~setup03a~~.png]]<br>		<br>[[image:Custom-setup3a.png]]<br>

	=== Combined Local and Remote Execution ===		=== Combined Local and Remote Execution ===

Admin: /* C: Remote execution using Scheduler and JobRunner */

2026-01-03T18:35:45Z

C: Remote execution using Scheduler and JobRunner

← Older revision		Revision as of 18:35, 3 January 2026
Line 71:		Line 71:

	<br>[[image:Custom-setup03.png]]<br>		<br>[[image:Custom-setup03.png]]<br>

			Another sample which is a bit odd and should only display the capabilties of
			the check_plugins as they can write dierectly to the custom exporter via network.

			<br>[[image:Custom-setup03a.png]]<br>

	=== Combined Local and Remote Execution ===		=== Combined Local and Remote Execution ===