Özhan,
You have described usage server work and I would say -- this is how it
should work in fact. Some points may seem strange from user perspective, but if
you go deeper into its logic, you will see that everything supposed to work
like that.
Keep in mind that key point of usage server is scheduler that works
pretty much the same as UNIX cron. Database contains record of the next run
and all previous runs. By default, aggregation range is 14400 minutes or 24
hours. This parameter contains CS global variable --
usage.stats.job.aggregation.range. If you change the value using CS management
interface -- it will not affect JOB scheduler immediately, even if you restart
management server (which is required). Time interval should be updated after
recent JOB is executed.
If I remember correctly, all the date/time values in database are UTC.
Timezone affects aggregation statistics runner, so if you would like to charge
client usage billing based on your local time - this is your case. Otherwise --
GMT is fine.
From my point of view -- to run usage stats every 30 min is overkill.
Will suggest you to use default settings (i.e. once a day) unless you really
need it.
Regards,
Vadim.
-----Original Message-----
From: Özhan Rüzgar Karaman [mailto:[email protected]]
Sent: Wednesday, July 29, 2015 2:37 PM
To: [email protected]
Subject: Re: Enabling CloudStack Usage Server Problem
Hi Vadim;
Usage Statistics Calculation is started today, but what i have noticed is
somehow when i change any of usage parameters and stop/start the management
server it effects after some time like one day :))
Yesterday i changed usage.stats.job.exec.time parameter several times to
manually trigger usage stats calculation daemon but it did not ever start.
Today when i check the logs i noticed that it started working at the mentioned
time in parameter today :) Now i raised usage.stats.job.aggregation.range
parameter from 10 to 30 an restarted management server and now i see that it
continues to collect for 10 minutes of time :)) I do not know when it will
mention the parameter is changed and change the calculation interval. By the
way i made the parameter changes with admin user and CS main interface.
I have also another question my timezone is not listed on official
documentation for valid timezones. I will use Asia/Istanbul for timezone fields
for usage and we will see how system will respond to it :) I do not expect any
problems but :)
Thanks for your reply :)
Regards
Özhan
On Wed, Jul 29, 2015 at 10:53 AM, Vadim Kimlaychuk < [email protected]>
wrote:
> Hello Özhan,
>
> Have you checked JOB table at your database ? Try to log in
> into usage database and
>
> select * from usage_job;
>
> If you don't see anything probably you haven't installed java
> mysql connector
>
> Vadim.
>
> -----Original Message-----
> From: Özhan Rüzgar Karaman [mailto:[email protected]]
> Sent: Tuesday, July 28, 2015 11:55 AM
> To: [email protected]
> Subject: Enabling CloudStack Usage Server Problem
>
> Hi;
> I am using CloudStack 4.5.1 with KVM clients. I have problem with
> getting vm usage statistics, i could not able to start/operate
> CloudStack Usage Deamon. I could not see any values under Mysql
> cloud_usage database. My settings are below...
>
> Thanks
> Özhan
>
> *Global Settings Parameters:*
> usage.aggregation.timezone : GMT
> usage.execution.timezone : GMT
> enable.usage.server : true
> publish.usage.events : true
> usage.stats.job.exec.time: 13:35
> usage.stats.job.aggregation.range :10
>
> *root@cloudstack:~# dpkg -l|grep clouds*
> ii *clouds*tack-common 4.5.1-shapeblue-00
> all A common package which contains files which are shared by
> several CloudStack packages
> ii *clouds*tack-management 4.5.1-shapeblue-00
> all CloudStack server library
> ii *clouds*tack-usage 4.5.1-shapeblue-00
> all CloudStack usage monitor
>
> *root@cloudstack:/var/log/cloudstack/management# cat
> management-server.log|grep usage*
> 2015-07-28 11:29:32,784 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-5:ctx-f8b40397) checking health of *usage* server
> 2015-07-28 11:29:32,786 DEBUG [c.c.h.HighAvailabilityManagerImpl]
> (HA-5:ctx-f8b40397) *usage* server running? true, heartbeat: Tue Jul
> 28
> 11:29:15 EEST 2015
> 2015-07-28 11:39:32,784 INFO [c.c.h.HighAvailabilityManagerImpl]
> (HA-5:ctx-0383793a) checking health of *usage* server
> 2015-07-28 11:39:32,786 DEBUG [c.c.h.HighAvailabilityManagerImpl]
> (HA-5:ctx-0383793a) *usage* server running? true, heartbeat: Tue Jul
> 28
> 11:39:15 EEST 2015
>
> *root@cloudstack:/var/log/cloudstack/usage# tailf usage.log *
> 2015-07-27 13:22:00,152 INFO [utils.component.ComponentContext]
> (main:null) Starting
> com.cloud.user.dao.UserAccountDaoImpl_EnhancerByCloudStack_3605546c
> 2015-07-27 13:22:00,152 INFO [utils.component.ComponentContext]
> (main:null) Starting
> com.cloud.usage.dao.UsageNetworkDaoImpl_EnhancerByCloudStack_d8d23a61
> 2015-07-27 13:22:00,152 INFO [utils.component.ComponentContext]
> (main:null) Starting
> com.cloud.alert.dao.AlertDaoImpl_EnhancerByCloudStack_b9e90fb5
> 2015-07-27 13:22:00,153 INFO [utils.component.ComponentContext]
> (main:null) Starting
> com.cloud.user.dao.VmDiskStatisticsDaoImpl_EnhancerByCloudStack_f62ca4
> 4d
> 2015-07-27 13:22:00,153 INFO [utils.component.ComponentContext]
> (main:null) Starting
> com.cloud.user.dao.UserDaoImpl_EnhancerByCloudStack_36959499
> 2015-07-27 13:22:00,153 INFO [utils.component.ComponentContext]
> (main:null) Starting
> com.cloud.usage.dao.UsageVMSnapshotDaoImpl_EnhancerByCloudStack_66e103
> 68
> 2015-07-27 13:22:00,153 INFO [utils.component.ComponentContext]
> (main:null) Starting
> com.cloud.usage.UsageManagerImpl_EnhancerByCloudStack_38bd4b32
> 2015-07-27 13:22:00,154 INFO [cloud.usage.UsageManagerImpl]
> (main:null) Starting Usage Manager
> 2015-07-27 13:22:00,262 INFO [utils.component.ComponentContext]
> (main:null) Starting
> com.cloud.usage.UsageAlertManagerImpl_EnhancerByCloudStack_34791552
> 2015-07-27 13:22:00,262 INFO [cloud.usage.UsageServer] (main:null)
> UsageServer ready...
>
>
> *root@cloudstack:/var/log/cloudstack/usage# ls -l
> /etc/cloudstack/usage/*total
> 4
> lrwxrwxrwx 1 root root 40 Jul 27 12:09 *db.properties* ->
> /etc/cloudstack/management/db.properties
> lrwxrwxrwx 1 root root 30 Jul 27 12:09 *key* ->
> /etc/cloudstack/management/key
> -rw-r--r-- 1 root root 2966 May 6 03:19 log4j-cloud.xml
>
