-
Notifications
You must be signed in to change notification settings - Fork 265
winston out, intel in #4045
base: dev
Are you sure you want to change the base?
winston out, intel in #4045
Conversation
@seanmonstar - travis keeps failing. :( |
I restarted the failed jobs. Looks green now. |
Can you update the
|
@@ -38,6 +38,14 @@ var Logger = function(options) { | |||
* transactions. | |||
*/ | |||
|
|||
const SEVERITY_MAP = { | |||
// cef => intel | |||
info: '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.
I did this with winston at one point too, the reason I didn't change CEF logging over is because of a comment somewhere that said "we want to see CEF logs distinct from normal logs". I like this way 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.
yea, this still has cef being used explicitly, but everything sent to cef is also passed back to us as a normal log.
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.
Cool, I like it.
@seanmonstar - intel is a nice lib! All of my concerns are inline in comments already, I have not yet load tested this to see how it performs. I am seeing a substantial number of Selenium failures and am unsure whether they are caused by this PR or by something else. |
When running the selenium tests locally, this is the error I see:
|
@shane-tomlinson actually, the ssl cert for testidp.org has expired, so a lot of selenium tests are failing at the moment. |
@shane-tomlinson you rock! |
@shane-tomlinson I rebased in fixes for many of the comments. Some I left questions back for you. I have some work in intel@master that will allow me to remove several of the filters from |
@seanmonstar - can you add this diff? diff --git a/lib/logging/filters/statsd-increment.js b/lib/logging/filters/statsd-increment.js
index 6f6fd10..cedf569 100644
--- a/lib/logging/filters/statsd-increment.js
+++ b/lib/logging/filters/statsd-increment.js
@@ -12,8 +12,6 @@ var IncrementRegExpMatches = [
/^wsapi\./
];
-uncaught_exceptions
-
exports.test = function(msg) {
for (var i = 0, regExp; regExp = IncrementRegExpMatches[i]; ++i) {
if (regExp.test(msg)) return true; |
@seanmonstar - looking manually through the logs on a test instance, the entire configuration is printed when the processes start, meaning SMTP, database & other |
#4045 (comment) remove more files! |
@seanmonstar - When attempting to run the load tests, I am seeing 503s when creating the initial users. This happened before, but I was able to complete the user creation ~50% of the time before, now I cannot at all. Quite possibly user error on my part. [app@ip-10-105-2-239 bin]$ BROWSERID_FAKE_VERIFICATION=true ./load_gen -s https://intel-shane.personatest.org |
Not sure which you are asking to have turned off. Previously, it would put the config in the log on production environments, but not bother annoying the user in dev where it would have also been put in the console. I want the production dump to stay as-is. |
woops, I left in that |
@shane-tomlinson I had goofed on the |
Thanks for the feedback about the production dump @jrgm. |
Thanks for the changes @seanmonstar! From a dev standpoint, I am good with this PR as it is. Doing local load testing, I am seeing a slight performance regression from the current dev. Method: 3 windows & a stopwatch needed. Window 1: Window 2:
Stopwatch: Window 3:
Start the stopwatch and load_gen at the same time. In the window with htop, keep track of the TIME+ of the router. Stop load_gen when the stopwatch completes at 1:30. With the current dev, the router uses ~0:00.17 @jrgm - you have far more fu at load testing than I, could you give this a whirl and see what you think? |
@seanmonstar - I am seeing failures when running the backend tests locally:
|
@callahad fixed @shane-tomlinson latest comment. only other thing i'd point out, is that the json is likely a little different than what winston output. is that terrible? |
@seanmonstar this was the thing that killed the 10.23 release, right? Perf regressions with Still seeing unit test errors locally for me, might be my setup?
|
@seanmonstar ah yup, looks like travis is fine. mind rebasing? |
rebased! |
@@ -320,7 +320,7 @@ exports.getPublicKey = function(domain, cb) { | |||
// Is issuingDomain allowed to issue certifications for emails from | |||
// emailDomain. | |||
exports.delegatesAuthority = function (emailDomain, issuingDomain, cb) { | |||
exports.checkSupport(emailDomain, function(err, r) { | |||
exports.checkSupport(emailDomain, function onSupportChecked(err, r) { |
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.
yay function names 🍻
@seanmonstar Do you know anything about toobusy load testing for this patch? Been a while, I could use some help getting going. Maybe we can fill out the infamous empty section of the load_gen documentation that explains how to use the tool. paging @jrgm and/or @jbonacci :-) |
So, this replaces our usage of winston with intel. Why?
WritableStream
's internal buffering, instead of drain events: https://github.com/seanmonstar/intel/blob/master/lib/handlers/stream.js#L22