The Second Way - Create Telemetry to Enable Seeing and Solving Problems
13 important questions on The Second Way - Create Telemetry to Enable Seeing and Solving Problems
Where does telemetry have to be created?
- Within the application
- Deployment pipeline
- Pre-production environments
- Production environment
Which are according to 2015 State of Devops report are the top two technical practices to enable fast MTTR?
- Version controle
- Telemetry and proactive monitoring in the production environment.
What has to be part of the telemetry architecture?
- Data collection at the business logic, application and environment layer
- An event router responsible for storing our events and metrics.
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
Name different logging levels.
- Debug level
- Info level (user driven or system specific)
- Warn level (conditions that could become an error)
- Error level (e.g. API call failures, internal error conditions)
- Fatal level (information to terminate)
What questions can be asked when solving a problem using the telemetry?
- What evidence do we have from our monitoring that a problem is actually occurring?
- What are the relevant events and changes in our application and environments that could have contributed to the problem?
- What hypothesis can we formulate to confirm the link between the proposed causes and effects?
- How can we prove which of these hypothesis are correct and succesfully effect a fix?
Name a few metric libraries for creating telemetry.
- StatsD (open source created by Etsy)
- JMX
- codahale metrics
- New relic
- Appdynamics
- Dynatrace
- Munin
- Collectd
What is information radiator?
Which values are demonstrated by putting information radiators in visible places?
- The team has nothing to hide from its visitors
- The team has nothing to hide from itself; it acknowledge and confronts problems.
From which levels do we need telemetry?
- Business level
- Application level
- Infrastructure level
- Client software level
- Deployment pipeline level
- overlaying information (e.g. Operational activities as downtime,)
Where are business metrics used for?
- For our acquisition funnel
- A/B testing
- Organizational goals e.g. revenue, user attainment, conversion rates
- high level business planning and operations
- analyzing customer usage.
Name a few infrastructure production tools?
At application level we generate telemetry for..
- Application health
- If organizational goals are achieved.
What's customer acquisition funnel?
This is where the business metrics are needed for.
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding