It can fill up the logs quite easily when there are lot of scheduled
scripts running @ low intervals.
As an alternative,
Make it a DEBUG & have an UI option to see when was the script last ran.
eg:
[2015-12-18 13:05:34,067] INFO
{org.wso2.carbon.device.mgt.iot.controlqueue.mqtt.MqttSubscriber} -
Subscribed with client id: f9560:virtual_firealarm
[2015-12-18 13:05:34,067] INFO
{org.wso2.carbon.device.mgt.iot.controlqueue.mqtt.MqttSubscriber} -
Subscribed to topic: WSO2IoTServer/+/virtual_firealarm/+/publisher
[2015-12-18 13:06:00,002] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Accelerometer_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,002] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Battery_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,003] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: GPS_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,004] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Gravity_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,004] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Gyroscope_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,005] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Light_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,006] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Magnetic_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,006] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Pressure_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,007] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Proximity_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,008] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Rotation_Sensor_Script for tenant id: -1234
[2015-12-18 13:06:00,008] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Temperature_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,001] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Accelerometer_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,001] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Battery_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,002] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: GPS_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,002] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Gravity_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,003] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Gyroscope_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,004] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Light_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,004] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Magnetic_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,004] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Pressure_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,005] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Proximity_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,005] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Rotation_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:00,006] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Temperature_Sensor_Script for tenant id: -1234
[2015-12-18 13:07:28,405] ERROR
{org.eclipse.paho.client.mqttv3.internal.ClientState} - b942b:raspberrypi:
Timed out as no activity, keepAlive=60,000
lastOutboundActivity=1,450,424,128,407 lastInboundActivity=1,450,424,068,623
[2015-12-18 13:07:28,406] WARN
{org.wso2.carbon.device.mgt.iot.controlqueue.mqtt.MqttSubscriber} - Lost
Connection for client: b942b:raspberrypi to tcp://204.232.188.214:1883._This
was due to - Timed out waiting for a response from the server (Sanitized)
[2015-12-18 13:07:29,273] INFO
{org.wso2.carbon.device.mgt.iot.controlqueue.mqtt.MqttSubscriber} -
Subscribed with client id: b942b:raspberrypi
[2015-12-18 13:07:29,273] INFO
{org.wso2.carbon.device.mgt.iot.controlqueue.mqtt.MqttSubscriber} -
Subscribed to topic: WSO2IoTServer/+/raspberrypi/+/publisher
[2015-12-18 13:08:00,001] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Accelerometer_Sensor_Script for tenant id: -1234
[2015-12-18 13:08:00,001] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Battery_Sensor_Script for tenant id: -1234
[2015-12-18 13:08:00,002] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: GPS_Sensor_Script for tenant id: -1234
[2015-12-18 13:08:00,002] INFO
{org.wso2.carbon.analytics.spark.core.AnalyticsTask} - Executing the
schedule task for: Gravity_Sensor_Script for tenant id: -1234
--
/sumedha
m: +94 773017743
b : bit.ly/sumedha
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
