The reason the data was marked as noise is that error code 660 was returned when the customer page was accessed.For a streaming media task, the key objective is to verify whether the media stream can be opened. In this case, the monitored URL returned error 660 while opening the page before reaching the actual media stream. Since playback had not started, this data is not meaningful for a streaming media task, so it was marked as noise and filtered out.
Resolve the page-level 660 error. After the page error is fixed, the streaming media task data should return to normal.
2.
To monitor 660 errors without filtering them, configure a page task instead. Page tasks can report 660 errors, but they do not mark the point in red because 660 is not included in the Tingyun error library.
