Feature #6104
Client reports should be filterable at the client
| Status: | Needs More Information | Start date: | 02/01/2011 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Zach Leslie |
% Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
| Votes: | 1 |
Description
Because the reports are filtered on the master, and not on the client, the client still must send all of the data over the wire to the server. In some cases this can take far longer that is ideal. As a remediation, the clients should be configurable so that only the selected report data is sent to the server. This will keep data that is filtered out from being sent to the server and as a result, speed up the transaction.
Tunable options should include the following:
- metrics
- logs
- resource status
- etc…
History
Updated by Dan Bode over 1 year ago
- only show resources that have at least one event.
- remove internal puppet resources (schedules/filebucket)
Updated by James Turnbull about 1 year ago
- Assignee set to Nigel Kersten
Updated by Nigel Kersten 9 months ago
- Status changed from Needs Decision to Needs More Information
- Assignee changed from Nigel Kersten to Zach Leslie
- Priority changed from Normal to Low
I’m not actually in favor of this. I want more consistency in reporting, not less.
What drove the feature request Zach? Was it Dashboard being crap at accepting reports?
Updated by Luke Kanies 9 months ago
A lot of this ended up being because of a yaml processing bug or something similar on puppetmaster. That was fixed, and the problem largely went away.
However, a secondary problem is that the reports really are quite large, even for ones that have almost no changes. This was unintentional and might be worth assessing, but as you say, not on a conditional basis.
Updated by Zach Leslie 9 months ago
Yes, mostly to reduce the size of the reports, and it only seemed that a small portion of the report was actually being used. I think this has gotten better in recent versions, and since there is no affected version attached to the ticket, its hard to determine when this has gotten better.
Updated by Marcin Deranek 9 months ago
More details are in https://support.puppetlabs.com/requests/236 As far as I can see measurements were done with Puppet 2.6.4 vs 0.25.5 (bottom of the ticket).