-
-
Notifications
You must be signed in to change notification settings - Fork 43
Improve logging #29
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
Improve logging #29
Conversation
head: info.head, | ||
processingTime: info.processingTime | ||
} | ||
})) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps we could use a severity
field in the after-export
section. maybe 'INFO'
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks good to me. Have you been able to deploy it to stage and see if it looks OK on Stackdriver?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(This may have been an intermittent CircleCI issue so I'm going to retry the build.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rebuild worked. Now I'm dealing with a different deployment issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, that worked. The latest version of this branch has been deployed to stage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps we could use a severity field in the after-export section. maybe 'INFO'?
done in cbb4e13
cc @bpostlethwaite who might be interested in helping out. |
} | ||
}) | ||
|
||
app.on('export-error', (info) => { | ||
if (SHOW_LOGS) { | ||
console.log(`export error ${info.code} - ${info.msg}`) | ||
console.log(JSON.stringify({ | ||
severity: 'ERROR', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
console.warn(err) | ||
if (SHOW_LOGS) { | ||
console.log(JSON.stringify({ | ||
severity: 'ERROR', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@scjody @bpostlethwaite wanna give this another 👁️ ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💃
resolves #2