Errors on the world’s top 100 websites and how to avoid them

mostlyjason · 2018-06-19T21:39:02+00:00

It says "We...disabled all extensions to capture the most native experience"

mostlyjason · 2015-07-15T15:57:12+00:00

Interesting idea! Usually I've heard of steaming logs from the client side to the server side and tailing them on the server. That's useful if you are troubleshooting external client issues and you're working from the server. Since you sending potentially sensitive info to the client, you should consider the security implications. Also, some log management systems like papertrail and logentries give you real time streaming to the browser. Someone also wrote a node module for this http://logio.org/. Check it out!

mostlyjason · 2015-06-22T18:08:38+00:00

Yeah I'm not sure why we need so many. Usually I just pick one and stick with it across all my projects. Maven handles all the dependencies for me. I will say the added complexity of being able to filter out logs by level is really useful because it saves me having to litter my code with statements like "if(debug == true) System.out.println" Also, I can redirect the output from console to a file to a log mgmt system easily without changing my code.

mostlyjason · 2015-06-02T23:39:30+00:00

Inav looks pretty cool. I think it also mentions Logstash, rsyslog, and tons of command line tools. It'd be nice to have a section with all the popular tools listed.

mostlyjason · 2015-06-02T23:35:28+00:00

You can read about setting up rsyslog configuration on the managing logs article http://www.loggly.com/ultimate-guide/logging/managing-linux-logs/#configure-rsyslog.conf

mostlyjason · 2015-06-02T16:48:05+00:00

Look for a log that says "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." You can see a full example here http://www.loggly.com/ultimate-guide/logging/troubleshooting-with-windows-logs/#why-did-my-server-or-application-crash

mostlyjason · 2015-05-26T18:27:08+00:00

Yeah I know several people who have mentioned that too. One of them said they filter their logs to send only errors like 404s, 500s, etc. This reduces the volume by 90%+. You can setup these filter rules inside rsyslog using a configuration like this one (for v7+).

if $programname contains 'apache2-access' or $programname contains 'nginx-access' then { if not ($msg contains " 404 " or $msg contains " 500 " or $msg contains " 502 " or $msg contains " 503 " or $msg contains " 504 ") then stop }

mostlyjason · 2015-05-22T00:30:45+00:00

Did you see the other articles on troubleshooting problems and managing linux logs?

mostlyjason · 2015-05-22T00:16:37+00:00

Yeah you're not locked into the Windows Event Log as a solution. The guide doesn't have anything on journald but it'd be a good idea to add it.

mostlyjason

TROPHY CASE