Project

General

Profile

Actions

Bug #2194

closed

File name is always 'file' in inventory log messages

Added by Jonathan CLARKE almost 13 years ago. Updated over 9 years ago.

Status:
Released
Priority:
3
Assignee:
Jonathan CLARKE
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

For example, when a new report is received, I see in the logs:

13:46:59.993 [qtp723566380-66] INFO  c.n.i.p.e.FusionReportEndpoint - New input report: file
13:47:00.936 [qtp723566380-66] INFO  c.n.i.p.e.FusionReportEndpoint - Report file parsed in 933 milliseconds, sending to save engine.
13:47:00.975 [qtp723566380-72] INFO  c.n.i.p.e.FusionReportEndpoint - New input report: file
13:47:01.191 [qtp723566380-72] WARN  c.n.i.p.f.FusionReportUnmarshaller - Error when parsing date for last user loggin. Awaited format is EEE MMM dd HH:mm, found: boot  Wed Sep 21
13:47:01.414 [qtp723566380-72] INFO  c.n.i.p.e.FusionReportEndpoint - Report file parsed in 438 milliseconds, sending to save engine.
13:47:01.783 [qtp723566380-71] INFO  c.n.i.p.e.FusionReportEndpoint - New input report: file
13:47:02.999 [qtp723566380-71] INFO  c.n.i.p.e.FusionReportEndpoint - Report file parsed in 1 second and 216 milliseconds, sending to save engine.
13:47:03.047 [qtp723566380-67] INFO  c.n.i.p.e.FusionReportEndpoint - New input report: file
13:47:03.310 [qtp723566380-67] INFO  c.n.i.p.e.FusionReportEndpoint - Report file parsed in 263 milliseconds, sending to save engine.

This would be much more useful if it was a real filename.

I attach a patch that I propose may fix this problem, although I'm not sure, so I'd like some feedback before commiting it.


Files

patch (2.57 KB) patch Jonathan CLARKE, 2012-01-25 14:46
Actions

Also available in: Atom PDF