Thanks, Gedd! FWIW: Examples of integrations are generally what is most helpful to aid adoption. This is probably even more important with Flagon, given relatively very few public use-cases online.
Also, @Joshua C. Poore <poor...@apache.org> , do share initial docs, design, etc once ready to accept comments. On Fri, Jan 10, 2025 at 4:29 PM Gedd Johnson <geddjohns...@gmail.com> wrote: > Hey all! > > And Happy New Year! I’m happy to work on an integration with the Grafana > stack and provide an example in the repo > > Best, > Gedd Johnson > > On Fri, Jan 10, 2025 at 16:54 Joshua Poore <poor...@apache.org> wrote: > > > Hi All, > > > > Two quick things: > > > > @JKY and I (mostly Jason) are working a big idea for UserALE. We’re doing > > some feasibility studies, but then would like to raise with the community > > on course of action and integration with current UserALE.js. More on this > > soon, likely from @JKY. > > > > The Board is interested in us have less dependency on ELK. Truly, Flagon > > has NO dependency on ElasticSearch, though we do like it and have some > > worked examples in our repos. Even though our ELK example back-end is > just > > that (and never, ever distributed as a release), it’s probably a good > idea > > to create another worked example of an integration between Flagon and > other > > back-end. I’ve heard of users pushing UserALE.js logs into ELK, > CouchBase, > > Postgress. Apache OpenSearch is a compelling alternative. > > > > I’m not sure I’ll be able to do much with it in the near term... Is there > > anyone who might be interested in rolling a worked example for > integration > > with another backend? Generally, this is pretty easy given UserALE.just > > posts json to wherever. Let me know and I’m happy to help testing! > > > > Josh > > > > > > >
