Prometheus & Grafana - Revision history

Wikisailor: /* Introduction */

2026-02-24T00:12:51Z

Introduction

← Older revision		Revision as of 00:12, 24 February 2026
Line 2:		Line 2:

	It has been decided that it would be better if we had some detailed knowledge of what is happening with the '''[[Virtual Machines]]''' and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[Granadilla]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.		It has been decided that it would be better if we had some detailed knowledge of what is happening with the '''[[Virtual Machines]]''' and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[Granadilla]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.

			=='''[[Unified Monitoring Stack]]'''==

			The '''[[Unified Monitoring Stack]]''' has now superseded the separate VMs that performed the Prometheus & Grafana roles and should be used instead. These pages will be left for reference but will not be updated so that all of the Performance monitoring will be undertaken by the '''[[Unified Monitoring Stack]]''' including the Victoria Metrics and storage of the historical data.

	==Setup and Installation==		==Setup and Installation==

Wikisailor: /* Introduction */

2026-01-27T14:50:46Z

Introduction

← Older revision		Revision as of 14:50, 27 January 2026
Line 1:		Line 1:
	==Introduction==		==Introduction==

	It has been decided that it would be better if we had some detailed knowledge of what is happening with the ~~VMs~~ and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[Granadilla]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.		It has been decided that it would be better if we had some detailed knowledge of what is happening with the '''[[Virtual Machines]]''' and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[Granadilla]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.


	==Setup and Installation==		==Setup and Installation==

Wikisailor: /* Introduction */

2025-06-05T10:04:29Z

Introduction

