If you're asked to provide logs, zip up the entire folder to ensure that the correct logs are included. For example, the Notebooks output channel may output to a file named 3-Notebooks.log. exthost#/output_logging_#: these folders contain the messages displayed in the Output panel in Azure Data Studio.sqltools.log is the log for SQL Tools service.exthost#/Microsoft.mssql: Logs for the mssql extension, which contains much of the core logic for MSSQL-related features.exthost#/exthost.log: Log file for the extension host process (this is only the process itself, not the extensions running inside it).telemetry.log: When the log level is set to Trace, this file contains the telemetry events sent by Azure Data Studio.renderer#.log (for example, renderer1.log): this file is the log file for the main process.There are many different types of log files that write there. Azure Data Studio logs and locationįrom the Command Palette (Ctrl/Cmd + Shift + P), run the Developer: Open Logs Folder command to open the path to the logs. The Mssql: Tracing Level user setting is used to control the verbosity of the logging. If the Mssql: Log Debug Info user setting is set to true, then debug log info is sent to the MSSQL output channel. If you want to enable debug logging for startup then set the log level to Debug and run the Developer: Reload Window command. If you restart Azure Data Studio, it reverts back to the default Info level. This value isn't persisted over multiple sessions. command to select the log level for the current session. Simplify your code around the issue so we can better isolate the problem.ĭon't feel bad if we can't reproduce the issue and ask for more information! How to set the logging level Azure Data Studioįrom the Command Palette (Ctrl/Cmd + Shift + P), run the Developer: Set Log Level.Search the issue repository to see if the same issue already exists.Errors in the Dev Tools Console ( Help > Toggle Developer Tools).A code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue.īecause we need to copy and paste the code snippet, including a code snippet as a media file (that is.Images and animations illustrate repro-steps but don't replace them. Images, animations, or a link to a video.3.) and what you expected versus what you actually saw. Include the following information with each issue: The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix. Many issues look similar, but have different causes. ![]() ![]() Don't add your issue as a comment to an existing issue unless it's for the identical input.Don't enumerate multiple bugs or feature requests in the same issue.Write good bug reports and feature requestsįile a single issue per problem and feature request. Include any log information from the log file. Report issues to GitHub Issue Tracker and let us know any details that help reproduce the error. Azure Data Studio tracks issues and feature requests using on a GitHub repository issue tracker for the azuredatastudio repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |