Diagnostics WG Summit - Feb 12-13, 2018 - Ottawa, ON Canada

[mike-kaufman]

Diagnostics WG Summit

• Feb 12-13, 2018
• Ottawa, ON Canada
• Location Details & Accommodations: 2016 Ottawa_visitor_guide.pdf

Proposed Agenda

Day 1 - Feb 12 2017

Key Themes - Part1
8:30 - 9:00 - Arrive and settle in
9:00 - 9:10 - Introductions
9:10 - 9:20 - End user perspectives (Netflix)
9:20 - 9:30 - Agenda review
9:30 - 10:00 - Post Mortem - priorities/issues

10:00 - 10:30 - break

Key Themes - Part 2
10:30 - 11:00 - Monitoring - priorities/issues
11:00 - 11:15 - Debugging - priorities/issues
11:15 - 11:30 - Platform neutrality/APIs
11:30 - 12:00 - Testing and Documenation

12:00 - 1:00 - Lunch

1:00 - 3:00 - Breakout 1
3:00 - 3:30 - Break
3:30 - 5:30 - Breakout 2
5:30 - 6:00 - Demo from James/Matteo

6:30 - Dinner

Day 2 - Feb 13 2017
9:00 - 11:00 - Breakout 3
11:00 - 1:00 - Breakout 4

1:00 - 2:00 - lunch

2:00 - 3:15 - Breakout review
3:15 - 3:30 - Break
3:30 - 5:00 - Breakout review continued, recap and actions

The agenda is structured as a review of the key themes related to Diagnostics in order
lay the context for for the more in depth breakout sections, the breakout sessions
themselves and then finally a review of the output from the breakout sections and creation of
an action plan going forward.

Attendees:

1. @mhdawson
2. @mcollina
3. @mike-kaufman
4. @Qard
5. @hashseed
6. @watson
7. @mrkmarron
8. @jasnell
9. @danielkhan
10. @komawar
11. @joyeecheung
12. @cjihrig
13. @fhinkel
14. @jkrems
15. @ofrobots
16. @dshaw
17. @kjin
18. @aruneshchandra
19. @hekike
20. @mmarchini
21. @Flarna
22. @Hollerberg
23. @distracteddev
24. @apapirovski
25. @skaegi
26. @Fishrock123

Doc to refine subtopics/discussion points:
https://docs.google.com/document/d/1mB3nrCOhgKPEpPebpUEBDZQse6yKX4vwuwj-RpAWXWI/edit?usp=sharing

[mhdawson]

Will look into how to book a Room in our office in Ottawa and then suggest a date/time

[watson]

I'm in California for work from the Feb 26th to Mar 6th

[danielkhan]

Thank you for setting that up. I'll definitely attend if it's not in the last week of January. We should also ping @nodejs/post-mortem because if we merge, the summit would be a great kick off for that.

[mhdawson]

To start the discussion.

@nodejs/diagnostics
@nodejs/post-mortem
@nodejs/tsc

I would suggest we hold the summit on Mon Feb 12 and Tue Feb 13 in Ottawa at the IBM office. The weekends before/after include Winderlude if you like skating and the IBM office is close the airport if you want to just fly in/out. Please comment as to wether you want to participate and if those those days work for you or not and we'll either confirm or iterate as necessary.

I would suggest we structure discussion in terms of themes as we did at the first vm summit.

The themes I'd have in mind (probably incomplete, please make additional suggestions) would be:

• Post mortem diagnosis

  • Core tooling that should be part of Node.js itself
    • heapdump generation
    • node report generation (light weight easy to consume dump)
    • core dump generation
  • Core dump introspection
    • llnode, mdb, etc.
    • javascripts APIs
    • maintenance/automation of keeping required data up to date
  • Supporting Promises/async functions
  • What is missing ?

• Monitoring

  • Asynchronous context tracking
    • Async Hooks
  • Tracing
    • Adding Node.js trace points
    • Flight recorder
  • Loader Hooks ?
  • Profiling
  • What else should Node.js have in order to support great monitoring

• Debugging

  • Not sure what we need to discuss on this front....

• Documentation/Guidance

  • Module developers guide (as discussed in VM summit in Germany)
  • How to investigate common issues

• Testing

  • We don't necessarily have good testing or visibility into the testing we do have
  • Diagnostics test pass/fail should be a release criteria ?

• Platform neutrality/APIs

  • Expanding N-API to cover diagnostics APIs ?
  • Platform neutral internal APIs

• What's missing

  • How does Node.js stack up against other languages in terms of diagnostics
  • Would be good to be able to capture what we have, what we need to work on and have deck to
    position that Node.js is good from a diagnostics point of view (possibly after some work)

We can structure however we want but at the first vm summit we had the following general approach

• Morning of first day, discuss key themes as a group. At the end of the morning identify groups that
  want to break out to discuss specific themes
• Afternoon of first day/Morning of second day groups meet to discuss specific themes, make concrete
  plans for next steps and start working on those steps.
• Afternoon of second day get back together as a full group and each sub-group presents an overview of
  what they discussed/planned/completed.

Depending on the number of people we get and the interest in the themes it may or may not make sense to break out into sub-groups.

[jasnell]

Definitely +1, glad to see this move forward. I'll definitely be there.

[jasnell]

I will say that Feb 13th is not a great day as I would need to leave early in order to not be traveling on Feb 14th... which is problematic from a My-Wife-Will-Kill-Me-If-I'm-Gone-On-Valentines-Day perspective. That said, Feb 8-9 and Feb 19-23 are out for me also.

[dshaw]

+1

[danielkhan]

+1

[benjamingr]

Would be amazing to see a push for a better postmortem story for async functions.

[mhdawson]

@benjamingr I knew I was forgetting something. I had thought of that at one point but missed it when putting together the overview.

[mhdawson]

@benjamingr added

Supporting Promises/async functions

under the post mortem section. If that's not what you had in mind just give me some text to add

[ofrobots]

I'm tentative. I have other travel planned for the second half of Feb. I will be able to confirm closer to the date.

[hybrist]

I'll be there and I'm pretty flexible about the dates.