y-scope / yscope-log-viewer

A tool that can be used to view logs compressed in CLP's IR Stream format.
Apache License 2.0
11 stars 12 forks source link

docs: Add user docs for opening log files, level filtering, and formatting structured logs. #132

Closed davemarco closed 4 days ago

davemarco commented 5 days ago

Description

This PR is a starting point for the user guide. More can be added later.

I added sections for opening files, format string, and log level filtering.

For the format string. I added a simple example for the overview (I thought including only the full spec might overwhelm users). I also kept the full spec in another page. I also added a list of current field formatters.

Validation performed

Docs still work.

Summary by CodeRabbit

coderabbitai[bot] commented 5 days ago

Walkthrough

The pull request introduces substantial updates to the user guide for the YScope Log Viewer, enhancing both its structure and content. It replaces placeholder text with a grid layout featuring three informative cards linked to relevant documentation sections. Additionally, new documentation is added on formatters, log formatting capabilities, syntax for format strings, and log-level filtering methods. The .gitattributes file is updated to manage PNG files with Git LFS, and a new section on viewing logs is introduced, detailing how to access both local and remote log files.

Changes

File Path Change Summary
docs/src/user-guide/index.md Replaced placeholder text with a structured grid layout including links to "Quick start," "Formatting structured logs," and "Log level filtering." Added toctree directives for better organization.
docs/src/user-guide/.gitattributes Added configuration for PNG image files to be handled by Git LFS with appropriate attributes.
docs/src/user-guide/format-struct-logs-formatters.md Introduced a new section detailing the Timestamp and Round formatters, including usage examples.
docs/src/user-guide/format-struct-logs-overview.md Added an overview of the log viewer's capability to format structured logs with examples and references.
docs/src/user-guide/format-struct-logs-syntax.md Created a comprehensive guide on format string syntax, detailing components and providing examples.
docs/src/user-guide/log-level-filtering.md Updated to include methods for filtering logs by severity levels, illustrated with images.
docs/src/user-guide/quick-start.md Added a new section on "Viewing logs," detailing how to open local and remote log files.

Possibly related PRs

Suggested reviewers


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
kirkrodrigues commented 4 days ago

The suggestions lgtm. Feel free to commit them so that you remain the last pusher.

junhaoliao commented 4 days ago

For the PR title, how about:

docs: Add user docs for opening log files, level filtering, and formatting structured logs.

Can we also add (fixes #86) in the PR title?

davemarco commented 4 days ago

@junhaoliao technically, this dosent fix 86? it was already fixed by another PR. These docs just refer to nested logs.

junhaoliao commented 4 days ago

@junhaoliao technically, this dosent fix 86? it was already fixed by another PR. These docs just refer to nested logs.

Right, we could have closed issue #86 in PR #123 , but now the docs are added which completes the feature. Anyways, the PR and the issue has now been linked and i think it's fine not mentioning the issue in this PR title.