mozilla-services / mozilla-services/kent
handle sessions event
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 124
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
If I run socorro for a bit, I eventually see one of these in Kent:
{
"event_id":"ccb92246-db8a-47a8-ba2f-82e4127b0976",
"payload":{
"body":{
"aggregates":[
{
"exited":99,
"started":"2024-10-31T13:40:00.000000Z"
}
],
"attrs":{
"environment":"production",
"release":"none:unknown"
}
},
"envelope_header":{},
"header":{
"content_type":"application/json",
"length":132,
"type":"sessions"
}
},
"project_id":1
}
Kent captures these, but can't generate a summary. We should support these in summary.
Contributor guide
No contributing guide indexed for this repository
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 tracing how Kent handles the Sentry event type shown in the example and how existing events reach summary generation. Use the provided sessions payload as the reproduction case; done means Kent can generate a summary for sessions events instead of only capturing them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100