1.8 Alpha3 - Statistics

cslaughter · April 14, 2016, 6:06pm

Wondering about statistics on 1.8 Alpha3… We see a ton of data in the Stat table, but we don’t see media showing on the Statistics page, or via the API:

In the CMS we only see the Layout, which I would love to know how to query via the API, and media. But media is actually not media… not sure what that should be.

Second problem, we are not sure if we introduced or Alpha3 introduced this, but the dates if not predefined via the API, revert to 1969. (Better than the 1899 that we had in Alpha1) I thought at some point that reverted to 30 days in the past thru today. Am I wrong on this?

cslaughter · April 14, 2016, 7:01pm

We ran the same exact Postman test not even 5 minutes later and got this:

Still not all the data that we believe should be there.

dan · April 15, 2016, 6:32am

We don’t seem to be able to get this right do we! It should be the case that if the fromDt and toDt parameters are missing entirely then they default:

fromDt = now - 1 day
toDt = now

@Peter - can you make this your next test for the test suite please? Seems to keep regressing for some reason.

cslaughter · April 15, 2016, 3:41pm

The problem with 1969 is ours.

fromDt and toDt do not appear to work, CMS shows the same thing as I posted above.

Peter · April 18, 2016, 8:22am

Interesting, from what I can say about alpha3 and my tests it does work just fine here.

API:
ie without any filters it seems to be like Dan said
and all filters works ok (displayid, media id and the from/to)

CMS:
It seems correct here too, one thing is that it doesn’t refresh when I change the date alone (@dan enhancement perhaps? ) so I need to change for example the display to make it refresh and then it shows correct data.

cslaughter · April 19, 2016, 4:00pm

Stats are not working for us for some reason. CMS and API.

I will focus on the CMS since, I think if it doesn’t work for us there, it probably will not work via the API either.

In the CMS v1.8 Alpha3, we have two screens connected and displaying content as they should. In the Display settings, for Android, we have the option “Enable stats reporting?” checked. Both the screens connected are Android clients. Once is running R59 and the other R60. Each screen is running a different layout with multiple items, with video and/or image files. Layouts show good. Both show normal in the CMS as far as media downloaded and whatnot. Status screen on both looks good.

The “Stats” table in the database has about 57,000 records. This is what we see in the CMS:

NOTE: The screen shots show that the First Shown and Last Shown are only for roughly 24 hours. The media has been playing much longer than that. At least a week in this case.

cslaughter · April 19, 2016, 4:24pm

What is interesting is the log. Here is the first 100 post for the run:

