Daniel Putz & Maksim Puzykov [Volvo Cars] | History of Monitoring at Volvo Cars | InfluxDays Virtual Experience London 2020
•Descargar como PPTX, PDF•
0 recomendaciones•687 vistas
In this session, Daniel and Maksim from Volvo share their experiences using InfluxDB to build a monitoring ecosystem.
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Daniel Putz & Maksim Puzykov [Volvo Cars] | History of Monitoring at Volvo Cars | InfluxDays Virtual Experience London 2020
Similar a Daniel Putz & Maksim Puzykov [Volvo Cars] | History of Monitoring at Volvo Cars | InfluxDays Virtual Experience London 2020 (20)
Más de InfluxData
Más de InfluxData (20)
Último
Último (20)
Daniel Putz & Maksim Puzykov [Volvo Cars] | History of Monitoring at Volvo Cars | InfluxDays Virtual Experience London 2020
- 1. Influx Data @ Volvo Cars Daniel Putz - Maksim Puzyrkov
- 4. Report vs Reality 5 99.8% of infra-components in CMDB are monitored
- 5. One Key to Success 6
- 7. We had to do something different • Best of breed vs One fits all • Enable Digital Teams = provide Self-Service • Accelerate by removing dependency • Dont rule. Provide more value than available on the internet. 8
- 8. DEVOPS ENABLMENT STACK 9 Environment Planning CI/CD Quality Monitoring Logging Azure Azure Plans (ADO) NOI Application Insights Apica Azure Repos (ADO) Azure Pipelines (ADO) Azure Artifacts (ADO) Azure Test Plans (ADO)Performance Center LoadRunner UFT Elastic Search Kibana Grafana SonarQube Logstash ServiceNow
- 10. Resolution Principle 5/20/60Detect / Identify / Resolve 11
- 11. Where are we now? 12
Notas del editor
- Will talk about the importance of … Transparency when it comes to monitoring information Self-service in order to accelerate the product teams Mindset of the teams on taking responsibility … in an enterprise such as Volvo Might not make sense to all companioes (and is heavily challenged here as well)
- Focus on Infrastructure Monitoring Historically a lot of IBM IBM Tivoli monitoring on an old version By the way this is a Volvo Amazon, known for its durability! The older ones of you might remember. Does the job but you have to do it carefully and may not demand too much Application teams taking things into their own hand One central monitoring team having the insight onto the information Lots of
- Good numbers, hugh? Great monitoring I asked Maksim to visualize the data How does this happen? Thresholds not set correct because teams do not take responsibility Culture of hiding the problem So what was happening was that the teams were waiting for a component turning into critical state. This created P1 or P2 incidents and in the worst case the factory line was standing still. And that shall NEVER happen. IN a production focused company the assembly line can not stand still. So the question was:
- 2018 deciding to go for a different setup Providing a
- Best of breed: Architectural principle to use open source and to go for the best products in the market Volvo Cars changed the set up to DevOps Product Teams who take care of their entire life cycle. No central teams anymore.
- Very different throughout the organisation. Some teams have taken things in their own hands and have been running by themselves for along time. Many are like the ones in the picture getting started. But these Teams understand that they are responsible – and are fightened.
- One more thing that I want to share is a resolution principle that I always suggest larger teams to put in place-.
- Some teams appreciate a lot what we do Some teams want the full service back (to be able to point fingers) This is our XC40 recharge