Create Ingestion Warning when invalid session id is provided
Open
Nobody has claimed this yet.
enhancement
feature/ingestion
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Feature request
Is your feature request related to a problem?
When a customer sends invalid session ids that don't match our requirements, we don't seem to warn them of this.
It would be good if we did a little more to warn them.
Describe the solution you'd like
At the very least, adding a section to ingestion warnings would be a start. Even better if we can properly put a banner at the top to warn them as well.
Describe alternatives you've considered
Additional context
Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
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 reading the linked custom session ID requirements and tracing where ingestion warnings are generated and displayed. Determine how invalid session IDs are detected, then confirm that the resulting warning appears in the ingestion warnings area and, if supported by the existing design, in the requested banner.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100