Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Oh, oh, oh! I got one not mentioned yet:
ELK.
Well, not the whole of the ELK stack (Elastic, Logstash and Kibana, though the full stack size is much larger nowadays), but their watchers. A watcher is a piece of JSON with some search specifications on when to trigger and send an alert to email/slack/teams/whatever. We're basically abusing it as an alerting system, and generally it works... Fine... Presuming Filebeat actually ingests our logs (which is partially our fault, as there's a fix, but it takes too damn long to drag 3 teams along to implement what needs implementing to fix that problem).
Anyway, the problem is not the watcher itself, even though it is painful (heh) to learn the structure. It's "Painless", the JVM-based scripting language available in a watcher. It's anything but. It is SO painful to write code, inside of a JSON object, making sure everything is exactly as it should be, having to use the DevTools in Kibana to try and trigger it, wait to see what enormous error comes out while praying it works. No IDE, no nothing. Ah, I lied. It does have Syntax Highlighting, for non-Painless code, IIRC...
Oh, having to dig information out of the data you get is super unintuitive too.
At least the UI/Kibana is good, and Elastic is pretty good too. Fuck Filebeat though. And Painless.