Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

logging to disk #26

Open
alexeagle opened this issue Sep 17, 2021 · 0 comments
Open

logging to disk #26

alexeagle opened this issue Sep 17, 2021 · 0 comments

Comments

@alexeagle
Copy link
Member

  • show these logs via the tool (aspect replay)
  • user can upload logs when asking for help
  • log rotation, exec log included
  • demux into more than one log (maybe)
@cgrindel cgrindel mentioned this issue Oct 5, 2022
Open
@jbedard jbedard mentioned this issue Sep 11, 2023
Closed
gregmagolan pushed a commit that referenced this issue Sep 22, 2023
@jbedard @gregmagolan
refactor: add common cli logging utils (#3406)
eb34aba 
Moving the gazelle logging util methods to a common util for all of the
cli (cli/core/pkg/logger/logger.go). For now this util is the basic go
`log` package, if we continue using this util for logging then we can
replace the underlying log library with anything in the future.

For now there are 2 undocumented env vars to configure logging level +
output file.
The log file + level is auto configured when used within `bazel test`
which has been used by the gazelle tests for quite some time.

Ref:
#428
#480
#290
#26
GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard added a commit that referenced this issue Oct 4, 2023
@jbedard
refactor: add common cli logging utils (#3406)
c5998ed 
Moving the gazelle logging util methods to a common util for all of the
cli (cli/core/pkg/logger/logger.go). For now this util is the basic go
`log` package, if we continue using this util for logging then we can
replace the underlying log library with anything in the future.

For now there are 2 undocumented env vars to configure logging level +
output file.
The log file + level is auto configured when used within `bazel test`
which has been used by the gazelle tests for quite some time.

Ref:
#428
#480
#290
#26
GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard added a commit that referenced this issue Oct 4, 2023
@jbedard
refactor: add common cli logging utils (#3406)
7329b1a 
Moving the gazelle logging util methods to a common util for all of the
cli (cli/core/pkg/logger/logger.go). For now this util is the basic go
`log` package, if we continue using this util for logging then we can
replace the underlying log library with anything in the future.

For now there are 2 undocumented env vars to configure logging level +
output file.
The log file + level is auto configured when used within `bazel test`
which has been used by the gazelle tests for quite some time.

Ref:
#428
#480
#290
#26
GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard added a commit that referenced this issue Oct 4, 2023
@jbedard
refactor: add common cli logging utils (#3406)
c50293b 
Moving the gazelle logging util methods to a common util for all of the
cli (cli/core/pkg/logger/logger.go). For now this util is the basic go
`log` package, if we continue using this util for logging then we can
replace the underlying log library with anything in the future.

For now there are 2 undocumented env vars to configure logging level +
output file.
The log file + level is auto configured when used within `bazel test`
which has been used by the gazelle tests for quite some time.

Ref:
#428
#480
#290
#26
GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard added a commit that referenced this issue Oct 7, 2023
@jbedard
refactor: add common cli logging utils (#3406)
be03c61 
Moving the gazelle logging util methods to a common util for all of the
cli (cli/core/pkg/logger/logger.go). For now this util is the basic go
`log` package, if we continue using this util for logging then we can
replace the underlying log library with anything in the future.

For now there are 2 undocumented env vars to configure logging level +
output file.
The log file + level is auto configured when used within `bazel test`
which has been used by the gazelle tests for quite some time.

Ref:
#428
#480
#290
#26
GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard added a commit that referenced this issue Oct 7, 2023
@jbedard
refactor: add common cli logging utils (#3406)
109c77d 
Moving the gazelle logging util methods to a common util for all of the
cli (cli/core/pkg/logger/logger.go). For now this util is the basic go
`log` package, if we continue using this util for logging then we can
replace the underlying log library with anything in the future.

For now there are 2 undocumented env vars to configure logging level +
output file.
The log file + level is auto configured when used within `bazel test`
which has been used by the gazelle tests for quite some time.

Ref:
#428
#480
#290
#26
GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard added a commit that referenced this issue Oct 7, 2023
@jbedard
refactor: add common cli logging utils (#3406)
54f1245 
Moving the gazelle logging util methods to a common util for all of the
cli (cli/core/pkg/logger/logger.go). For now this util is the basic go
`log` package, if we continue using this util for logging then we can
replace the underlying log library with anything in the future.

For now there are 2 undocumented env vars to configure logging level +
output file.
The log file + level is auto configured when used within `bazel test`
which has been used by the gazelle tests for quite some time.

Ref:
#428
#480
#290
#26
GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard added a commit that referenced this issue Oct 9, 2023
@jbedard
refactor: add common cli logging utils (#3406)
1390ace 
Moving the gazelle logging util methods to a common util for all of the
cli (cli/core/pkg/logger/logger.go). For now this util is the basic go
`log` package, if we continue using this util for logging then we can
replace the underlying log library with anything in the future.

For now there are 2 undocumented env vars to configure logging level +
output file.
The log file + level is auto configured when used within `bazel test`
which has been used by the gazelle tests for quite some time.

Ref:
#428
#480
#290
#26
GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Open Source
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexeagle