t) and I'm not sure of the
>>> generally-accepted defaults / layout / structures for go projects. When I
>>> raised my paw, it was largely because I'd like to learn from people who do
>>> have this kind of experience (: I've found that working on lazygit h
learn more than following a course, not in the least because there's
>> existing code and structure there and people to tell me when I Do It Wrong :D
>>
>> I'm still very happy to be involved in log4go (assuming it's called that).
>>
>> -d
>> On
has made
> me learn more than following a course, not in the least because there's
> existing code and structure there and people to tell me when I Do It Wrong :D
>
> I'm still very happy to be involved in log4go (assuming it's called that).
>
> -d
> On 2021/
ing a course, not in the least because there's existing code
and structure there and people to tell me when I Do It Wrong :D
I'm still very happy to be involved in log4go (assuming it's called that).
-d
On 2021/07/01 17:23:40, Ralph Goers wrote:
Davyd,
You have commit rights but I
#x27;t think it should be
>>>> too complicated, would be to create a Go API that allows us to define
>>>> hierarchies of log levels, just like we know them in the Java world. This
>>>> API would be used in the application to log, but it wouldn't actual
>> API would be used in the application to log, but it wouldn't actually do
>>> any logging but internally sort of use an underlying framework (possibly
>>> auto configured to TRACE or the most talkative log level) and forward log
>>> requests to that if it p
Yes, I understand what you are asking for. From what I can see that would
involve
creating our Log4Go (wish we could use that name) to emulate Log4j as much as
possible and then creating separate Appender projects to pass events to logrus,
zerolog, etc. Typically, I would expect those
configured to TRACE or the most talkative log level) and forward log
>> requests to that if it passes the filter criteria.
>>
>> So in PLC4Go for example we could use this Go Logging API. If my company now
>> uses logrus or zerolog, then all we have to do in that applica
Hi Ralph and others,
right now the thing that annoys me most is that for example in PLC4Go we
used zerolog ... in an application at work we used logrus. Now I needed
to setup a configuration to sync the config of zerolog with that of
logrus. This is just annoying. With my proposed log4go API
ging API. If my company now
> uses logrus or zerolog, then all we have to do in that application is
> initialize the log4go system (I know there's a project using that name
> pattern ... I'm referring to something we built) with the corresponding
> adapter.
>
> What do you thin
ramework (possibly
auto configured to TRACE or the most talkative log level) and forward log
requests to that if it passes the filter criteria.
So in PLC4Go for example we could use this Go Logging API. If my company
now uses logrus or zerolog, then all we have to do in that application is
i
s logrus or zerolog, then all we have to do in that application is
initialize the log4go system (I know there's a project using that name pattern
... I'm referring to something we built) with the corresponding adapter.
What do you think? I'm not one of these "I whish someone
I support the initiative. At bol.com, we also needed to implement our own
Go logging layouts (JSON) and appenders (Redis). That said, I don't know Go
and I don't think I will be able to spare time to both learn a new language
(even though I am really into learning Go) and maintain such a project. I
Sounds cool to me, too. This could be a nice chance to standardize config
file formats across the various languages here, too, though more of a nice
to have.
On Wed, Dec 9, 2020 at 16:01 Gary Gregory wrote:
> I'm always up for learning something new :-)
>
> Gary
>
> On Wed, Dec 9, 2020, 16:29 Ra
I'm always up for learning something new :-)
Gary
On Wed, Dec 9, 2020, 16:29 Ralph Goers wrote:
> The company I work for has started using Go for some of the middleware
> components we are developing. I have looked at several logging frameworks
> for Go and have not been impressed by any of the
The company I work for has started using Go for some of the middleware
components we are developing. I have looked at several logging frameworks for
Go and have not been impressed by any of them. As such, I am considering
starting a project here. The major goals of this would be:
Use an externa
16 matches
Mail list logo
