Project

General

Profile

Feature #26173

Include puppet statistics in telemetry

Added by Lukas Zapletal over 1 year ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Category:
Monitoring
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

USE CASE:

Foreman telemetry stack tracks the performance of a system based on its current runtime. If there were a puppet metric, it would be dramatically simpler to correlate performance changes with system configuration changes.

Technical requirements:

Can a PCP plugin be written for puppet client that tracks the simple results of puppet runs on the system:

- Applied
- Restarted
- Failed
- Restart Failures
- Skipped
- Pending

I'd expect these metrics to only tick up at the conclusion of the puppet run (and mostly just pull them in from the post run status report) and to be zero for all other times.

ANALYSIS:

We can add a new metric that will track number of resources with label of "state". Each report will increase those counters, so monitoring will be able to show rate of resources applied/skipped etc.

Associated revisions

Revision 7b040dea (diff)
Added by Lukas Zapletal 11 months ago

Fixes #26173 - added config_report_metric_count metric

History

#1 Updated by The Foreman Bot over 1 year ago

  • Assignee set to Lukas Zapletal
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6521 added

#2 Updated by Tomer Brisker 11 months ago

  • Fixed in Releases 1.24.0 added

#3 Updated by Lukas Zapletal 11 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF