be2c6a96af
Log args and their indexes, if they look like object ids
2017-03-17 14:20:13 +00:00
e7f71a25d8
Use an explicit prefix
2017-03-17 11:47:38 +00:00
f397678589
Clean up, don't allocate an extra date
2017-03-16 15:07:25 +00:00
5ea83947dd
remove stray compiled js file
2017-03-16 10:10:40 +00:00
1f9d4950a2
Update gitignore
2017-03-16 10:09:16 +00:00
772f950d7c
Test failure when wrapped method is not async/callback
2017-03-16 10:07:52 +00:00
a5aec5b812
Test failure to wrap method
2017-03-16 10:02:19 +00:00
40b238271d
Add tests for methods producing errors, and logger
2017-03-16 09:55:07 +00:00
c3b18618bf
Add unit tests
2017-03-16 09:49:45 +00:00
e99a7f6a87
refactor
2017-03-15 16:07:36 +00:00
3cb0ab2784
Add a 'timeAsyncMethod' helper
2017-03-15 15:06:54 +00:00
caeac717fc
Set UV_THREADPOOL_SIZE to 128 for all processes
2016-10-24 10:50:44 +01:00
2df5845444
updated version to 1.5.0
2016-03-17 09:40:40 +00:00
622bbe3123
return timeSpan from timers
...
to allow additional calculation
2016-03-15 13:52:40 +00:00
29177f8de8
add support for statsd count method
2016-03-15 13:52:32 +00:00
8db30020ae
Monitor event loop by looking for skew
...
If we monitor with setImmediate, we miss big blocking loops. For example,
suppose we have 1000 1ms loops then a single bad 1000ms loop. setImmediate
will only be called at the right time 1/1000 of the time (it has to be the
loop just before the bad one). So this monitoring method gives a good average
if the std dev is low, but doesn't pick up spikes.
Instead, we can monitor the skew from the expected time between setIntervals.
In the case above, with a setInterval for 1000ms, we will pick up a skew
proportional to the amount of time that it overlaps the bad loop. So 50%
change of picking up skew > 500ms, and thus getting a good sense of any
spikes.
2015-12-03 16:32:20 +00:00
738363a6de
Set maxSockets to Infinity for all services
2015-08-31 14:02:03 +01:00
0215b12a5f
log memory usage every minute
2015-08-20 17:03:58 +01:00
f237f7c3cc
remove bug in optional argument handling
2015-08-18 11:23:10 +01:00
27c382416a
fix whitespace
2015-08-17 15:19:13 +01:00
e3e8d80466
remove non-working metrics from graphite
2015-08-17 15:19:07 +01:00
d2af7b24a0
remove randomisation to avoid shutdown problems
2015-08-17 15:18:18 +01:00
bb2dbeaa6e
Merge branch 'master' of github.com:sharelatex/metrics-sharelatex
2015-08-14 15:49:07 +01:00
577a3759c0
bugfix for memory chunk size
2015-08-14 15:44:24 +01:00
e577695f07
Merge pull request #5 from sharelatex/memory
...
add memory check and periodic gc
2015-08-14 14:47:10 +01:00
46ec20ef9c
add memory check and periodic gc
2015-08-14 14:38:24 +01:00
175e3efd5f
update package version to 1.2.0
2015-08-06 09:40:58 +01:00
4bb95541c6
Merge pull request #4 from sharelatex/mongo-driver-upgrade
...
add compatibility with v2 mongo driver
2015-08-02 15:39:34 +01:00
349b499f85
add compatibility with v2 mongo driver
2015-07-30 08:57:43 +01:00
78f429f2b5
Merge pull request #3 from sharelatex/event-loop-monitor
...
added monitoring of event loop time
2015-06-23 13:21:04 +01:00
ffa523bced
added monitoring of event loop time
...
should indicate if node is blocking on libuv threads
as described in https://nodejs.org/api/dns.html#dns_dns_lookup
2015-06-23 10:51:48 +01:00
9329249bc9
Revert "reduce memory capture in http logger"
...
This reverts commit fc2e043b20204e04f240814d4efc05762db7df96.
Had to revert this because req.route.path is not set until a matching
route has been hit, so it was always null inside res.end meaning
statsd data was never sent over.
This commit did not actually stop the memory leak so reverting it
has not short term repocusion
2015-05-14 16:14:24 +01:00
1e0a991fcd
reduce memory capture in http logger
...
only capture the properties of 'req' that we need, to avoid leaking
the whole req object for responses that never call res.end()
2015-05-05 10:50:59 +01:00
1816676e5c
Merge pull request #2 from sharelatex/clean-shutdown
...
Clean shutdown
2015-01-06 14:03:49 +00:00
fa7e068ebb
update minor version, due to addition of new close() method
2015-01-05 16:46:44 +00:00
30070f23b8
add a close() method to terminate the module cleanly
...
closes the statsd connection and cancels registered interval timers
prevents express from hanging when trying to shutdown
2015-01-05 16:45:32 +00:00
60857982b6
Create LICENSE
2014-09-08 09:19:39 +01:00
9acca85843
Release version 1.0.0
2014-08-19 13:32:41 +01:00
c8fae26995
changed type to query_type as it conflicts with logstash
2014-05-13 15:24:23 +01:00
1dea55d8f2
Check that req.route.path is set
2014-05-12 15:28:09 +01:00
284d8fb588
Namespace gauge keys correctly
2014-05-09 13:54:33 +01:00
00c0036ca5
Add open socket monitoring
2014-05-09 13:30:12 +01:00
86f220a2d2
Add collection into graphite key
2014-05-07 11:50:09 +01:00
45ec60d8a6
Fix broken key building in timer
2014-05-07 11:43:46 +01:00
873297b02e
Namespace http request keys
2014-05-07 11:13:21 +01:00
befb48a20f
Use correct key in Metrics.timing
2014-05-07 11:08:46 +01:00
f4895fb04f
Add in http monitoring
2014-05-07 10:58:52 +01:00
4da7fa43fa
Scope name argument properly
2014-05-06 17:33:09 +01:00
125790b604
Ignore all queries
2014-05-06 17:19:04 +01:00
00c12ccab6
Remove redundant count
2014-05-06 17:06:34 +01:00
Shane Kilkelly