|
|
|
|
Back to newsletter 209 contents
A significant percentage of the average experienced performance engineer's time is spent on troubleshooting. There's a problem in production or QA, and you need to figure out what is causing it. The better the visibility into your system, the easier it is to find the (root) cause. What I've been calling the "visibility" has new term in performance engineering: "observability".
Baron Schwartz provides a lovely quote to clarify how "observability" relates to monitoring: "Monitoring tells you whether the system works. Observability lets you ask why it's not working". This is fundamental for performance engineering. You need monitoring - without it you are blind to what is happening in your system. But monitoring only gets you the data.
Your system needs to produce metrics (data generation). You need to collect the metrics to provide monitoring (data collection). These metrics can be displayed for analysis, typically with some kind of dashboard/console/profile display tool, or automatically analysed typically using threshold breaches of trend lines to generate alerts (data analysis). This is basic observability. Make sure you have it.
Now on to our usual Java performance news section, tools, articles, talks. And of course those tips from this month's articles and talks, as ever are extracted into this month's tips page.
Java performance tuning related news.
Java performance tuning related tools.
Back to newsletter 209 contents
