Silvan Reporter - Revision history

Wikisailor: /* Initial steps */

2026-04-07T16:05:14Z

Initial steps

← Older revision		Revision as of 16:05, 7 April 2026
Line 34:		Line 34:
	\|}		\|}

	The next thing to do was to setup a NFS share for the ~~reporter~~ to communicate		The next thing to do was to setup a NFS share for the Go application to communicate.

Wikisailor: /* Initial steps */

2026-04-07T16:04:28Z

Initial steps

← Older revision		Revision as of 16:04, 7 April 2026
Line 33:		Line 33:
	\|-		\|-
	\|}		\|}

			The next thing to do was to setup a NFS share for the reporter to communicate

Wikisailor: /* Initial steps */

2026-04-07T15:59:22Z

Initial steps

← Older revision		Revision as of 15:59, 7 April 2026
Line 10:		Line 10:

	The first thing that was needed was to install a LXC we chose to use Debian 13 as the basis for the LXC. It was set out shown in the following table.		The first thing that was needed was to install a LXC we chose to use Debian 13 as the basis for the LXC. It was set out shown in the following table.

			{\| class="wikitable"
			\|+ LXC Configuration
			\|-
			!Type!! Value
			\|-
			\| ID\|\| 106
			\|-
			\|Hostname \|\|SilvanReporter
			\|-
			\|IP Address \|\| 192.168.100.50/24
			\|-
			\|CPU\|\| 2 Cores
			\|-
			\|RAM\|\|2GB
			\|-
			\|Swap\|\| None
			\|-
			\|Root disk\|\| 10 gb
			\|-
			\|Privaledged\|\| No
			\|-
			\|}

Wikisailor: /* Initial steps */

2026-04-07T15:46:52Z

Initial steps

← Older revision		Revision as of 15:46, 7 April 2026
Line 9:		Line 9:
	==Initial steps==		==Initial steps==

	The first thing that was needed was to install a LXC we chose to use Debian 13 as the basis for the LXC. It was set as		The first thing that was needed was to install a LXC we chose to use Debian 13 as the basis for the LXC. It was set out shown in the following table.

Wikisailor: /* Outline */

2026-04-07T15:46:23Z

Outline

← Older revision		Revision as of 15:46, 7 April 2026
Line 6:		Line 6:

	The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.		The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.

			==Initial steps==

			The first thing that was needed was to install a LXC we chose to use Debian 13 as the basis for the LXC. It was set as

Wikisailor: /* Introduction */

2026-04-07T15:41:49Z

Introduction

← Older revision		Revision as of 15:41, 7 April 2026
Line 1:		Line 1:
	==Introduction==		==Introduction==

	The ~~Intention~~ of the Silvan Reporter is to generate reports on the current state of the '''[[Home Lab]]'''. The suite will also be able to show the current status of all of the entire network including all of the ~~VMs~~ and all [[Systems & Services \| services]].		The intention of the Silvan Reporter is to generate reports on the current state of the '''[[Home Lab]]'''. The suite will also be able to show the current status of all of the entire network including all of the '''[[Virtual Machines]]''' and all '''[[Systems & Services \| services]]'''.

	==Outline==		==Outline==

	The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.		The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.

Wikisailor: /* Introduction */

2026-04-07T15:32:25Z

Introduction

← Older revision		Revision as of 15:32, 7 April 2026
Line 1:		Line 1:
	==Introduction==		==Introduction==

	The Intention of the Silvan Reporter is to generate reports on the current state of the '''[[Home Lab]]'''. The suite will also be able to show the current status of all of the entire network including all of the VMs and all services.		The Intention of the Silvan Reporter is to generate reports on the current state of the '''[[Home Lab]]'''. The suite will also be able to show the current status of all of the entire network including all of the VMs and all [[Systems & Services \| services]].

	==Outline==		==Outline==

	The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.		The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.

Wikisailor: /* Introduction */

2026-04-07T15:30:46Z

Introduction

← Older revision		Revision as of 15:30, 7 April 2026
Line 1:		Line 1:
	==Introduction==		==Introduction==

	The Intention of the Silvan Reporter is to generate reports on the current state of the ~~Homelab~~. it will also be able to show the current status of all of the entire network.		The Intention of the Silvan Reporter is to generate reports on the current state of the '''[[Home Lab]]'''. The suite will also be able to show the current status of all of the entire network including all of the VMs and all services.

	==Outline==		==Outline==

	The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.		The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.

Wikisailor: Created page with "==Introduction== The Intention of the Silvan Reporter is to generate reports on the current state of the Homelab. it will also be able to show the current status of all of the entire network. ==Outline== The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all o..."

2026-04-07T15:26:57Z

Created page with "==Introduction== The Intention of the Silvan Reporter is to generate reports on the current state of the Homelab. it will also be able to show the current status of all of the entire network. ==Outline== The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all o..."

New page

==Introduction==

The Intention of the Silvan Reporter is to generate reports on the current state of the Homelab. it will also be able to show the current status of all of the entire network.

==Outline==

The outline of the project is to have a LXC on Orchard with a SWI Prolog orchestrator with a Go application that builds a model of the current Silvan network then uses the data from the Victoria metrics / Prometheus application to report on the current status of all of the applications, VMs, LXCs nd hosts. There will be an additional WASM Prolog application that will get the details as presented from the server side Prolog. To avoid direct contact between the two halves of the reporting application suite we will be creating a directory within public_html to write the relevant data so that there can be no security risk or chance of a web application having control of the services inside the hosts.