Paul K space : Brainstorming: PK high level problem statement comments

 Brainstorm planning

 Brainstorm pre-work

 Brainstorm agenda

 Brainstorm outcomes

I recommended new relxci for one reason - the most acurate end to end caoture of internal errors... MNailOnline 24% errors backend = 30 e220's; 1 week worjkign with dev's dropping errors to less than 1% and shifting images to Akamai = 3 e220s - saved them literally millions...if we have anyone expert in any of that kevekl oif tooling we shiould takk asap - if not, NRis quick and I know how to leverage each biut....
the RUM what I need first - end to end trace and timings for a user jouyrney....

1. install agents for each service

2. sort focus to slowest function

3. split that journey so it uses pinned resources for that call only (on slow components)

4. 1 day deep dive with developers to parse results

1. error rate reduction and error handling

2. repetetive funtions that be covrted to classes

3. identify extermal factors on performance

top 10 slow queries - 11 days

1. all development teams consistent message and collective session on the tooling and what it will show

2. propose the plan to deep dive each team and schedule - all resources available

3. potentially bring in tech/tool coach to guide them to improved code

depending on results look at

• Data cache

• prebuilt queries and nosql layer

• deep dive into data

all going well we can enhance scalability with Service Bus in poarallel running

Summary of results

• Andy to resource team members
• Azure / Python / Data
• APM for app and stack - recommend new relic
• APM data to align priorities
• Top Down focus resource at pressure points
• Identify and Validate proposed solutions to problems
• 1 day workshop per issue
• work with dev team
• align understanding
• coach solutions
• agree delivery
• support

Decisions