diff --git a/wg-meetings/2019-04-17.md b/wg-meetings/2019-04-17.md
new file mode 100644
index 0000000..1c24a0c
--- /dev/null
+++ b/wg-meetings/2019-04-17.md
@@ -0,0 +1,90 @@
+# Node.js Foundation Diagnostics WorkGroup Meeting 2019-04-17
+
+## Links
+
+* **Recording**: https://www.youtube.com/watch?v=FxsT8qZua-E  
+* **GitHub Issue**: https://github.com/nodejs/diagnostics/issues/292
+
+## Present
+
+* Michael Dawson (@mhdawson)
+* Peter Marton (@hekike)
+* Ruben Bridgewater (@BridgeAR)
+* Kelvin Jin (@kjin)
+* Diagnostics team: @nodejs/diagnostics
+
+## Agenda
+
+## Announcements
+ 
+*Extracted from **diag-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
+
+* Kevin, perfetto repo is now created, https://github.com/nodejs/perfetto-nodejs-wip
+  * Have build perfetto with gyp, ironing out a few issues.
+* Peter still working on use cases, hope to share today, but hope to share tomorrow and we
+  can discuss in 2 weeks.
+
+### nodejs/node
+
+* Support pausing the debugger on script load [#24687](https://github.com/nodejs/node/issues/24687)
+  * Kevin was going to follow up since person who opened left Google. 
+    will report back next time.
+
+### nodejs/diagnostics
+
+* Post-mortem debugging support inside V8/Node.js [#227](https://github.com/nodejs/diagnostics/issues/227)
+  * We can take agenda tag off, we agree on way forward at summit
+    now we just need to wait for progress.
+
+* Diagnostics "Best Practices" Guide? [#211](https://github.com/nodejs/diagnostics/issues/211)
+  * Work that Peter is doing is moving this forward as mentioned before.
+
+* Diag WG Deep Dives - topics [#168](https://github.com/nodejs/diagnostics/issues/168)
+  * No update this week.
+  * Peter Marton, after he shares use cases would be good to do deep dive on each use case.
+
+* Expectation about tier of support from diagnostic tools and VMs [#157](https://github.com/nodejs/diagnostics/issues/157)
+  * No update this week, focus is on defining best practices
+  * Peter Marton working on a doc with an updated set of user stories.
+  * Removing agenda tag until we make progress on the best practices.
+
+* \[async_hooks\] stable API - tracking issue [#124](https://github.com/nodejs/diagnostics/issues/124)
+  * Related is issue around async context propagation. Vladimir is trying to resolve one
+    test case where state is lost.
+  
+* Async-context formalization and diagnostics support [#107](https://github.com/nodejs/diagnostics/issues/107)
+  * We don’t have Mike K this week so no update.
+
+* \[trace_event\] tracking issue [#84](https://github.com/nodejs/diagnostics/issues/84)
+  * Working on perfetto but nothing else to report this week.
+
+* Flag for unhandled rejects in core
+  * Should we talk about new default?
+    * you can opt in, strict or warn (almost default but no deprecation warning)
+    * Would like to have a survey to get more opinions on what they would prefer
+      * blog post, followed by survey on what they would like as the default
+      * would also want to figure based on type of user.
+    * Ruben, will open an issue and work on the questions the first step.
+
+* Diagnostic WG mission, was surprised current content.
+  * Peter will submit PR to suggest a few modifications.
+
+* Who’s coming to summit
+  * Michael, Ruben and Peter from those in attendance.
+
+
+## Q&A, Other
+
+* Question (@wentout) about Async Storage and it’s connection to #107
+https://github.com/nodejs/node/pull/26540
+
+* No other questions this week
+
+## Upcoming Meetings
+
+* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
+
+
+