Skip to content
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

Closed
hekike opened this issue Jun 19, 2019 · 8 comments
Closed

Diagnostics Use Case Survey 2019 #309

hekike opened this issue Jun 19, 2019 · 8 comments
Labels

Comments

@hekike
Copy link
Contributor

hekike commented Jun 19, 2019

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

@gireeshpunathil
Copy link
Member

@hekike - here are some points, feel free to incorporate

4.1 How frequently you get into production anomalies?

  • none so far
  • couple of times an year
  • few times a month

4.2 What do you do when your Node.js deployment has issues?

  • try to debug and fix myself
  • report an issue in the ommunity
  • i have an internal node.js support team
  • i have an external node.js support vendor

4.3 What is your knowledge level on Node.js diagnostics?

  • zero, or little
  • moderate, I understand the Node.js excution environment
  • advanced, I know to use most of the tools, including crash diagnostics

4.3 If we were to develop and deliver diagnostic best practices content, how do you want the format?

  • as a long list of best practices
  • as a case study with real issue
  • as a story telling with lot of examples in it

Section 5. Your Business with Node.js

5.1 How long you have been using Node.js?

  • not yet, seriously considering
  • < 1 year
  • > 5 years

5.2 How important Node.js is to your business?

  • non-critical, used for trivial tasks with alternatives
  • minimal, but moderately improtant
  • a good share of my business depend on it
  • critical, node.js is startegically improtant for me.

@Flarna
Copy link
Member

Flarna commented Jun 24, 2019

Maybe add a question like "Are diagnostic/monitoring tools used continuously in production or only in case of problems".

@mhdawson
Copy link
Member

A few questions to add:

How many node instances do you have running in production

  • 5 or less
  • 5-20
  • 20-100
  • 100 or more

When you try to debug production issues do you use

  • JavaScript Debuggers
  • Native Debuggers
  • Other JavaScript tools
  • Operating system tools

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?

  • out of memory
  • crash
  • high cpu usage
  • hang
  • other

@hekike
Copy link
Contributor Author

hekike commented Jul 1, 2019

Thank you for sharing your thoughts, great ideas! I incorporated them into the docs.
Please take a look.

@gireeshpunathil
Copy link
Member

LGTM!

@github-actions
Copy link

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.

@github-actions github-actions bot added the stale label Jul 16, 2020
@mmarchini
Copy link
Contributor

Did we share and gather results for this survey, or did it went stale? We could still send it if we want to.

@mmarchini mmarchini removed the stale label Jul 21, 2020
@github-actions
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants