Skip to content

docs: explain application log level and component filters #32

Closed

Description

@Quick104

Silo-Server/silo-server#1568 adds a Level filter to Admin > Logs > Application and component suggestions while keeping the component field editable. Update src/content/docs/docs/running-a-server/logging.md (/docs/logging) after that PR merges.

In View logs, describe:

  • Level offers debug, info, warn, and error; All levels clears the filter.
  • Component suggests known values and accepts exact names such as apiv2 or notifications.fanout. Clear the field to show all components.
  • Both filters apply to live logs and Browse log history, and remain in the URL for sharing or reloading.

Keep the distinction between viewing debug entries and the opslog.capture_level collection threshold. This changes the web admin controls; it needs no Apple, Android, or Jellyfin client documentation changes.

Written with gpt-6-astra in T3 Code using the Codex provider.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions