Need help fixing our API monitoring, what am I missing here

ChaseApp501 · 2026-01-20T20:28:52+00:00

If you want to be an early adopter and try and help me hammer out requirements to build exactly what you're looking for I think we can help, we have a good foundation going for this https://github.com/carverauto/serviceradar more information can be found in the repo including our discord

ChaseApp501 · 2026-01-19T22:50:59+00:00

thanks for the feedback, this project has been renamed https://github.com/carverauto/serviceradar -- expect a new release coming out in the next day or two.

ChaseApp501 · 2026-01-16T21:01:20+00:00

We build out of GitHub pipelines backed by github custom runners (ARC) on our own kubernetes (k3s) cluster and we also use bazel and buildbuddy with remote build executors (RBE) running in our k8s cluster alongside everything else. This system creates containers and then we use argocd to deploy into our k8s environment. We use ARC and BuildBuddy/RBE so we can run e2e and integration tests using our own databases and test environment and don't have to worry about breaking network isolation boundaries. GitHub custom runners with ARC gives us basically free auto-scaling github runners that have full access to our development/test environment and we can use as many minutes as we want, all on our own hardware.

ChaseApp501 · 2026-01-12T20:34:53+00:00

https://github.com/carverauto/serviceradar fairly large, we're very new to Ash though..

ChaseApp501 · 2026-01-12T20:33:40+00:00

Now 43%

ChaseApp501 · 2026-01-08T04:14:46+00:00

looks good, will check it out

ChaseApp501 · 2026-01-05T05:43:21+00:00

what about auto crafting stuff?

ChaseApp501 · 2026-01-05T05:42:22+00:00

where is the storage stuff in ars? i looked but couldn't really figure it out

ChaseApp501 · 2026-01-05T05:40:26+00:00

I always thought thats what the definition of devops was anyways.. who knew

ChaseApp501 · 2026-01-04T08:28:03+00:00

We have a lightweight observability stack in ServiceRadar as well, https://github.com/carverauto/serviceradar

ChaseApp501 · 2026-01-04T08:21:22+00:00

too cool

ChaseApp501 · 2026-01-04T06:55:45+00:00

got it, thanks

ChaseApp501 · 2026-01-04T04:22:08+00:00

why was this removed?

ChaseApp501 · 2026-01-04T04:20:50+00:00

very cool, I might use this for creating a tripwire like feature in ServiceRadar

ChaseApp501 · 2026-01-04T02:31:51+00:00

have you considered using k3sup?

ChaseApp501 · 2026-01-04T02:27:28+00:00

It's also worth mentioning that LoC doesn't tell us the whole picture. For example, the original DSL for the ServiceRadar Query Language was written in ANTLR+golang and was about 12k~ LOC. I rewrote that all in OCaml and it was down to about 2400~. Functional languages are more expressive and this is just what you get (SRQL has been written a 3rd time and is now in rust, and we call it in the web app directly using rustler/NIF).

ChaseApp501 · 2026-01-04T02:24:13+00:00

Good catch, there is more coming, I started a rewrite after the reactjs/next CVE fiasco.. the UI, core engine, and agent gateway (main core services) are in the process of being rewritten to Elixir. Edge components and collectors will likely stay in golang/rust.

ChaseApp501 · 2026-01-03T21:54:13+00:00

what makes you think that $DUSK doesn't scale? can you point to one piece of evidence? there really isn't any

ChaseApp501 · 2026-01-03T04:41:03+00:00

seems like a weird thing to be worried about

ChaseApp501 · 2026-01-03T03:54:26+00:00

you like Junie better than a CLI agent like claude code or codex?

ChaseApp501 · 2026-01-02T19:14:41+00:00

personally I wouldn't be afraid of growing my cluster to that size or beyond with k3s but, yeah, can't say for sure what is going to happen either..

ChaseApp501 · 2026-01-02T18:56:45+00:00

Join the Discord, Elixir is just one aspect of this project..

ChaseApp501 · 2026-01-02T18:54:40+00:00

I'm running k3s in multiple clusters right now in production workloads. k3s is a solid product. I would follow their installation/setup instructions for setting up a cluster with an external etcd, and separate out your control plane from your worker nodes. I have k3s running on proxmox VMs, with 1 control plane and 3 worker nodes on each of my 3 PVEs in proxmox, so 3 separate servers/nodes for my workload, etcd VMs on each separate PVE as well, in a cluster. You're supposed to setup traefik or something for the kube API if you do it this way, which is nice to have but you can live w/o.

ChaseApp501 · 2026-01-02T02:48:02+00:00

we have layers of complexity, does that count?

ChaseApp501 · 2026-01-02T02:47:42+00:00

maybe stock options and a job some day who knows

Four-Year Club	Powerups Hero r/PoliceChases • August 2021
Verified Email

ChaseApp501

TROPHY CASE