Project

General

Profile

Actions

Bug #9441

closed

Trends background processing is unnecessarily complicated

Added by Bryan Kearney about 9 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
gem foreman_statistics
Difficulty:
easy
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1192176
Description of problem:
I'll admit I don't fully understand what Trends will end up showing me, since I haven't gotten it working, but it seems odd that we force users to use both the Web UI and the CLI to get them set up.

When you first visit the Trends page, and there's nothing configured, you see:
"No trend counter defined.
To define trend counters, use the Add Trend Counter button.To start collecting trend data, set a cron job to execute 'rake trends:counter' every Puppet Interval (30 minutes)."

If you click on New Trend Counter, and make something, the message changes:
"No trend counter found.
To start collecting trend data, set a cron job to execute 'RAILS_ENV=production bundle exec rake trends:counter' every Puppet Interval (30 minutes)"

Why can't I fully configure Trends through the Web UI? Couldn't we configure that through Satellite and have Sat push any CLI commands needed in the background?

Also, there's no ending punctuation for that second message.

Version-Release number of selected component (if applicable):
6.0.6

Actions

Also available in: Atom PDF