Three tings that come to my mind:

   1. Trends should be defined first, do you have any trends defined?
   2. Most of interesting trends come from facts, do you have puppet facts 
   reporter configured?
   3. Trends are stored as intervals, which means no extra data will be 
   added if no changes in counts were detected. Do you have a change to an 
   existing trend that was not recorded?

On Wednesday, October 12, 2016 at 6:48:11 PM UTC+3, Danny Kimsey wrote:
> I am trying to setup trends and I can verify that the rake trends:counter 
> command is executing (system's cron.log). I can even run it manually, and 
> it runs fine. However, no data is actually populated into the trends page. 
> I'm at a loss as to how to debug this further. Enabling debug logs do not 
> add anything useful.
> CentOS 7
> Katello 3.1
> Foreman 1.12.3
> *rake --trace trends:counter*
> ** Invoke trends:counter (first_time)
> ** Invoke environment (first_time)
> ** Execute environment
> ** Execute trends:counter
> *production.log*
> 2016-10-12 10:31:49 [foreman-tasks/dynflow] [I] start terminating 
> throttle_limiter...
> 2016-10-12 10:31:49 [foreman-tasks/dynflow] [I] start terminating client 
> dispatcher...
> 2016-10-12 10:31:49 [foreman-tasks/dynflow] [I] stop listening for new 
> events...
> 2016-10-12 10:31:49 [foreman-tasks/dynflow] [I] start terminating clock...

You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to