Improve verbosity of logs
See original GitHub issueThis is a Feature Proposal
Description
I found that existing logs that output with -v
option, doesn’t give good overview of internal process.
To have better overview of that, I looked into serverless internals and added for my purpose logs that expose
- Commands that are about to be pursued with their hooks filled and unfilled with actions
- Hook start and end points with own duration it took
- All AWS requests with parameters, so I can see exactly how SLS works with AWS SDK
Here’s an example output:
I think it’ll be nice to have it in Serverless natively (at least I think there’s no way to introduce it via plugin), so they show either in verbose mode, or with SERVERLESS_DEBUG=true
, or with some kind of namespace debugging (as can be achieved with debug).
I’ll be happy to propose a PR, with that, let me know what you think
Additional Data
- Serverless Framework Version you’re using: v1.19.0
- Operating System: macOS v10.12.6
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
How To: How to increase debugging verbosity of profile status ...
Locate the status log which corresponds to the profile and save a copy of the log for review with a Webtrends Technical Support...
Read more >Increase Build Log Verbosity to Get More Details About a ...
This can be fixed by increasing build verbosity from within Visual Studio Options. We recommend switching it to normal; this displays errors, ...
Read more >Increasing Build Log Verbosity for Visual Studio
Start Visual Studio. Click on "Tools"->"Options...". The following dialog should appear: Visual Studio's option dialog; Select the item "Project ...
Read more >Adjusting log verbosity
Adjust the verbosity programmatically. Log verbosity can also be adjusted by setting a configuration profile on the MobileFirst Operations Console, which must ...
Read more >Configuring the verbosity for restjavad logs on the BIG-IP ...
Important: Increasing restjavad logging verbosity results in higher disk usage. F5 recommends that you reset the restjavad logging configuration ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@medikoo I think so.
AwsProvider#request
is also a central interface method, that is used by core and 3rd party plugins. A change there would break everything.Additionally to
PluginManager#invoke
I would also patchPluginManager#spawn
and show a different message because spawn is used to invoke internal plugin lifecycles from plugins. It allows access toentrypoints
which are not accessible from the CLI. It would be enough to showSpawned 'XXXXXX'
in that case.@horike37 @medikoo I think the core integration solution will introduce too much technical debt and complexity (we’re already talking about 2 env vars here).
Thanks for creating @medikoo and thanks for commenting @horike37 and @HyperBrain 👍
I agree. Having this as an external would be super nice here (something like an extra
debug
plugin).I’ll close this one, but please comment here again if you have any questions or need help. Furthermore feel free to comment once the plugin is done!
Thanks again for opening and kicking off the discussion @medikoo 👍
This issue might be related to https://github.com/serverless/serverless/pull/2821.