projectdiscovery / gologger Goto Github PK

Description

gologger.Debug().TimeStamp().Msg("test") => [DBG] [2022-09-19T15:07:57+05:30] test

• Add action for automatic release (see https://github.com/projectdiscovery/roundrobin/blob/main/.github/workflows/release-tag.yml)
• Ensure new releases are created only if there are new commits (see https://github.com/projectdiscovery/team-backlogs/issues/228)

Add at least the following github actions:

• Dependantbot
• CodeQL
• Lint

For example see: https://github.com/projectdiscovery/fastdialer/tree/master/.github

Current Behavior:

Color byte shows like a blankspace block character.

Expected Behavior:

There is no unrecognized character.

Steps To Reproduce:

Run any command that can output colorized information.

Anything else:

Ref: https://github.com/logrusorgru/aurora#windows

Hello there!

I'm encountering a difficulty related to logging in subfinder, which seems to be connected to how gologger handles label and log level. In the piece of code provided below, it seems that whenever an event that includes a label value is logged, this value gets converted to log level during formatting. Is there a specific reasoning behind this design decision?

To illustrate, when I operate subfinder with verbose log level configuration, I encounter numerous logs with a log level that my external logging system cannot process.

{"level":"dnsdumpster","msg":"rate-limited-proxy-108-177-77-100.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"code.l.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"captive.adservice.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"rate-limited-proxy-108-177-64-100.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"google-proxy-66-249-83-100.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"rate-limited-proxy-108-177-73-0.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"rate-limited-proxy-108-177-73-100.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"colab-sandbox.research.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"tensorboard-staging.cloud.google.com","timestamp":"2023-05-25T14:07:57+0000"}
{"level":"dnsdumpster","msg":"mail.google.com","timestamp":"2023-05-25T14:07:57+0000"}

Hello there!
I just tried to pull the newest release of chaos from its corresponding git repo but during compilation it just threw some nasty errors at me. I believe that you removed some methods that go would have been happy to find, but unfortunately it didn't. Tbh I didn't dig down the rabbit hole but I'm certain that it has to be something with the code here.
Cheers,
0x5ECF4ULT

Go version:
go version go1.15.5 linux/amd64

Command ran:
GO111MODULE=on go get -u github.com/projectdiscovery/chaos-client/cmd/[email protected]

Can you guys generate a new release please?
The TimeStamp() method is missing from the current latest release but is shown in the basic-example and exists in the latest codebase.

Cool project, much thanks.

I get these errors on Windows system when trying to install any project-discovery tool from source.

Note:

• By default, the -timestamp flag is set to false in the gologger package.
• You can use the gologger.SetTimestamp function to set the -timestamp flag to either true or false.
• The gologger package will automatically use timestamps in log events based on the value of the -timestamp flag.

Hey there! I was wondering if anyone knows of a way to automatically include the date and time when logging information or errors? It would be super helpful to streamline my logging process.