kdl VS prometheus-operator

IMO, there’s a wide unexplored design space between the minimalism of Lisp and richness of other languages. A programming language inspired by something like KDL (https://github.com/kdl-org/kdl) has the potential to be in a very sweet spot between the two. "Everything is a node" instead of "everything is a list" is only slightly more complicated, but also vastly more readable that a soup of parenthesis.

KDL is a variant of SDLang that’s worth checking out.

https://github.com/kdl-org/kdl

Either way I've got high hopes for KDL becoming the new gold standard for clean, flexible data formats that are editable by hand.

I'd love to understand why all the advertised implementations have permissive licenses except for the Rust implementation, which is released under the Parity Public License 7.0.0 [1]? This seems to be as restrictive as the GPL, no?

In my mind, copyleft licenses applied to infrastructural projects like kdl-rs prematurely limits their adoption and promotes the development of alternatives with more permissive licensing, since the spec is released under a Creative Commons license [2].

[1]: https://github.com/kdl-org/kdl-rs/blob/87f836134c1d901ff5ce6...

[2]: https://github.com/kdl-org/kdl/blob/785abebfc507ff6b7bdeac07...

p.s. if anyone is interested in helping or just wants the info, this is the tracking issue for implementations supporting 1.0 (the actual thing that just got released): https://github.com/kdl-org/kdl/issues/144

Oh nice. It will be a nice library to use to parse KDL (https://github.com/kdl-org/kdl)

It's still in its infancy but I'm keeping an eye on kdl

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.

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.

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?

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.

Try some monitoring.

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...

The Prometheus operator is this one https://github.com/prometheus-operator/prometheus-operator

At a minimum, you want to look at your metrics using the Prometheus Operator. You can write alerts for resource requests.

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.