-
Logdna keeps our server alive after we try to terminate with SIGINT. Here's Why we think it occurs (steps 1, 2, 3):
```
function onSignal(sigType) {
var i = loggers.length;
var finalize …
-
```
echo "deb http://repo.logdna.com stable main" | sudo tee /etc/apt/sources.list.d/logdna.list
wget -O- http://repo.logdna.com/logdna.gpg | sudo apt-key add -
sudo apt-get update
sudo apt-get in…
-
Flushing logs on SIGINT and SIGTERM is a nice idea, but since you don't then call `process.exit()` the node process hangs after the logs have been flushed:
https://github.com/logdna/nodejs/blob/mas…
-
At the moment it is not possible to build the agent on windows with Visual Studio 2017.
Therefore the Text in the CONTRIBUTING.md seems to be wrong: `Ensure you have Visual Studio 2015 or newer ins…
virth updated
7 years ago
-
Hey,
I'm using Logdna w/ bunyan. On SIGTERM my logs are being logged to console but don't make it to logdna. I see you have some sort of message buffer. Is there a way to flush it manually or anoth…
-
This is a pretty big deal for me, see comment here: https://github.com/logdna/nodejs/commit/a14e1245a91e9c0e7493e0c6a38f547409ebca1b#diff-212f63e53d7aa8ed04659d1cabd48137R210
-
My apologies if this is user error...
This doesn't work:
```var Logger = require('logdna');
var options = {
hostname: 'localhost',
app: 'app-name'
};
var logger = Logger. setupDef…
-
Starting new pod results in:
```rb
2017-04-26T13:51:07.122756255Z [170426 13:51:07] ------------------------------------------------------------------
2017-04-26T13:51:07.125148525Z [170426 13:51…
-
Logspout stops logging after truncating a logfile from a container
to reproduce this, follow these steps:
start a container f.e.:
`docker run -d ubuntu /bin/sh -c "while true; do echo hello wo…
-
it would be nice if there was a command to the logdna agent to show files that is "successfully" watching instead of using lsof -p