← Older revision		Revision as of 10:04, 5 June 2025
Line 2:		Line 2:

	It has been decided that it would be better if we had some detailed knowledge of what is happening with the VMs and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[Granadilla]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.		It has been decided that it would be better if we had some detailed knowledge of what is happening with the VMs and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[Granadilla]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.


			==Setup and Installation==

			It seemed logical to install Prometheus & Grafana at the same time as they are both required to be meaningful but they are two separate hosts so the details will be listed separately. '''[[Victoria Metrics]]''' is not actually required to make monitoring possible but it is a useful addition to the setup and it's installation is covered in a different heading in the Infra network's hosts.

			===Prometheus===
			'''[[Pineapple \| Prometheus install]]''' consists of installing the rule processing and it's supporting functions part of the suite on '''[[Pineapple]]''' followed by the lengthy installation of the agents that supply the data from each individual client. A more detailed step by step guide can be found '''[[Pineapple \| here]]'''.

			===Grafana===
			'''[[Granadilla \| Grafana install]]''' consist of installing the webserver on '''[[Granadilla]]''' and collecting the data to be viewed. further details can be found '''[[Granadilla \| here]]'''.

	==Prometheus==		==Prometheus==

Wikisailor: /* Setup and Installation */

2025-06-05T10:04:05Z

Setup and Installation

← Older revision		Revision as of 10:04, 5 June 2025
Line 72:		Line 72:
	Leveraging '''[[Victoria Metrics]]''' through Prometheus: While Grafana directly queries Prometheus, Prometheus itself is configured to remotely write its data to '''[[Victoria Metrics \| Victoria (Victoria)]]''' for long-term storage. This means that when Grafana requests historical data (e.g., performance trends from weeks or months ago), Prometheus on pineapple will efficiently retrieve that data from VictoriaMetrics on '''[[Victoria Metrics \| Victoria]]''' and then serve it back to Grafana. This architecture ensures that Grafana can access both recent and deep historical data seamlessly without needing to manage the complexities of long-term storage itself.		Leveraging '''[[Victoria Metrics]]''' through Prometheus: While Grafana directly queries Prometheus, Prometheus itself is configured to remotely write its data to '''[[Victoria Metrics \| Victoria (Victoria)]]''' for long-term storage. This means that when Grafana requests historical data (e.g., performance trends from weeks or months ago), Prometheus on pineapple will efficiently retrieve that data from VictoriaMetrics on '''[[Victoria Metrics \| Victoria]]''' and then serve it back to Grafana. This architecture ensures that Grafana can access both recent and deep historical data seamlessly without needing to manage the complexities of long-term storage itself.
	In essence, Grafana on '''[[Granadilla]]''' is the window into the operational state of our entire home lab. It translates the raw numbers from Prometheus into intuitive charts and graphs, enabling us to quickly understand performance trends, diagnose issues, and ensure the stability of all our services and infrastructure. Its flexible visualization capabilities complement Prometheus's robust data collection and VictoriaMetrics' scalable storage, forming a powerful monitoring triumvirate.		In essence, Grafana on '''[[Granadilla]]''' is the window into the operational state of our entire home lab. It translates the raw numbers from Prometheus into intuitive charts and graphs, enabling us to quickly understand performance trends, diagnose issues, and ensure the stability of all our services and infrastructure. Its flexible visualization capabilities complement Prometheus's robust data collection and VictoriaMetrics' scalable storage, forming a powerful monitoring triumvirate.

	~~==Setup and Installation==~~

	It seemed logical to install Prometheus & Grafana at the same time as they are both required to be meaningful but they are two separate hosts so the details will be listed separately. '''[[Victoria Metrics]]''' is not actually required to make monitoring possible but it is a useful addition to the setup and it's installation is covered in a different heading in the Infra network's hosts.

	~~===Prometheus===~~
	'''[[Pineapple \| Prometheus install]]''' consists of installing the rule processing and it's supporting functions part of the suite on '''[[Pineapple]]''' followed by the lengthy installation of the agents that supply the data from each individual client. A more detailed step by step guide can be found '''[[Pineapple \| here]]'''.

	~~===Grafana===~~
	~~'''[[Granadilla \| Grafana install]]''' consist of installing the webserver on '''[[Granadilla]]''' and collecting the data to be viewed. further details can be found '''[[Granadilla \| here]]'''.~~

Wikisailor: /* Setup and Installation */

2025-06-05T10:03:37Z

Setup and Installation

← Older revision		Revision as of 10:03, 5 June 2025
Line 73:		Line 73:
	In essence, Grafana on '''[[Granadilla]]''' is the window into the operational state of our entire home lab. It translates the raw numbers from Prometheus into intuitive charts and graphs, enabling us to quickly understand performance trends, diagnose issues, and ensure the stability of all our services and infrastructure. Its flexible visualization capabilities complement Prometheus's robust data collection and VictoriaMetrics' scalable storage, forming a powerful monitoring triumvirate.		In essence, Grafana on '''[[Granadilla]]''' is the window into the operational state of our entire home lab. It translates the raw numbers from Prometheus into intuitive charts and graphs, enabling us to quickly understand performance trends, diagnose issues, and ensure the stability of all our services and infrastructure. Its flexible visualization capabilities complement Prometheus's robust data collection and VictoriaMetrics' scalable storage, forming a powerful monitoring triumvirate.

	===Setup and Installation===		==Setup and Installation==

	It seemed logical to install Prometheus & Grafana at the same time as they are both required to be meaningful but they are two separate hosts so the details will be listed separately. '''[[Victoria Metrics]]''' is not actually required to make monitoring possible but it is a useful addition to the setup and it's installation is covered in a different heading in the Infra network's hosts.		It seemed logical to install Prometheus & Grafana at the same time as they are both required to be meaningful but they are two separate hosts so the details will be listed separately. '''[[Victoria Metrics]]''' is not actually required to make monitoring possible but it is a useful addition to the setup and it's installation is covered in a different heading in the Infra network's hosts.

Wikisailor: /* Setup and Installation */

2025-06-05T10:03:04Z

Setup and Installation

← Older revision		Revision as of 10:03, 5 June 2025
Line 73:		Line 73:
	In essence, Grafana on '''[[Granadilla]]''' is the window into the operational state of our entire home lab. It translates the raw numbers from Prometheus into intuitive charts and graphs, enabling us to quickly understand performance trends, diagnose issues, and ensure the stability of all our services and infrastructure. Its flexible visualization capabilities complement Prometheus's robust data collection and VictoriaMetrics' scalable storage, forming a powerful monitoring triumvirate.		In essence, Grafana on '''[[Granadilla]]''' is the window into the operational state of our entire home lab. It translates the raw numbers from Prometheus into intuitive charts and graphs, enabling us to quickly understand performance trends, diagnose issues, and ensure the stability of all our services and infrastructure. Its flexible visualization capabilities complement Prometheus's robust data collection and VictoriaMetrics' scalable storage, forming a powerful monitoring triumvirate.

	==Setup and Installation==		===Setup and Installation===

	It seemed logical to install Prometheus & Grafana at the same time as they are both required to be meaningful but they are two separate hosts so the details will be listed separately. '''[[Victoria Metrics]]''' is not actually required to make monitoring possible but it is a useful addition to the setup and it's installation is covered in a different heading in the Infra network's hosts.		It seemed logical to install Prometheus & Grafana at the same time as they are both required to be meaningful but they are two separate hosts so the details will be listed separately. '''[[Victoria Metrics]]''' is not actually required to make monitoring possible but it is a useful addition to the setup and it's installation is covered in a different heading in the Infra network's hosts.

Wikisailor: /* Introduction */

2025-06-04T13:45:21Z

Introduction

← Older revision		Revision as of 13:45, 4 June 2025
Line 1:		Line 1:
	==Introduction==		==Introduction==

	It has been decided that it would be better if we had some detailed knowledge of what is happening with the VMs and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[~~Grandilla~~]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.		It has been decided that it would be better if we had some detailed knowledge of what is happening with the VMs and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[Granadilla]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.

	==Prometheus==		==Prometheus==

Wikisailor: /* Introduction */

2025-06-04T13:44:25Z

Introduction

← Older revision		Revision as of 13:44, 4 June 2025
Line 1:		Line 1:
	==Introduction==		==Introduction==

	It has been decided that it would be better if we had some detailed knowledge of what is happening with the VMs and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of ~~the~~ Pear ~~suite~~.		It has been decided that it would be better if we had some detailed knowledge of what is happening with the VMs and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus on '''[[Pineapple]]'''. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed on to '''[[Grandilla]]''', also on the Infra network. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of Pear and it's collection of VMs and CTs.

	==Prometheus==		==Prometheus==

Wikisailor: /* Introduction */

2025-06-04T13:40:43Z

Introduction

← Older revision		Revision as of 13:40, 4 June 2025
Line 1:		Line 1:
	==Introduction==		==Introduction==

	It has been decided that it would be better if we had some detailed knowledge of what is happening with the VMs and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus ~~and as~~ Prometheus does not do justice to the data that it collects Grafana has also been installed~~, further long~~ term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of the Pear suite.		It has been decided that it would be better if we had some detailed knowledge of what is happening with the VMs and indeed on the host Pear as well. The Proxmox GUI does give an approximation of what the state of resources are on the Host and VMs but it does seem to be a bit vague and out of date. It is with the Proxmox lack of detail that prompted the installation of Prometheus. However, Prometheus does not do justice to the data that it collects so Grafana has also been installed. Long term data storage requires some thing like Victoria Metrics is needed. So what started out to be a simple data collection issue ended with a suite of VMs to gather, store and view the metrics of the Pear suite.

	==Prometheus==		==Prometheus==

Wikisailor: /* Data Flow and Integration with Prometheus and VictoriaMetrics */

2025-06-04T13:22:55Z

Data Flow and Integration with Prometheus and VictoriaMetrics

← Older revision		Revision as of 13:22, 4 June 2025
Line 70:		Line 70:

	* Primary Data Source: Prometheus (pineapple): Grafana is primarily configured to use Prometheus (running on pineapple) as its data source. When a dashboard is loaded, Grafana sends PromQL queries directly to the Prometheus API endpoint on pineapple.		* Primary Data Source: Prometheus (pineapple): Grafana is primarily configured to use Prometheus (running on pineapple) as its data source. When a dashboard is loaded, Grafana sends PromQL queries directly to the Prometheus API endpoint on pineapple.
	Leveraging '''[[Victoria Metrics ~~\| Victoria (Victoria)~~]]''' through Prometheus: While Grafana directly queries Prometheus, Prometheus itself is configured to remotely write its data to '''[[Victoria Metrics \| Victoria (Victoria)]]''' for long-term storage. This means that when Grafana requests historical data (e.g., performance trends from weeks or months ago), Prometheus on pineapple will efficiently retrieve that data from VictoriaMetrics on '''[[Victoria Metrics \| Victoria]]''' and then serve it back to Grafana. This architecture ensures that Grafana can access both recent and deep historical data seamlessly without needing to manage the complexities of long-term storage itself.		Leveraging '''[[Victoria Metrics]]''' through Prometheus: While Grafana directly queries Prometheus, Prometheus itself is configured to remotely write its data to '''[[Victoria Metrics \| Victoria (Victoria)]]''' for long-term storage. This means that when Grafana requests historical data (e.g., performance trends from weeks or months ago), Prometheus on pineapple will efficiently retrieve that data from VictoriaMetrics on '''[[Victoria Metrics \| Victoria]]''' and then serve it back to Grafana. This architecture ensures that Grafana can access both recent and deep historical data seamlessly without needing to manage the complexities of long-term storage itself.
	In essence, Grafana on '''[[Granadilla]]''' is the window into the operational state of our entire home lab. It translates the raw numbers from Prometheus into intuitive charts and graphs, enabling us to quickly understand performance trends, diagnose issues, and ensure the stability of all our services and infrastructure. Its flexible visualization capabilities complement Prometheus's robust data collection and VictoriaMetrics' scalable storage, forming a powerful monitoring triumvirate.		In essence, Grafana on '''[[Granadilla]]''' is the window into the operational state of our entire home lab. It translates the raw numbers from Prometheus into intuitive charts and graphs, enabling us to quickly understand performance trends, diagnose issues, and ensure the stability of all our services and infrastructure. Its flexible visualization capabilities complement Prometheus's robust data collection and VictoriaMetrics' scalable storage, forming a powerful monitoring triumvirate.