121604	a5f1869	2016-04-19 09:15	XMDS	POST	INFO	Big Screen	SubmitLog	PDO stats: {"connections":2,"selects":2,"inserts":0,"updates":1}.
121603	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:53,,,
121602	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:07:40,,,
121601	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:40,,,
121600	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:07:40,,,
121599	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:40,,,
121598	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,failed to connect to /10.0.1.103 (port 80) after 10000ms: isConnected failed: EHOSTUNREACH (No route to host),Client,XmdsBase,2016-03-20 06:07:39,,,
121597	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:07:27,,,
121596	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:27,,,
121595	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:27,,,
121594	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:07:27,,,
121593	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:07:14,,,
121592	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:14,,,
121591	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:07:14,,,
121590	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:14,,,
121589	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:07:01,,,
121588	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:01,,,
121587	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:07:01,,,
121586	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:07:01,,,
121585	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:06:48,,,
121584	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:06:48,,,
121583	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:06:48,,,
121582	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:06:48,,,
121581	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:06:35,,,
121580	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:06:35,,,
121579	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:06:35,,,
121578	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:06:35,,,
121577	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:06:22,,,
121576	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:06:22,,,
121575	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:06:22,,,
121574	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:06:22,,,
121573	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:06:09,,,
121572	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:06:09,,,
121571	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:06:09,,,
121570	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:06:09,,,
121569	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:05:56,,,
121568	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:56,,,
121567	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:56,,,
121566	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:05:56,,,
121565	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:05:43,,,
121564	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:43,,,
121563	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:43,,,
121562	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:05:43,,,
121561	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:05:30,,,
121560	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:30,,,
121559	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:30,,,
121558	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:05:30,,,
121557	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:05:17,,,
121556	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:17,,,
121555	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:05:17,,,
121554	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:17,,,
121553	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:05:04,,,
121552	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:04,,,
121551	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:05:04,,,
121550	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:05:04,,,
121549	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:04:51,,,
121548	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:04:51,,,
121547	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:04:51,,,
121546	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:04:51,,,
121545	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:04:38,,,
121544	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:04:38,,,
121543	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:04:38,,,
121542	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:04:38,,,
121541	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:04:25,,,
121540	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:04:25,,,
121539	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:04:25,,,
121538	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:04:25,,,
121537	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:04:12,,,
121536	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:04:12,,,
121535	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:04:12,,,
121534	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:04:12,,,
121533	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:03:59,,,
121532	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:59,,,
121531	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:03:59,,,
121530	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:59,,,
121529	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:03:46,,,
121528	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:46,,,
121527	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:03:46,,,
121526	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:46,,,
121525	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,failed to connect to /10.0.1.103 (port 80) after 10000ms: isConnected failed: EHOSTUNREACH (No route to host),Client,XmdsBase,2016-03-20 06:03:39,,,
121524	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:03:33,,,
121523	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:33,,,
121522	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:33,,,
121521	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:03:33,,,
121520	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:03:20,,,
121519	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:20,,,
121518	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:03:20,,,
121517	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:20,,,
121516	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:03:07,,,
121515	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:07,,,
121514	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:03:07,,,
121513	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:03:07,,,
121512	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:02:54,,,
121511	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:02:54,,,
121510	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:02:53,,,
121509	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:02:53,,,
121508	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Default Layout failed: canRun Test,Client,DisplayManager,2016-03-20 06:02:40,,,
121507	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:02:40,,,
121506	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	audit,Layout 3 cannot run as it has a region without any media assigned,Client,Region,2016-03-20 06:02:40,,,
121505	a5f1869	2016-04-19 09:15	XMDS	POST	NOTICE	Big Screen	SubmitLog	error,Cannot set the next Layout from the Schedule. Schedule Invalid,Client,DisplayManager,2016-03-20 06:02:40,,,

It seems to be complaining about a lot. The layout it says contains an empty region, is simply not right. Here is the layout:

Update: Sorry, I noticed I uploaded a screen shot of the wrong screen, it now shows the correct screen in the picture above.

Also note, that it can and does connect to the CMS just fine. So I am also not sure why the errors about connection. Both the CMS and client are on the same local network.

UPDATE: I also check the “region” table to make sure that I did not see multiple entries for the layout ID in questions. ( Just to make sure I was not missing an empty region that the designer was not alerting me to) I only see one entry for the layout.

UPDATE2: The dates on when things were logged are about a month old… Why are the logs not being cleared? Is this why the stats are not showing correctly in the CMS? Why would some stats be making it through? Date and time on both screens are correct. The stats in the log should have been downloaded and cleared when we were running alpha 2 with these screens. We did a fresh install of Alpha 3.

Update3: Is this possible? The date from the old logs, is right about the time we switched from the standard Xibo Android Client to the Whitelabel Android Client. We know that Android treats these two as separate apps. But would they share the same log location/file? If so, is it possible that the whitelabel version can read the file, but not write or update the file? Thus producing the problem we see? We can test this theory if someone can tell us which file it is we should delete, assuming it would be automatically recreated.

cslaughter · April 19, 2016, 6:47pm

I think this may play into my first problem, but not sure.
Second Stats problem… Inconsistent results in CMS

I brought up the CMS Statistics page and set the From Date to 2016-04-01 XX:XX, To Date to 2016-04-19 XX:XX, Display to “Big Screen” and got this:

I then change Display to another screen, and then back to “Big Screen” and got this:

dan · April 20, 2016, 7:51am

I can’t explain this at present - logs should be cached player side for a maximum of 10 days before they are cleared out. You clearly have logs from beyond that being sent, so i’ve made a note to investigate.

Logs and Stats are separate so I don’t think so.

Good idea - but no this is not possible.

I believe we still have access to your CMS? @Peter can we get connected and have a look please?

Peter · April 20, 2016, 7:56am

We do, but not to 1.8alpha3, so @cslaughter if it’s possible for us to have a look at your 1.8 CMS, please let me know via pm.

dan · April 21, 2016, 12:52pm

Its very odd Colin - your CMS had a JavaScript error on the statistics page which was preventing the filter form from correctly rendering (meaning it would not allow selection of dates).

I need to investigate the root cause of this error, because its not obvious.

