/explore
|
You are here 
|
vadosware.io | ||
| | | | |
loudwhisper.me
[AI summary] The author implements a minimal, privacy-focused web analytics system for their blog using Traefik logs, Vector as a forwarder, and Openobserve as a log aggregator in a Kubernetes environment, all without JavaScript. |
|
| | | | | ||
| | | | |
arveknudsen.com
In my previous blog post I showed how to use the Kops tool to create a production ready Kubernetes cluster on Amazon Web Services (AWS). In this follow-up post I will show how to install Elasticsearch and its graphical counterpart Kibana in the cluster, in order to be able to collect and store logs from your cluster and search/read them. We will also install Fluentd as this component is responsible for transmitting the standard Kubernetes logs to Elasticsearch. This is generally known as the ELK stack, which stands for Elasticsearch, Logstash (precursor to Fluentd) and Kibana. |
|
| | | | | ||
| | | | |
kndrck.co
Prelude I've been trying to find a quick and easy example on how to setup application metrics logging on kubernetes using prometheus and grafana, from someone with minimal kubernetes experience. However after scouring the web, the examples I could find had lots of assumed knowledge on how kubernetes and its tooling worked, or just overly verbose. This article is more for me as a reference guide on how to setup application monitoring in Kubernetes using prometheus, and grafana with the help of Helm on EKS. |
|
| | | | | ||
| | | | |
questdb.com
How to monitor a QuestDB instance using Loki and Prometheus |
|
| | | |||
