-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Add option to change the log level of the logs emitted by triggers #8329
Comments
Thanks for opening this issue!
|
Interesting idea; is there an alternative concept to adding N parse server options? In theory someone could ask the same for any other log entry that is written and we'd end up with many new Parse Server options. |
Yes, I guess we could use a single option and an object as value, but I guess it would be tricky to use with environment variable. |
If I'm not mistaken we do have other parse options that accept stringified JSON objects, so it should work fine as env var. |
Mmmm, you're right, thx. I'll make some corrections... |
@mtrezza I made some corrections according to your comments. What do you think ? |
New Feature / Enhancement Checklist
Current Limitation
Parse Server can really get very wordy when actively using triggers (beforeSave, afterSave) : this can quickly lead to oversized log files and drowned informations.
By default, theses messages are written to the log file using the 'info' channel. The only way to shut them off is to raise the log level of Parse Server to the 'warn' level.
Customization is a key characteristic of Parse Server. Developers should be able to modify the channel so they can enforce their log policy.
Feature / Enhancement Description
Add three log level options into the Parse Server config (logLevelTriggerAfterHook, logLevelTriggerSuccessBeforeHook, logLevelTriggerErrorBeforeHook) in order to fine-tune the triggers log channel according Winston's one ('info', 'debug','warn').
Example Use Case
Alternatives / Workarounds
The only way to shut them off is to raise the log level of Parse Server to the 'warn' level.
3rd Party References
The text was updated successfully, but these errors were encountered: