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.

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

CLI should log to a file instead of the console #2916

Closed
binaek opened this issue Dec 23, 2022 · 2 comments · Fixed by #3680
Closed

CLI should log to a file instead of the console #2916

binaek opened this issue Dec 23, 2022 · 2 comments · Fixed by #3680
Assignees
Labels
Milestone

Comments

@binaek
Copy link
Contributor

binaek commented Dec 23, 2022

Currently, when we set the log level to TRACE, Steampipe CLI sends its log to the console. While having the log is useful for debugging, it is cumbersome and unwieldy.

Instead, steampipe should always send the log out to a dedicated log file like the plugin-manager and service.

@binaek binaek self-assigned this Dec 23, 2022
@github-actions
Copy link

'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.'

@github-actions github-actions bot added the stale No recent activity has been detected on this issue/PR and it will be closed label Mar 31, 2023
@kaidaguerre kaidaguerre removed the stale No recent activity has been detected on this issue/PR and it will be closed label Apr 6, 2023
@binaek binaek added this to the 0.21.0 milestone Jul 13, 2023
@binaek
Copy link
Contributor Author

binaek commented Jul 19, 2023

Optionally, we should consider streaming stderr from all components to the CLI stderr

Two env vars to tweak the behavior:

  • STEAMPIPE_LOG_TO_STDERR - defaults to false
  • STEAMPIPE_LOG_TO_FILE - defaults to true

Postgres has a log_destination config value (link) which can be used to setup multiple log targets depending on which env vars are set.

binaek added a commit that referenced this issue Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment