Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise): Community
• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): no

Context

• node version: 12
• module version: latest
• environment (e.g. node, browser, native): node
• used with (e.g. hapi application, another framework, standalone, ...): hapi app
• any other relevant information:

What problem are you trying to solve?

Reduce CPU usage

Do you have a new or modified API suggestion to solve the problem?

Don't poll memory usage if disabled

To allow single sampler with many policies

Perhaps change the return to be { isOverloaded, reason }

In hapi it would be nice when the load log is created if it includes the reason (https://github.com/hapijs/hapi/blob/master/lib/connection.js#L208)

In lib/index.js line 44
I believe that

this.settings = Hoek.applyToDefaults(internals.defaults, options);

should in fact be:

this.settings = Hoek.applyToDefaults(internals.defaults.process, options);

No big deal but was confusing when trying to understand the logic of the module.

Correct me if I'm wrong. Otherwise I can make a quick PR if you'd like.

It would be great if the README was updated with instructions on what this module is and how to use it.

Upgrade joi to 6.x.x

This would be useful to allow adding a custom callback to do things like monitoring/log every time a new sample is measured.

Support plan

• which support plan is this issue covered by? (e.g. Community, Core, Plus, or Enterprise): community
• is this issue currently blocking your project? (yes/no): no
• is this issue affecting a production system? (yes/no): kinda

Context

• node version: 12
• module version: latest
• environment (e.g. node, browser, native): node
• used with (e.g. hapi application, another framework, standalone, ...): hapi app
• any other relevant information:

How can we help?

What's a recommended setting for max event loop delay and sampling interval?

Also, if answered I can PR to include an explanation in the docs :)

Thank you!

When hapi hits the load directives and it hits the 503 condition, we should log what the reason for that is with the relevant stat so its clear what the issue is in the logs.

-Lloyd

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.