If you are ready to setup your own server, you can use Splunk logstash graylog For me the splunk seems the easiest to setup. If you don't want to setup your server, you need to use free plans in loggly-like services. That usually means maximum monthly limit you can send...
Logentries has a special endpoint for logging from AJAX and server-side JS applications. This means that for environments like Parse where using 3rd party libraries is awkward, direct integration is still dead simple- see my fork of @Marco T's gist.
That is an odd article in my eyes, use log4j by installing syslog, hmmmm. There is no way that would work on Openshift. I would suggest you follow the logback instructions instead https://www.loggly.com/docs/java-logback/ With a slf4j Bridge http://www.slf4j.org/legacy.html#log4j-over-slf4j That will enable to log remotely from openshift while only requiring some...
You can avoid these problems if you can manage how you log errors. Clearly just dumping the error object won't work for reasons you discovered. I cherry pick the error information I want to log. I generally don't dump the entityErrors; I select the tell-tale info from them that I...
You should use type: loggly instead of stream. # config.yml monolog: handlers: main: type: loggly token: my-loggly-token level: info tag: symfony-app ...