prometheus-operator
config
Our great sponsors
prometheus-operator | config | |
---|---|---|
39 | 32 | |
8,730 | 6,088 | |
1.5% | 0.3% | |
9.7 | 4.5 | |
6 days ago | 6 months ago | |
Go | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
prometheus-operator
-
Smart-Cash project -Adding monitoring to EKS using Prometheus operator
The project repository for Prometheus-operator can be found here, The repo defines the CRDs and the controller. You can follow this documentation for the installation. which will require the creation of metrics exporters, node exporters, scrape configurations, etc.
-
Ask HN: Best solution for homelab service monitoring?
Personally I use kubernetes, k3s is kind of lightweight, with the Prometheus operator.
https://k3s.io/
https://prometheus-operator.dev/
Kubernetes is not for everyone and is far from perfect but you already use Docker and you seem to seek many features offered by Kubernetes.
-
Opinions on using the Prometheus Operator vs. installing yourself?
I see that the operator is a community-run project. Does anybody have any experience (positive or negative) on running the operator itself? I wonder if it is more for multi-tenant Prometheus. For single tenant Prometheus collection, I guess the big gain is abstracting scrape config into ServiceMonitor and PodMonitor resources? Is there anything else that this makes much better?
-
Prometheus node exporter and cadvisor to send metrics to central prometheus cluster
But in all honesty if you’re on k8s you’re probably best served by the Prometheus operator. It’ll give you all that and more, easily.
-
Overcommitted cpu
Try some monitoring.
- What's your favorite monitoring stack?
-
Writing a Kubernetes Operator
It’s a common pattern [1] how else can users override the child objects you’re controller creates?
1 https://github.com/prometheus-operator/prometheus-operator/b...
-
Modify Prometheus rules when installed via Helm chart
The Prometheus operator is this one https://github.com/prometheus-operator/prometheus-operator
-
How do I stop my apps from being killed in k8s?
At a minimum, you want to look at your metrics using the Prometheus Operator. You can write alerts for resource requests.
-
Spring Boot monitoring with Prometheus Operator
Prometheus Operator is an independent project from the Prometheus project. I know, it can lead to confusion. In the official README you can find short comparison. Basically, Prometheus Operator does what an operator should do - provides Kubernetes native deployment and management of Prometheus and related monitoring components like Grafana or Alert Manager.
config
- Hocon (Human-Optimized Config Object Notation)
-
XML is better than YAML
I don‘t understand why HOCON (https://github.com/lightbend/config/blob/main/HOCON.md) isn‘t used more often (at least for configuration use cases). It‘s a superset of JSON, has comments, multiline strings, optional quotes, replacement syntax. We use it at many places, and it‘s as nice at it can get.
- Toml-bench – Which toml package to use in Python?
- slf4j or System.Logger?
- TOML: Tom's Obvious Minimal Language
-
Ron: Rusty Object Notation
HOCON is a great human-readable alternative to JSON. It's a superset of JSON with lots of cool features that make it both more readable and easier to use.
Here's a rundown of HOCON's main features: https://github.com/lightbend/config#features-of-hocon
-
Spring and scala
"Typesafe Config" is the library generally used to read configuration files in HOCON format, which this library introduced. It's commonly used in essentially OOP/imperative Scala contexts, including Akka and its ecosystem.
-
Make systemd better for Podman with Quadlet
Interesting!
For my own servers I use an internal tool that integrates apps with systemd. You point it at the output of your build system and a config file, and it produces a deb that contains systemd unit files and which registers/starts the server on install/reboot/upgrade, as a regular debian package would. Then it uploads it to the server via sftp and installs it using apt, so dependencies are resolved. As part of the build process it can download and bundle language runtimes (I use it with a JVM), it scans native binaries to find packages that the app should depend on, and you can define your config including package metadata like dependencies and systemd units using the HOCON language [1].
Upshot is you can go from a Gradle or Maven build to a running server with a few lines of config. Oh and it can build debs from any OS, so you can push from macOS and Windows too. If your server needs to depend on e.g. Postgres, you just add that dependency in your config and it'll be up and running after the push.
It also has features to turn on DynamicUser and other sandboxing features. I think I'll experiment with socket activation next, and then bundled BorgBackup.
Net/net it's pretty nice. I haven't tried with containers because many language ecosystems don't seem to really need them for many use cases. If your build tool knows how to download your language runtime and bundle it sans container by just setting up paths correctly, then going without means you can rely on your Linux distribution to keep things up to date with security patches in the background, it means networking works as you'd expect (no accidentally opened firewall ports!) and so on. SystemD knows how to configure resource isolation/cgroups and kernel sandboxing, so if you need those you can just write that into your build config and it's done. Or not, as you wish.
With a deployment tool to automate builds/pushes, systemd to supervise processes and a big beefy dedicated machine to let you scale up, I wonder how much value the container part is really still providing if you don't need the full functionality of Kubernetes.
[1] https://github.com/lightbend/config/blob/main/HOCON.md
-
Introducing JXC: An extensible, expressive data language. It's a drop-in replacement for JSON and supports type annotations, numeric suffixes, base64 strings, and more!
Other similar standards: TOML, HOCON
-
Jsonnet is better than YAML for generating JSON
I've also used HOCON pretty extensively for config, and it is better than both YAML and JSON for config with moderate to high complexity.
What are some alternatives?
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
cfg4j - Modern configuration library for distributed apps written in Java.
mimir - Grafana Mimir provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus.
owner - Get rid of the boilerplate code in properties based configuration.
kubernetes-mixin - A set of Grafana dashboards and Prometheus alerts for Kubernetes.
dotenv - Loads environment variables from .env for nodejs projects.
kuberhealthy - A Kubernetes operator for running synthetic checks as pods. Works great with Prometheus!
dotenv - A twelve-factor configuration (12factor.net/config) library for Java 8+
helm-charts - Prometheus community Helm charts
Configur8 - Nano-library which provides the ability to define typesafe (!) configuration templates for applications.
prometheus - The Prometheus monitoring system and time series database.
centraldogma - Highly-available version-controlled service configuration repository based on Git, ZooKeeper and HTTP/2