Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Send data to Pillarbox QoS backend #961

Closed
4 of 5 tasks
defagos opened this issue Aug 7, 2024 · 0 comments · Fixed by #1042
Closed
4 of 5 tasks

Send data to Pillarbox QoS backend #961

defagos opened this issue Aug 7, 2024 · 0 comments · Fixed by #1042
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@defagos
Copy link
Member

defagos commented Aug 7, 2024

As a Pillarbox QoS backend developer I need to receive QoS data from Pillarbox player so that I can create dashboards based on real data.

Hints

Android and web players will send monitoring data for URLs and URNs. We won't do the same on Apple platforms since this would force monitoring at the PillarboxPlayer level (apps can still decide to attach a tracker if needed).

Acceptance criteria

  • Metrics data associated with SRG SSR content is visible on Pillarbox metrics dashboards.

Tasks

@defagos defagos added this to Pillarbox Aug 7, 2024
@defagos defagos converted this from a draft issue Aug 7, 2024
@defagos defagos added the enhancement New feature or request label Aug 7, 2024
@defagos defagos moved this from ✏️ Draft to 📋 Backlog in Pillarbox Aug 7, 2024
@defagos defagos added this to the QoS milestone Aug 7, 2024
@defagos defagos moved this from 📋 Backlog to 🚧 In Progress in Pillarbox Sep 26, 2024
@waliid waliid linked a pull request Oct 10, 2024 that will close this issue
4 tasks
@github-project-automation github-project-automation bot moved this from 🚧 In Progress to ✅ Done in Pillarbox Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

2 participants