User Details
- User Since
- Mar 15 2019, 8:42 PM (172 w, 2 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- TheAnarcat [ Global Accounts ]
Oct 7 2019
Why double? Curly braces don't need escape in the shell.
Oct 3 2019
On a more detailed level: there will be at least one conflict in syntax I can think of right now, { and } can appear in both Cumin and Prometheus. I'm assuming the latter will need escaping (?)
Oct 2 2019
Are you suggesting to keep the grammar super basic and let the user write any prometheus query?
Oct 1 2019
hi! i've been looking into this again and I think i might start looking at making a backend for Prometheus myself. It seems the first step would be to design a grammar for the Prometheus queries that wouldn't conflict with the existing selectors.
May 2 2019
whoohoo! thanks!
oh i hadn't noticed tests had failed... fixed that and the other comment, hopefully we're all done here.
May 1 2019
ping - i think we need someone to review this...
Apr 4 2019
Mar 21 2019
would love to see this happen as well.. i've been banging my head against this trying to figure out why =true wouldn't work until I found this ticket. :) as a stopgap, documenting this limitation would be a good start...
Mar 19 2019
right, so I think I understand your setup - you use HTTPS to talk to the PuppetDB from various hosts and probably use something like IP-level blocking to ensure data integrity. that's fine and it's what we do for other stuff like monitoring (Prometheus) here as well. i just don't see why i should absolutely get a valid certificate to talk to the PuppetDB if I have authentication and privacy figured out some other way.
Mar 18 2019
patch now lives in https://gerrit.wikimedia.org/r/#/c/operations/software/cumin/+/497312 - let me know if i should expand it to cover ~/.config discovery and so on.
hi @Volans ! long time no see ;)
I did - as you can see, in the last command:
Mar 15 2019
i managed to login to gerrit, but couldn't figure out how to push my patch for review:
As an extension to this, it would perhaps be necessary for Cumin to look in standards directories, like ~/.config/ (or maybe ~/.config/cumin) for its configuration file, otherwise root is still required to edit things in /etc/cumin/...