"Richard O'Keefe" writes:
> Neither of those use cases actually works.
In practice, they do.
> Consider the following partial class hierarchy from my Smalltalk system:
That's not what I have to deal with in practice. My data comes in as a
CSV file or a JSON file, i.e. formats with very shallow
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
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. B
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
Hi Gabriel,
I found this Beacon-Server [1] that could work, it would be a good use
case in a docker environment where you have several worker images
talking to a single beacon-server-container.
Regards!
[1] https://github.com/grype/Beacon-Server
Esteban A. Maringolo
On Mon, Aug 9, 2021 at 9:10
