-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Log system information early during startup #124926
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Information about the system, and in particular the running JVM, is logged relatively late in startup. When problems occur in low level initialization, it is often useful to have this information. This commit moves logging of system information to right after logging has been initialized. Note that it no longer utilizes the JvmInfo class as most was already easily available and the static init of JvmInfo does a lot.
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
ldematte
approved these changes
Mar 14, 2025
Contributor
ldematte
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Member
Author
|
@elasticmachine update branch |
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Mar 15, 2025
Information about the system, and in particular the running JVM, is logged relatively late in startup. When problems occur in low level initialization, it is often useful to have this information. This commit moves logging of system information to right after logging has been initialized. Note that it no longer utilizes the JvmInfo class as most was already easily available and the static init of JvmInfo does a lot.
Collaborator
💔 Backport failed
You can use sqren/backport to manually backport by running |
elasticsearchmachine
pushed a commit
that referenced
this pull request
Mar 15, 2025
Information about the system, and in particular the running JVM, is logged relatively late in startup. When problems occur in low level initialization, it is often useful to have this information. This commit moves logging of system information to right after logging has been initialized. Note that it no longer utilizes the JvmInfo class as most was already easily available and the static init of JvmInfo does a lot.
mosche
pushed a commit
to mosche/elasticsearch
that referenced
this pull request
Jul 24, 2025
Information about the system, and in particular the running JVM, is logged relatively late in startup. When problems occur in low level initialization, it is often useful to have this information. This commit moves logging of system information to right after logging has been initialized. Note that it no longer utilizes the JvmInfo class as most was already easily available and the static init of JvmInfo does a lot. (cherry picked from commit 789eb2f) # Conflicts: # server/src/main/java/org/elasticsearch/bootstrap/Elasticsearch.java # server/src/main/java/org/elasticsearch/node/NodeConstruction.java
mosche
pushed a commit
to mosche/elasticsearch
that referenced
this pull request
Jul 24, 2025
Information about the system, and in particular the running JVM, is logged relatively late in startup. When problems occur in low level initialization, it is often useful to have this information. This commit moves logging of system information to right after logging has been initialized. Note that it no longer utilizes the JvmInfo class as most was already easily available and the static init of JvmInfo does a lot. (cherry picked from commit 789eb2f) # Conflicts: # server/src/main/java/org/elasticsearch/bootstrap/Elasticsearch.java # server/src/main/java/org/elasticsearch/node/NodeConstruction.java
Contributor
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jul 28, 2025
Information about the system, and in particular the running JVM, is logged relatively late in startup. When problems occur in low level initialization, it is often useful to have this information. This commit moves logging of system information to right after logging has been initialized. Note that it no longer utilizes the JvmInfo class as most was already easily available and the static init of JvmInfo does a lot. (cherry picked from commit 789eb2f) # Conflicts: # server/src/main/java/org/elasticsearch/bootstrap/Elasticsearch.java # server/src/main/java/org/elasticsearch/node/NodeConstruction.java Co-authored-by: Ryan Ernst <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jul 28, 2025
Information about the system, and in particular the running JVM, is logged relatively late in startup. When problems occur in low level initialization, it is often useful to have this information. This commit moves logging of system information to right after logging has been initialized. Note that it no longer utilizes the JvmInfo class as most was already easily available and the static init of JvmInfo does a lot. (cherry picked from commit 789eb2f) # Conflicts: # server/src/main/java/org/elasticsearch/bootstrap/Elasticsearch.java # server/src/main/java/org/elasticsearch/node/NodeConstruction.java Co-authored-by: Ryan Ernst <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport
Automatically create backport pull requests when merged
backport pending
:Core/Infra/Core
Core issues without another label
>refactoring
Team:Core/Infra
Meta label for core/infra team
v8.18.1
v8.19.0
v9.0.1
v9.1.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Information about the system, and in particular the running JVM, is logged relatively late in startup. When problems occur in low level initialization, it is often useful to have this information. This commit moves logging of system information to right after logging has been initialized. Note that it no longer utilizes the JvmInfo class as most was already easily available and the static init of JvmInfo does a lot.