[
https://issues.apache.org/jira/browse/ACE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906983#comment-13906983
]
Wilfried Sibla commented on ACE-459:
------------------------------------
Yes, this makes also sense.
But on server side, the feedback info isn't interpreted. It's only a bunch of
key-value pairs.
Thus all feedback events must be parsed to determine the bundle name.
It's again a trade of between network traffic and amount of logging data and on
the other side of having a more informative UI and more diagnostic info... or
simpler code and algorithms on server side.
I would prefer having the bundle names directly within the event.
In scenraios where this would be too much data, the events could also be
skipped on the target with the corresponding configuration
> Add BundleSymbolicName and Version to AuditLog/FeedBack on BundleEvents
> -----------------------------------------------------------------------
>
> Key: ACE-459
> URL: https://issues.apache.org/jira/browse/ACE-459
> Project: ACE
> Issue Type: Improvement
> Components: Management Agent
> Affects Versions: 1.0.0
> Reporter: Wilfried Sibla
> Priority: Minor
> Attachments: EventLogger.patch
>
>
> The LogViewer within the Target dialog on the ACE server only shows the id of
> the bundles (except directly during installation).
> It would be very helpful to have the BSN and version also there in case of
> problem diagnostics etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