I cleared the error, refreshed and was then able to selected a from/to date - from that point onwards the stats were returned as expected.

The above JavaScript error would not have effected your API calls, so I would have expected them to be OK.

cslaughter · April 21, 2016, 8:24pm

Interesting… I guess that is why it would also returns different results at different times.

Seems like we have at least two problems, maybe 3 coming together to really give us some fun.

dan · April 22, 2016, 7:44am

There were 3 issues all together which I suspect confused the issue for you. However none of these issues effect the API or the core values returned - so I think we will have to look there next.

Setting the filter form saved values was failing and knocking out subsequent javascript
The grid was loading first time before the saved values were populated
The date pickers didn’t trigger a form refresh

cslaughter · April 22, 2016, 11:49pm

Much better Thank you.

Our API data now matches what we see in the CMS.

I think the last two problems that I see right now are with 1 Android unit we have here polluting the data.

I am not sure how or why this unit is not clearing the old data. Also it is reporting data from the Alpha 2 install we had before installing Alpha3. So the layout and media IDs have changed and it is reporting that it is playing the wrong layout, when in all actuality the data is old and the layout being recorded is not actually the one matching the layout’s ID. (I think maybe a installation CMS ID being sent with the logs could fix this?) I think this also explains why some entries would show up with no name, as the media IDs do not exist in the new installation. ( I think this goes back to another post about getting Stats from units transferred between CMS servers, and the old stats being included on the database the unit was transferred to.
Android 1.7.5 Connecting to New CMS, Old Stats Being Transfered)

Dan, Peter, I am not sure if you guys want any data from the Android this unit before we re-image it to correct it’s problem. Please let me know.

dan · April 23, 2016, 9:51am

The stats should be completely truncated when the CMS address, CMS key or Hardware key changes on the player - this is part of the same logic that tells the player to re-register when those items change. I suppose your CMS address hasn’t changed when you reinstalled?

Under routine operation I wouldn’t expect the stats to be cleared on CMS upgrade.

Its the logs that clear, rather than the stats - so I would expect the device to continue sending old stats data.

All of that being said, we do have an item to look at how this will work going forwards. The current mechanism of sending 100 stat records during collection was a reasonable way of operating before XMR - however now that the collection interval should be set much higher, the chance that a player will fall behind with its stats reporting is much greater.

I would suggest that you re-image the unit and we look to address this issue as part of the larger concern above.

cslaughter · April 23, 2016, 7:02pm

Correct.

The only trouble I see is in a situation, like we did, where a CMS server is lost/replaced and a new instance of the CMS installed. The address would be the same, but the CMS instance is not.

Sounds like this will be addressed.

Thank you guys for the great support, your time, and patience.

One last question for now on Stats:

How can we ask for a layout’s stats?

cslaughter · April 24, 2016, 6:04pm

Well we thought we had everything working. Turns out we see a number of other problems. ( We did completely re-image the device that was polluting our data.)

We noticed that when media is removed from layouts, you do not seem to be able to search and get stats on the media any longer. In this image we are searching for media that has been playing on two layouts for over a week. Once we removed the media from both layouts and then try to search the stats we get this:

We also noticed some inconsistencies on the times:

When we try to search for stats on individual media via the API we do not get what we expect. It seems to return some random media:

dan · April 25, 2016, 7:16am

You can’t yet - we need to add a layoutId filter option.

Hence the suggestion of an installation id? Complete reinstall would regenerate the installation key but an upgrade wouldn’t. It’s quite a big bit of work for an edge case - we will give it some thought.

As for the other items - something is still odd as you say… we will look into it.

dan · April 25, 2016, 11:27am

I understand the issue with mediaId’s but unfortunately I am not sure how to solve it at present. For the time being removing a media item from the layout will also remove it from the stats - obviously it would be good to solve that and we will think about how to achieve it.

cslaughter · April 26, 2016, 4:56am

Correct. A player could send the installation ID back with all communications, which it would grab on registration with the CMS. If the CMS was re-installed at the same address, the new CMS could basically just not record the data that does not match it’s ID, and then send it’s installation ID to the display. (No need to keep the old stats, because they would not match anything in the database to begin with and just pollute the data. This would also allow for changing of URLs of a server and not losing that data as was brought up in the this post Android 1.7.5 Connecting to New CMS, Old Stats Being Transfered)

Thank you.