Unable to populate trends data, rake trends:counter does nothing

Support
1

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…

2

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... > >
3

Apologies for the absurd delay. I missed this email.

I had trends defined.

The distribution trend seemed not to work. Possibly related to a change in
Puppet, but likely a red-herring in my cause.

But root cause was that trend was not functional (no results) and cronjobs
were disabled because the foreman user was not permitted access to cron by
default in our /etc/security/access.conf. I hate that thing.

Thank you, it pointed me in the right direction.

··· On Thursday, October 13, 2016 at 1:48:48 AM UTC-5, ssh...@redhat.com wrote: > > > 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 >> ... >> >>