Monitoring Flashcards
standard practice in most companies to
manage the error reporting infrastructure, monitor and triage incoming errors, and use trends in errors to make decisions about improvements to future releases and release processes.
hard to monitor performance without
actually harming performance.
biggest limitation of the monitoring is that
it only reveals what people are doing with your software, not why they are doing it, or why it has failed.
Monitoring can help you know that a
problem exists, but it can’t tell you why a program failed or why a persona failed to use your software successfully.
Usability problems and missing features are even harder to detect or observe because
the only true indicator that something is hard to use is in a user’s mind.
monitoring application usage
1) automatically instrumenting applications for user interaction events
2) mining events for problematic patterns
3) browsing and analyzing patterns for more subjective issues
to find out why users are doing something you
need to get explicit feedback from support tickets, support forums, product reviews, and other critiques of user experience.
for developers to fix a problem, they need
detailed steps to reproduce the problem, or stack traces or other state to help them track down the cause of a problem.
**these are precisely the kinds of information that are hard for users to find and submit, given that most people aren’t trained to produce reliable, precise information for failure reproduction.
once the information is recorded in a bug report, even interpreting the information requires
social, organizational, and technical knowledge, meaning that if a problem is not addressed soon, an organization’s ability to even interpret what the failure was and what caused it can decay over time
Insight Providers
gather and analyze data to inform decisions
Modeling Specialists
use their machine learning expertise to build predictive models
Platform Builders
create the infrastructure necessary for gathering data
