Add categorized protocol error view
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- javascript
- 领域
- frontend
调研方向
从 /settings/admin/logging 视图开始，跟踪协议条目的显示方式。查看请求的分组示例，并确定如何对重复错误进行分类，同时保留各条单独的消息和完整的日志视图。完成的标准是，管理员无需手动扫描或使用单独的日志扫描器即可识别只出现一次的错误。
由索引模型根据 Issue 内容生成。
描述
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
We are currently hosting a big nextcloud with a lot of users, causing a lot of protocol messages:
24580 Fehler in den Protokollen seit 8. April 2024 (24580 errors in protocol since 8. April 2024)
A lot of errors are just the same:
InsufficientStorage Insufficient space in /some/users/directory, 49303676 required, 48654 availableLogin failed: 'test1' (Remote IP: '10.20.30.40')LocalServerException No DNS record found for owncloud.mathematik.tu-dortmund.de error while discovering ocm provider(some app warning I couldn't care less about)TooManyRequests Exception thrown: OCA\DAV\Connector\Sabre\Exception\TooManyRequests Exception thrown: OCA\DAV\Connector\Sabre\Exception\TooManyRequests- some more ....
Describe the solution you'd like
There are just errors/warning flying in at /settings/admin/logging and I would like to have them categorized in the view, there is no point in seeing the same errors over and over again, some bigger mistakes are hidden between them and the current solution is to manually search in the logs. So additionally to the full log view I would like to have them categorized by the main exception, and then, maybe listed in a sub menu (or spoiler style?) list them individually. This way I can see errors that only occurred once without using a dedicated log scanner.
Example:
Login failed (CLICK ME)
'test1' (Remote IP: '10.20.30.40')
'test2' (Remote IP: '10.20.30.42')
InsufficientStorage (CLICK ME)
Insufficient space in /some/users/directory, 49303676 required, 48654 available
Insufficient space in /someother/users/directory, 49303676 required, 48654 available
Describe alternatives you've considered
Alternatively I'd like to ignore/disable some errors:
- if the user exceeds his storage quota I don't need an exception for this
- if somebody is sending too many requests I don't need an exception for this
- If somebody fails his login, I don't need an exception for this
Additional context
- 主要语言
- JavaScript
- 星标
- 71
- 派生
- 30
- 平均合并
- 10 小时 12 分钟
- 30 天内合并 PR
- 98
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nextcloud/logreader 的其他 Issue
-
0. Needs triage bug
难度 1/5 1 小时以内 新手友好度 66/100
维护者通常 1 天内回复
-
Display Filtering is very slow and results in extreme CPU usage spikes on server可能已有人在做 @Antreesy 于 143 天前认领。 未关闭0. Needs triage bug
难度 4/5 3-5 天 新手友好度 48/100
nextcloud/logreader#2045 · 5 条评论 ·
维护者通常 1 天内回复
-
0. Needs triage bug
难度 3/5 1-2 天 新手友好度 35/100
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 25/100
维护者通常 1 天内回复
-
0. Needs triage bug
难度 3/5 1-2 天 新手友好度 42/100
维护者通常 1 天内回复
查看 nextcloud/logreader 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
swc-project/swc-next#1165 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
nhsuk/nhsuk-prototype-kit-package#439 ·
维护者通常 1 天内回复
-
Add: &TV Logo未关闭check:passed logos:add
难度 1/5 1 小时以内 新手友好度 74/100
-
BUG: Appointment time renders blank and PM appointment slots miscalculate vertical position in CalendarScreen可能已有人在做 @aryanpatil-07 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
AOSSIE-Org/BabyNest#297 · 1 条评论 ·
维护者通常 1 天内回复
-
Onboarding form: instructor radio never pre-selected "Yes" (permission vs permissions typo)可能已有人在做 @ThakuraAnki 今天认领。 未关闭bug
难度 1/5 1 小时以内 新手友好度 72/100
WikiEducationFoundation/WikiEduDashboard#7235 ·
维护者通常 1 天内回复