That is my impression with Beacon, there was a lot of discussion about it and then never heard of it again.
Is your code available somewhere? Regards! ps: There is also TinyLogger that works by means of a DynamicVariable, but I liked the idea of using objects instead of just strings for logging (which I'm manually doing now). Esteban A. Maringolo On Mon, Aug 9, 2021 at 9:16 AM Norbert Hartl <norb...@hartl.name> wrote: > > Beacon is a sad story. There was a lot of initiative and motivation for > loggers which was killed. But it is still a good foundation to build > something useful on top of it. I integrated a syslog option when I was > working on beacon. In my projects I’ve done a sender to elasticsearch for > logging. Beacon’s design allows all of that. After motivation died nobody put > some love into it again. That’s all! > > Maybe time to pick it up again. But I personally have too much on my plate > right now to take another attempt. > > Norbert > > > Am 09.08.2021 um 14:08 schrieb Gabriel Cotelli <g.cote...@gmail.com>: > > Beacon is integrated as part of Pharo now, but the repository includes more > logger options. Maybe some option there allows forwarding the logs to a > centralized place. I'm also interested in other's experiences regarding > logging options because we want to settle on some option as the default for > our Pharo components. > > On Sun, Aug 8, 2021 at 11:29 AM Esteban Maringolo <emaring...@gmail.com> > wrote: >> >> What are the current options for logging? >> >> Beacon seems to be the most modern one, but the Github repository >> doesn't seem very active (maybe it forked somewhere else). >> >> Given that the logs might come from different worker images, is there >> something that can work via HTTP or similar? (it is, forwarding the >> logged events to a server). >> >> Regards! >> >> ps: I think I've asked this before, but couldn't find my previous >> question about it. >> >> >> Esteban A. Maringolo > >
