Displaying 7 results from an estimated 7 matches for "resource_statuses".
2011 Aug 16
4
Dashboard table resource_statuses growing uncontrollably
I''ve "inherited" the administration of a puppet-dashboard (version
1.1.0, installed on RHEL 5.6 from puppetlabs RPM), and have hit a
problem I''m hoping for some help with.
In short, one table, "resource_statuses" appears to be growing at a
rate far higher then the other tables:
mysql> select count(*) from nodes;
+----------+
| count(*) |
+----------+
| 107 |
+----------+
mysql> select count(*) from resource_statuses;
+-----------+
| count(*) |
+-----------+
| 188068011 |
+-----------+
Y...
2013 Dec 18
0
ruby
...puts report.host
print "Started : "
puts report.time
print "Log count: "
puts report.logs.size
print "Metrics count: "
puts report.metrics.size
print "Resource Status count: "
puts report.resource_statuses.size
print "Status: "
puts report.status
report.logs.each do |logg|
puts "LOG ---------------------------------------------"
if logg.file
print "File: "
puts logg.file
end...
2011 Jul 12
1
Possible leaking records in dashboard db
...ommand:
nice -n +1 rake RAILS_ENV=production reports:prune upto=1 unit=mon
This seems to work fine, and the amount of reports returnd by this mysql query seems to drop by the proper amount:
select count(*) from reports;
Right now it returns a value of 12591. So far so good.
The problem is the resource_statuses statuses table. Right now I have 63695 distinct values for report_id as returned by:
select count(*) from (select distinct report_id from resource_statuses)as count;
Am I missing something?
It seems to me this can be fixed by just making the table "cascade on delete", though I'&...
2012 Jan 03
6
Puppet Dashboard: db:migrate failure (1.2.2 to 1.2.4)
...ess, the DB is pretty huge and the process takes a
while to execute.
Executed from the puppet-dashboard directory: sudo rake db:migrate
RAILS_ENV=production
== AddReportForeignKeyConstraints: migrating
=================================
Going to delete orphaned records from metrics, report_logs,
resource_statuses, resource_events
Preparing to delete from metrics
2012-01-03 14:16:07: Deleting 0 orphaned records from metrics
Deleting 100% |##########################################| Time:
00:00:00
Preparing to delete from report_logs
2012-01-03 14:16:41: Deleting 0 orphaned records from report_logs
Del...
2013 Nov 26
37
get a *structured* version of the puppet agent output
puppet agent --verbose shows a verbose output of the changes done by
puppet, such as:
notice:
/Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner:
owner changed ''root'' to ''logstash''
notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed
''stopped'' to ''running''
2011 Jun 09
6
Prerun, Postrun Commands, and Stages
Hi all,
I''m looking for background information about how bug #7127[1] should
be fixed: prerun_command don''t stop puppet on error
I think there''s general agreement that if the prerun command fails,
then the catalog should not be applied, but the report should be sent,
and the report''s status should be "failed".
However, what about the post-run
2012 Jan 09
14
scaling projections for dashboard database?
So I got dashboard up and running on our production system on Thursday before I left. Within 48 hours it had completed filled the /var filesystem. The ibdata1 file is currently at 8GB in size.
1. What size should I expect for ~500 nodes reporting every 30 minutes?
2. Are there some database cleanup scripts which I have managed to overlook that need to be run?
--
Jo Rhett
Net Consonance :