-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Diagnostics Use Case Survey 2019 #309
Comments
@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?
|
Maybe add a question like "Are diagnostic/monitoring tools used continuously in production or only in case of problems". |
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 When you try to debug and fix production issues, what tools do you use? What production issues have you most commonly run into?
|
Thank you for sharing your thoughts, great ideas! I incorporated them into the docs. |
LGTM! |
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. |
Did we share and gather results for this survey, or did it went stale? We could still send it if we want to. |
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. |
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.
cc @gireeshpunathil @mhdawson
The text was updated successfully, but these errors were encountered: