Client-side (browser) logger to use with Loggly gen2. Check out Loggly's Javascript logging documentation to learn more.
Place the following on your page, and replace the logglyKey value with the key provided by the website:
<script type="text/javascript" src="/js/loggly.tracker.js" async></script>
<script>
var _LTracker = _LTracker || [];
_LTracker.push({
'logglyKey': 'your-customer-token',
'sendConsoleErrors' : true,
'tag' : 'javascript-logs'
});
</script>
Logging text:
_LTracker.push('my tracking string');
Logging JSON:
_LTracker.push({
'text': 'my tracking string',
'aList': [9, 2, 5],
'anObject': {
'id': 1,
'value': 'foobar'
}
});
separate logging instace:
var myBetterLogger = new LogglyTracker();
myBetterLogger.push({'logglyKey': 'your-customer-token' }); // push a loggly key to initialize
Keeping sendConsoleErrors value to true will send all the unhandled errors to the Loggly with the detailed information like error message, URL, line number and column number. This script also take cares of all the previously defined window.onerror functions.
Send your custom tags to Loggly by setting the tag
property.
_LTracker.push({
'logglyKey': 'your-customer-token',
'sendConsoleErrors' : true,
'tag' : 'tag1,tag2'
});
You can proxy the requests from your own domain if the script or its requests are blocked by Ad blockers. To do this, you need to perform following steps
Set useProxyDomain
property to true
_LTracker.push({
'logglyKey': 'your-customer-token',
'sendConsoleErrors' : true,
'tag' : 'javascript-logs',
'useDomainProxy' : true
});
Use the following configuration on your server to forward the requests to Loggly
#Proxy to Loggly
location /loggly/ {
rewrite ^/loggly/(.*)$ /$1 break; # remove the '/loggly' part from the path, leaving /inputs/xxxxxxxx-xxxx-.../tag/xxx
proxy_set_header Host logs-01.loggly.com;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_pass https://logs-01.loggly.com;
}