What does monit.memory actually represent?

Open
#5,391 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js

Research direction

Start with the PM2 API documentation and the source that assigns monit.memory; compare its value with the fields returned by process.memoryUsage(). Done means documenting the metric’s exact meaning and source in the API documentation so the question is resolved.

Written by the indexing model from the issue text.

Description

Looking at docs and source I can't figure out exactly how monit.memory is set - aka what does it represent?

Is it some attribute from the object returned from process.memoryUsage()?

Thanks in advance.

Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Unitech/pm2

All issues in Unitech/pm2

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.