Discussion
Coffee wasn't strong enough, so I'm doing easy stuff today.
Error: × Failed to interpret etc/iocaine.kdl
├─▶ Failed to evaluate `initial-seed`
├─▶ Failed to evaluate `seed`
╰─▶ argument `seed` (at position #0) is of wrong type
╭─[6:14]
5 │
6 │ initial-seed 4
· ┬
· ╰── here
7 │ state-directory ""
╰────
help: `initial-seed` requires the `seed` argument (at position #0) to be of string type
I was thinking... what if I merged the metrics persistences into a single file, and had all state in said file?
No need to configure metrics persistence for every server. A global one will do.
And also: do I want separate metrics servers for each server? Wouldn't it make more sense to have one? And then the per-server metrics are either on different paths, or... there's just one, with all metrics combined.
For OJF reasons, one metrics server, with per-server metrics on different paths makes most sense.
initial-seed "4"
state-file "state.kdl"
prometheus-server {
bind-to @iocaine.metrics
persist interval="1h"
}
http-server nsoe {
bind-to @iocaine.http
script language=roto path="/some/path" {
module "nsoe" path="/path/to/nam-shub-of-enki"
configuration file="nsoe.kdl"
}
}
Some implications:
prometheus-server./<server-name>, rather than /metrics, since there's only one such server now.I think this results in less resource use, simpler configuration (less repetition!), and simpler code too. The downside is that there's a small metric collection overhead.
I could make that optional, mind you, and if there's a sufficiently compelling case for it, I will - later.
Yeah, I think I like this.
One thing I want to figure out, is how to make it possible for something like OnlyJunk.Fans to hook into the prometheus server and lock the paths down to require a bearer token. Luckily, that's something I can figure out post-4.0!
Because the prometheus-server implementation is in a non-library crate, and isn't a public struct. So post-4.0, I can spin it out into a separate crate, make it hookable, and still be backwards compatible, because as far as the public API goes, this would be pure addition.
I've done this before, for fuck. Now I'm making it nicer to use, both from Rust, and eventually from Roto and Lua too.
Install Fedizen
Get the full app experience
As is tradition, the internal struct names are somewhat unhinged. The configuration is called a Blueprint, which is an interpretation of a Recipe, which is made of Components. Not yet sure how to split a component further (I need nodes and children - will figure something out).
Within the blueprint, I'll have some normally typed members (
Strings andUtf8PathBufs), but the iocaine-specific types will also be funnyly named.For example, a
http-serveris going to beZoomies(because I dunno, it's a name that came to mind, and I'll retroactively find an explanation), the HAProxy server's declaration will internally be calledDevil(because the devil never sleeps, and is such Highly Available).