ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Sentry: Mask user messages in traces
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
User messages are currently visible in Sentry traces, raising privacy concerns. A 7-day trace retention is insufficient as NGOs may report issues after a week.
Describe the solution you'd like
- Investigate the feasibility of masking user messages in traces.
- If masking is not possible, configure trace retention to ~30 days.
- Document the decision as part of the ops/observability workstream.
Original issue
Context
User messages are currently visible in Sentry traces (not logs), which is a privacy concern.
Decision (to investigate)
Either:
- Mask user messages in traces, OR
- Set trace retention to ~30 days.
7-day retention is too short since NGOs sometimes raise issues after a week.
Acceptance criteria
- Determine feasibility of masking user messages in traces.
- If not masking, configure trace retention to ~30 days.
- Decision documented as part of the ops/observability workstream.
@vprashrex
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating how Sentry traces expose user messages and whether masking is feasible in the current ops/observability setup. If masking is not possible, assess configuring trace retention to about 30 days; document the decision and verify that the acceptance criteria are addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100