June 14, 2017 at 17:57Statistics collection service with Flussonic
Hello everyone, I want to tell you about our first service that we are going to provide to our customers: statistics collection and reports .
For many years we only sold software, now we have prepared to launch a service for collecting statistics and providing reports. They take Flussonic from us, launch it on their servers, subscribers watch videos from these Flussonic instances and create recordings of viewing sessions.
These sessions just merge into our service and we will show the reports made on them in your account .
It turns on easily: in your account there is a large button "Enable statistics". After clicking a minute later, Flussonic will start sending us sessions and they will be stored securely.
At the moment, we will give only the most basic reports: distribution by country, by browser (and other devices), by channel. We can give both a crude list of sessions and aggregate similar to each other: For two weeks of closed testing, we still have a modest billion records , but we are confident that we can cope with a volume of 100 times more: for now, we can show very quickly even unique sessions, and this is a very expensive report. Specifically, in this screenshot, I showed how gluing similar sessions into unique ones, i.e. if from the same address, with the same User Agent, they tried to look at the same thing for a narrow period of time, then most likely this is one session, just poorly taken into account.
We have already encountered the very unpleasant problem of parsing the User Agent header: after all, we have a lot of set-top-boxes and other similar things, and they are not in the usual browser databases.
An unexpected problem with MaxMind also surfaced: you can’t just buy from them a complete database and show you the search results on it, it requires a special license from $ 30,000.
But this is all true, the problems are being solved, and we are working with all this now.
A separate moment with a javascript face: this is a SPA React application that lives in a separate microservice along with the service itself. We are not the first component to do this: javascript, css live and develop with the service backend itself and the user is connected with a simple javascript insert. There are tricks with authorization, because we want to not only inform the account, but at the same time its access rights, so the authorization session opens when a user logs into his personal account through interserver interaction.
We have many plans for the future:
If someone wants to try, feel, but have not yet launched Flussonic, then we will gladly give a free trial .
And, by the way, it’s important: we are going to do statistics collection and reports for free!
For many years we only sold software, now we have prepared to launch a service for collecting statistics and providing reports. They take Flussonic from us, launch it on their servers, subscribers watch videos from these Flussonic instances and create recordings of viewing sessions.
These sessions just merge into our service and we will show the reports made on them in your account .
It turns on easily: in your account there is a large button "Enable statistics". After clicking a minute later, Flussonic will start sending us sessions and they will be stored securely.
At the moment, we will give only the most basic reports: distribution by country, by browser (and other devices), by channel. We can give both a crude list of sessions and aggregate similar to each other: For two weeks of closed testing, we still have a modest billion records , but we are confident that we can cope with a volume of 100 times more: for now, we can show very quickly even unique sessions, and this is a very expensive report. Specifically, in this screenshot, I showed how gluing similar sessions into unique ones, i.e. if from the same address, with the same User Agent, they tried to look at the same thing for a narrow period of time, then most likely this is one session, just poorly taken into account.
Some details
We have already encountered the very unpleasant problem of parsing the User Agent header: after all, we have a lot of set-top-boxes and other similar things, and they are not in the usual browser databases.
An unexpected problem with MaxMind also surfaced: you can’t just buy from them a complete database and show you the search results on it, it requires a special license from $ 30,000.
But this is all true, the problems are being solved, and we are working with all this now.
A separate moment with a javascript face: this is a SPA React application that lives in a separate microservice along with the service itself. We are not the first component to do this: javascript, css live and develop with the service backend itself and the user is connected with a simple javascript insert. There are tricks with authorization, because we want to not only inform the account, but at the same time its access rights, so the authorization session opens when a user logs into his personal account through interserver interaction.
Plans
We have many plans for the future:
- make separation in statistics on interserver traffic and traffic to clients
- help catch those who share the account with friends, as well as those who are engaged in restriming
- add information about the depth of viewing the archive, etc.
If someone wants to try, feel, but have not yet launched Flussonic, then we will gladly give a free trial .
And, by the way, it’s important: we are going to do statistics collection and reports for free!
Only registered users can participate in the survey. Please come in.
What would you be interested in from the statistics of a video streaming server?
- 46.6% user device information 7
- 33.3% knowledge of user preferences for content 5
- 46.6% content consumption details 7
- 53.3% increased anomaly control 8
- 26.6% reconciliation of statistics with counterparties 4
- 13.3% something else, I will write in the comments 2
