- Development logs importance: Allow tracking progress, detecting problems, and investigating incidents. Value and advantages should be remembered and as many logs as possible preserved.
- Typical project problem: Managers want to optimize costs by decreasing development logs in services like Sentry/Rollbar, despite their value in collecting production errors.
- Data as project asset: Data is as important as code and people. Deleting collected data to save money is actually burning resources accumulated in the project.
- Necessity of event tracking data: Data from services like Sentry/Rollbar or Mixpanel is necessary to track project regressions and detect anomalies and trends.
- Retrospective analysis: Historic data can detect problems in the development process, such as repeated errors indicating ineffective bug fixing.
- GitLab repository example: Management decided to purge the GitLab repository, losing significant historical data and increasing bug investigation time despite the low cost of disk space.
- AI era and data importance: In the era of rapid AI advancement, data is more crucial. If a company focuses on disk space cost without using code analysis based on development history, it may miss potential profit.
- General point: This applies to all logs, not just analytics events and git.
**粗体** _斜体_ [链接](http://example.com) `代码` - 列表 > 引用
。你还可以使用@
来通知其他用户。