By: Thu Nguyen
Read Time: 3 min
You’ve deployed a new feature into production. You’ve done your unit testing, fixed lots of bugs, your code is awesome. Now it’s time for hundreds/thousands/millions of users to break…err…use your feature.
You’re diligent about track usage in real-time and get customer feedback when something goes wrong. You track the performance and response time impacts on the server.
All is good…except…that feature isn’t quite working for a specific group of users. Now what?
With LogDNA, you can monitor for stack traces and exceptions in real time. In your browser, you can tail -f like a boss and see real-time logs from all your app sources, Nginx, and Redis. Since you can combine data from multiple sources and see related events, you can do a thorough root cause analysis and surface hard-to-find bugs.
"403 Forbidden" login
ClassCastException OR NullPointerException
2 hours ago
"'str' object" -TypeErrorTimeframe:
last friday 10am
an hour ago,
Isn’t all logging pretty much the same? Logs appear by default, like magic, without any further intervention by teams other than simply starting a...
First published on www.ibm.com on October 7, 2019. Written by: Norman Hsieh, VP of Business Development, LogDNA You know what they say: you can’t fix what you can’t...
First published as a case study on www.ibm.com on October 3, 2019. What is Log Analysis? IBM Cloud™ Log Analysis with LogDNA enables you to quickly find...