No Data After Configuring a Streaming Media Monitoring Task

Problem description

The customer monitored the video stream, configured streaming the media, and found that there was a problem with Availability and the data amount, which was quite different.
① It was found that the data returned and the data sent were not equal. Compared with before, the amount of data was significantly smaller;
②The task data was normal before, but suddenly there were a large number of Error;
As shown in the picture:

Troubleshooting

First check whether the distribution and collection are normal.
Through the background data, it was found that the distribution was normal, but there was a problem with the collection. When it was put into the database, half of it was missing;

2. Through background investigation, the missing data is because the data is noisy data.

Cause of the problem

By looking at the mark noise data, the reason is because when accessing the customer page, the Error code thrown is 660

Corporate WeChat screenshot_e93791f6-16ab-48f7-a8c8-0835f57d3c96(1).webp

Because settings are a streaming media task, one thing must be determined first. For this Task Type, it is to test whether the streaming video stream can be opened. The URL monitored by the customer does not reach the video stream, but an error is reported when the page is opened, and error 660 is reported. It has not been played yet, so such data is meaningless for streaming tasks, so the noise is marked and filtered.

Solution

Solve the problem of page error 660, and the streaming media task data is normal

If you want to monitor 660Error without filtering, you can use the page task settings. The page task can monitor 660Error, but it will not mark a red dot because 660 is not in our Error library.

No Data After Configuring a Streaming Media Monitoring Task

Problem description#

Troubleshooting#

Cause of the problem#

Solution#

Problem description

Troubleshooting

Cause of the problem

Solution