Tips & strategies for interpreting Teleport debug traces #8160
Replies: 1 comment
-
When teleport is in debug mode, that simply means that it will output messages of every possible log severity to its logs. When troubleshooting, this is helpful since you get the most information possible from the logging. With teleport the log severities can be thought of generally as follows:
The teleport logs also include a component field, which helps identify which general subsystem is emitting the log. This appears in square brackets after the severity. Examples include The next item that appears in a log entry is a generic message. This could be a simple word or phrase. It could be a full multiline stacktrace. This is often helpful in determining what exactly happened. The stacktrace can be utilized to step through the code to see lots of details about what was happening when the stacktrace was encountered. Not all errors include a stacktrace. The last section of the logs is the file and line number from where the log message was emitted. This is helpful for investigating messages that don't include a stacktrace. Most of the time when debug mode is activated, there is some reason to extract as much information as possible about what is going on. The additional information helps give more clues to investigating the behavior that is in question. |
Beta Was this translation helpful? Give feedback.
-
Does anyone have tips for interpreting Teleport debug traces?
Beta Was this translation helpful? Give feedback.
All reactions