“LOGS – Learning about the Output through a Glass like System”
summary
Explains that logs are sequential raw outputs used as a blueprint for debugging and claims specific levels — fatal/error/warning/info/debug/trace — with debug and trace as stepwise and microgranular. Lists files and config: all.log cache.log system.log and logback.xml. Identifies practical challenges: space limits, readability and restricted production access, and practical fixes: elasticsearch indexing, storage scaling and log UIs (x log, log analyze, clunk). Shows concrete payoffs: find the exact server, count occurrences, spot patterns and tie errors to a deployment timestamp.
AI-written summary · about
related talks
23mA peek into observability from a tester's lens
20mPython Logging: A meditation on silent failures
43mDebug Like a Scientist!
41mA peek into observability from testers lens
38mLearning from your bugs
21mDealing with Verification Data Overload
21mDealing with Verification Data Overload
46mTesting applications without a GUI. Or using the ELK stack to analyze behavior