Skip to content

/ graylog2-server

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

Jump to bottom

Log more information about host machine during starting #1244

Closed
kroepke opened this issue Jun 11, 2015 · 1 comment
Closed

Log more information about host machine during starting #1244

kroepke opened this issue Jun 11, 2015 · 1 comment
Labels
infrastructure
Milestone
1.3.0

Comments

@kroepke
Copy link
Member

@kroepke kroepke commented Jun 11, 2015

To make it easier to understand performance issues, esp with contention and thread pool/count sizes, it is helpful to know how many cores the host machine actually has.

Print this, and potentially other information, like memory sizes, during startup.
@kroepke kroepke added this to the 1.2.0 milestone Jun 11, 2015
@bernd bernd removed this from the 1.2.0 milestone Aug 31, 2015
@kroepke
Copy link
Member Author

@kroepke kroepke commented Nov 3, 2015

At the very least we should use http://search.maven.org/#artifactdetails%7Corg.graylog.repackaged%7Cos-platform-finder%7C1.0%7Cjar to log the OS details.
@kroepke kroepke added this to the 1.3.0 milestone Nov 3, 2015
bernd added a commit that referenced this issue Nov 11, 2015
@bernd
Log operating system details on server startup
Loading status checks…
91bbaeb 
Fixes #1244
@bernd bernd mentioned this issue Nov 11, 2015
Merged
bernd added a commit that referenced this issue Nov 12, 2015
@bernd
Log operating system details on server startup
Loading status checks…
3b49808 
Fixes #1244
@bernd bernd closed this in 38b9912 Nov 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
infrastructure
Projects
None yet
Milestone
1.3.0
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@bernd @kroepke