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

Provide threshold to automatically trigger dump creation #70

Open
tobespc opened this issue Apr 18, 2017 · 2 comments
Open

Provide threshold to automatically trigger dump creation #70

tobespc opened this issue Apr 18, 2017 · 2 comments

Comments

@tobespc
Copy link
Member

tobespc commented Apr 18, 2017

As well as being able to manually request a dump, can we add some configurable thresholds that if reached (mem > xxxx for example) a dump is automatically triggered

@sam-github
Copy link
Contributor

Seems like a useful feature of appmetrics itself, or some addon, but shouldn't require a UI dashboard. In particular, it shouldn't involve UI interaction with every single uservice after it comes up to configure the threshold. Would be nice to have this feature be remotely accessible via protocol, and to be configurable via env var.

This would be an easy feature to add into strong-supervisor, but it seems like it is more fundamental than that. If we aren't recommending strong-supervisor for all runtimes, then the feature should be in appmetrics, or at least easy to add to appmetrics.

/to @cvignola, because liberty has similar features to this, and its the kind of feature that should be available uniformly in docker-deployed node.js runtimes, as well as bluemix.

@tobespc
Copy link
Member Author

tobespc commented Apr 19, 2017

The core feature to do the actual triggering and would be in appmetrics. The UI would be able to configure it live for those users who do not want to use the api. For other use cases, we would have it configurable via the api/config files

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

No branches or pull requests

2 participants