mirror of
https://github.com/Foundry376/Mailspring.git
synced 2025-03-03 03:23:45 +08:00
Try adding newrelic logging
This commit is contained in:
parent
14b5bef0a7
commit
93189b0f22
4 changed files with 51 additions and 0 deletions
|
@ -1,3 +1,5 @@
|
|||
require('newrelic');
|
||||
|
||||
const Hapi = require('hapi');
|
||||
const HapiSwagger = require('hapi-swagger');
|
||||
const HapiBoom = require('hapi-boom-decorators')
|
||||
|
|
24
packages/nylas-api/newrelic.js
Normal file
24
packages/nylas-api/newrelic.js
Normal file
|
@ -0,0 +1,24 @@
|
|||
/**
|
||||
* New Relic agent configuration.
|
||||
*
|
||||
* See lib/config.defaults.js in the agent distribution for a more complete
|
||||
* description of configuration variables and their potential values.
|
||||
*/
|
||||
exports.config = {
|
||||
/**
|
||||
* Array of application names.
|
||||
*/
|
||||
app_name: ['Nylas K2 API'],
|
||||
/**
|
||||
* Your New Relic license key.
|
||||
*/
|
||||
license_key: 'e232d6ccc786bd87aa72b86782439710162e3739',
|
||||
logging: {
|
||||
/**
|
||||
* Level at which to log. 'trace' is most useful to New Relic when diagnosing
|
||||
* issues with the agent, 'info' and higher will impose the least overhead on
|
||||
* production applications.
|
||||
*/
|
||||
level: 'info',
|
||||
},
|
||||
}
|
|
@ -1,3 +1,4 @@
|
|||
require('newrelic');
|
||||
global.Promise = require('bluebird');
|
||||
|
||||
const {DatabaseConnector} = require(`nylas-core`)
|
||||
|
|
24
packages/nylas-sync/newrelic.js
Normal file
24
packages/nylas-sync/newrelic.js
Normal file
|
@ -0,0 +1,24 @@
|
|||
/**
|
||||
* New Relic agent configuration.
|
||||
*
|
||||
* See lib/config.defaults.js in the agent distribution for a more complete
|
||||
* description of configuration variables and their potential values.
|
||||
*/
|
||||
exports.config = {
|
||||
/**
|
||||
* Array of application names.
|
||||
*/
|
||||
app_name: ['Nylas K2 Sync'],
|
||||
/**
|
||||
* Your New Relic license key.
|
||||
*/
|
||||
license_key: 'e232d6ccc786bd87aa72b86782439710162e3739',
|
||||
logging: {
|
||||
/**
|
||||
* Level at which to log. 'trace' is most useful to New Relic when diagnosing
|
||||
* issues with the agent, 'info' and higher will impose the least overhead on
|
||||
* production applications.
|
||||
*/
|
||||
level: 'info',
|
||||
},
|
||||
}
|
Loading…
Reference in a new issue