logentries

Rails app hosted on heroku: Error R12 (Exit timeout)

由 本小妞迷上赌 提交于 2019-12-20 09:37:32
问题 I have a Rails 3.1.4 app hosted on heroku. I have added the logentries add-on. I didn't touch the default configuration for alerts, and I now receive every few hours an alert: 'Exit timeout': Exit timeout: Heroku/myappname 2012-03-23 11:01:41.723 168 <40>1 2012-03-23T11:01:41+00:00 d. heroku web.1 - - Error R12 (Exit timeout) -> Process failed to exit within 10 seconds of SIGTERM You are receiving this email because your Logentries alarm "Exit timeout" has been triggered. In context: 2012-03

Logentries with Winston in not capturing ERROR, DEBUG

由 橙三吉。 提交于 2019-12-11 19:08:18
问题 I am using Winston 3.1.0 in my NodeJS app, together with Logentries le_node 1.8.0. Logentries is only capturing only INFO, DEBUG nor ERROR nor DEBUG. I am using also Console & File transports, and those are logged correctly. Any idea why LE is only capturing info, debug ? 回答1: Solved by defining levels in constructor: 来源： https://stackoverflow.com/questions/54945706/logentries-with-winston-in-not-capturing-error-debug

Rails app hosted on heroku: Error R12 (Exit timeout)

由 江枫思渺然 提交于 2019-12-02 19:19:30
I have a Rails 3.1.4 app hosted on heroku. I have added the logentries add-on . I didn't touch the default configuration for alerts, and I now receive every few hours an alert: 'Exit timeout': Exit timeout: Heroku/myappname 2012-03-23 11:01:41.723 168 <40>1 2012-03-23T11:01:41+00:00 d. heroku web.1 - - Error R12 (Exit timeout) -> Process failed to exit within 10 seconds of SIGTERM You are receiving this email because your Logentries alarm "Exit timeout" has been triggered. In context: 2012-03-23 11:01:28.878 95 <40>1 2012-03-23T11:01:28+00:00 d. heroku web.1 - - Idling 2012-03-23 11:01:31.740
订阅 logentries