O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Retour d’expérience sur 4 ans d’utilisation d’un
outil de surveillance synthétique chez SeLoger
A n t o n i o G o m e s R ...
2
SeLoger context1
The rise and fall of our homemade tool2
How we have chosen a new tool3
How we use this tool4
3
SeLoger
1 2 3 4
4
SeLoger: a lot of web sites to monitor and feature teams to help
5
In 2016, SeLoger creates
a performance team to:
HELP TEAMS
Audit
Teach methodology
Coordinate (HTTP/2 migration…)
CHOOSE...
6
21 3 4
The rise and fall of our
homemade tool
7
Our needs
The genesis of our Synthetic Monitoring tool
Third party awareKeep pace with our knowledgeOur KPI
8
PerfMon, our homemade tool
WPT server WPT agents
HAR parser
WS
Cron
Execute test
Cron
Update
URLs of test
PerfMon
9
PerfMon, our homemade tool
10
PerfMon, some features
Access to WPT test
Top requests tracking
Speed Index…
11
PerfMon, tracking Third Party
12
PerfMon, reporting
13
PerfMon, evolution
Each new needs are
implemented quickly
14
PerfMon is AWSOME, but…
Some teams use another tool Some teams don’t trust the results
Small team to maintain it
Need m...
15
31 2 4
How we have chosen a
new tool
16
Questions to ask before starting
Who is the sponsor of
the current tool?
Who uses the tool? How is the tool used? What ...
17
Build vs Buy
18
Make a POC
Provision a budget
Define an objective (complete
features needed)
Involve several teams for a
better adoptio...
19
The processes of selection
Choose tools
Already used
1
Already used
2
Famous
Challenger
Test it
Test it
Test it
Test it...
20
Some tips
Demo from editors are useful
knowledge of market tools is important to choose tools
Make the tool available a...
21
41 2 3
How we use this tool
22
Today
Watch my page
Developers use it
We have migrated to percentile and Speed Index
Reporting is made with it
Performa...
Próximos SlideShares
Carregando em…5
×

We Love Speed 2019 : Retour d’expérience sur 4 ans d’utilisation d’un outil de surveillance synthétique chez SeLoger

138 visualizações

Publicada em

Il y a quelques années, SeLoger a beaucoup investi dans la performance applicative de ses sites Web. Cela s’est concrétisé par la création de postes, l’achat d’outils et la création d’un outil de Synthetic Monitoring basé sur WebPageTest. Aujourd’hui nous avons migré ce dernier sur un outil du marché.

Pendant cette conférence, vous découvrirez dans un 1er temps pourquoi et comment nous avons créé un outil de Synthetic Monitoring.

Nous répondrons aux questions suivantes.
Pourquoi ne pas avoir pris un outil du marché ?
Comment nous l’avons architecturé ?
Comment et pourquoi nous l’avons fait évoluer ?
Comment nous l’avons utilisé en interne pour créer une culture, un référentiel orienté Web Performance ?

Puis dans un second temps, pourquoi et comment nous avons réalisé cette migration :
Pourquoi abandonner un outil sur mesure ?
Quels impacts sur nos projets ?
Quels choix avons-nous effectués tout au long du processus ?
Qu’avons-nous appris ?
Quels sont les pièges à éviter ?
Quels compromis avons-nous acceptés ?

Je commencerai par présenter le contexte de SeLoger et notre défunt outil de Synthetic Monitoring. Puis nous déroulerons le processus de sélection que nous avons mis en place.

Publicada em: Internet
  • Seja o primeiro a comentar

We Love Speed 2019 : Retour d’expérience sur 4 ans d’utilisation d’un outil de surveillance synthétique chez SeLoger

  1. 1. Retour d’expérience sur 4 ans d’utilisation d’un outil de surveillance synthétique chez SeLoger A n t o n i o G o m e s R o d r i g u e s
  2. 2. 2 SeLoger context1 The rise and fall of our homemade tool2 How we have chosen a new tool3 How we use this tool4
  3. 3. 3 SeLoger 1 2 3 4
  4. 4. 4 SeLoger: a lot of web sites to monitor and feature teams to help
  5. 5. 5 In 2016, SeLoger creates a performance team to: HELP TEAMS Audit Teach methodology Coordinate (HTTP/2 migration…) CHOOSE PERFORMANCE TOOLS Synthetic Monitoring, APM, load test… REPORT Monthly report to board Monthly report on TV wallboards
  6. 6. 6 21 3 4 The rise and fall of our homemade tool
  7. 7. 7 Our needs The genesis of our Synthetic Monitoring tool Third party awareKeep pace with our knowledgeOur KPI
  8. 8. 8 PerfMon, our homemade tool WPT server WPT agents HAR parser WS Cron Execute test Cron Update URLs of test PerfMon
  9. 9. 9 PerfMon, our homemade tool
  10. 10. 10 PerfMon, some features Access to WPT test Top requests tracking Speed Index…
  11. 11. 11 PerfMon, tracking Third Party
  12. 12. 12 PerfMon, reporting
  13. 13. 13 PerfMon, evolution Each new needs are implemented quickly
  14. 14. 14 PerfMon is AWSOME, but… Some teams use another tool Some teams don’t trust the results Small team to maintain it Need maintenance PerfMon is a program that prints some performance numbers Few teams use it
  15. 15. 15 31 2 4 How we have chosen a new tool
  16. 16. 16 Questions to ask before starting Who is the sponsor of the current tool? Who uses the tool? How is the tool used? What is the budget?
  17. 17. 17 Build vs Buy
  18. 18. 18 Make a POC Provision a budget Define an objective (complete features needed) Involve several teams for a better adoption Plan (0.5 day by week for 3 months)
  19. 19. 19 The processes of selection Choose tools Already used 1 Already used 2 Famous Challenger Test it Test it Test it Test it Demo by editor Demo by editor WOW effect Unsuitable Dashboard Report Unsuitable Not oriented webperf Try to understand pricing Ping pong mails Ask evolution Negotiate license Ask evolution Report bug « No » man Selected Not Selected Ask evolution « Yes » man
  20. 20. 20 Some tips Demo from editors are useful knowledge of market tools is important to choose tools Make the tool available and visible Communicate with editors to adapt the license Have a sponsor Prove the accuracy of the tools (ask help to the editor if needed) Show the tool in action Forward the needs to editors "You are the first customer to ask us for this feature" = Warning Try to have the editor’s roadmap "We will add this feature to our backlog" = Warning
  21. 21. 21 41 2 3 How we use this tool
  22. 22. 22 Today Watch my page Developers use it We have migrated to percentile and Speed Index Reporting is made with it Performance culture improved Anybody (Dev, PO…) can use it

×