Diagnostics Use Case Survey 2019 #309
Description
Part of the use case and user journey driven diagnostics and best practices efforts we would like to collect information from the community about Node.js diagnostics use cases. We are planning to use the collected data to decide which diagnostics use-cases we will focus in the first round. The information will be also used to complete the Node.js WG Diagnostics User Journeys document and to help move out the document from the draft state.
Please see the proposal for the survey content:
https://docs.google.com/document/d/1T2hGtYcUxLiBZD29daDNvZkgRZi4YPNHwYqZ8YtT0yw/edit#heading=h.6wa1g9fvakxd
We are also looking for distribution channels.
Activity
gireeshpunathil commentedon Jun 24, 2019
@hekike - here are some points, feel free to incorporate
4.1 How frequently you get into production anomalies?
4.2 What do you do when your Node.js deployment has issues?
4.3 What is your knowledge level on Node.js diagnostics?
4.3 If we were to develop and deliver diagnostic best practices content, how do you want the format?
Section 5. Your Business with Node.js
5.1 How long you have been using Node.js?
5.2 How important Node.js is to your business?
Flarna commentedon Jun 24, 2019
Maybe add a question like "Are diagnostic/monitoring tools used continuously in production or only in case of problems".
mhdawson commentedon Jun 24, 2019
A few questions to add:
How many node instances do you have running in production
When you try to debug production issues do you use
Can you access for production environment directly?
If you cannot access your production environment directly how do you debug/get
information?
When you try to debug and fix production issues, what tools do you use?
What production issues have you most commonly run into?
hekike commentedon Jul 1, 2019
Thank you for sharing your thoughts, great ideas! I incorporated them into the docs.
Please take a look.
gireeshpunathil commentedon Jul 2, 2019
LGTM!
github-actions commentedon Jul 16, 2020
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.
mmarchini commentedon Jul 21, 2020
Did we share and gather results for this survey, or did it went stale? We could still send it if we want to.
github-actions commentedon Oct 19, 2020
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.