The document discusses transforming monitoring into an observability platform using InfluxDB, highlighting pain points such as downtime and stakeholder impact. It outlines a proposed architecture and challenges faced, including issues with regional alerting and system management. Additionally, it mentions recruitment opportunities at WP Engine.

1. #
Transforming monitoring
into an Observability
Platform with InfluxDB
Tanny Ng & Nadeem Syed
10.26.2021

2. WP Engine is the leader in Wordpress

3. Who are we?
Tanny Ng
Senior Product Manager,
Observability
Nadeem Syed
Principal Software Engineer,
Observability

4. Agenda
1. Pain Points
2. Solution
○ Our Constraints
○ Architecture, What’s different?
○ Challenges & What we wish we knew?
3. What’s next?
4. We are recruiting! - https://wpengine.careers/ JR100541

5. Pain Points
Downtime Blind Monitoring at Limit

6. Stakeholder Impact
250k/min
Zabbix Backend Queries
10 alerts/hr

7. Solution - What were our considerations?
Build vs Buy? Sensitive Data Cost

8. Solution - What’s different?
Multi Region Alerting Scalable Streaming Distributed Scalability

9. Stakeholder Impact
250k/min
Zabbix Backend Queries
10 alerts/hr
5.5M/min
Points Written
4 alerts/hr

10. Architecture

11. Architecture - Metrics Platform

12. Architecture 1 - Aggregation Layer

13. Architecture 2 - Alerting Layer

14. Architecture 3 - Storage & Visualization

15. Architecture - Metrics Platform

16. Proposed Architecture - Logging Platform

17. Challenges What we wished we know?
● Bear the risk of inaccessible Metrics -
Regional Alerting, but no regional
redundancy of Metrics Platform
Database
● Kapacitor k8 task reload fails - Forced to
restart Kapacitor when tickscripts are
modified
● Influx Enterprise does not work with k8s
● Decomm is hard

18. What’s next?

19. We are hiring!

20. Thank you.
Tanny Ng, Nadeem Syed