0
Completed

Event Broker 3.0 CSV log file location is not configurable

Bob Bradley 8 years ago • updated by anonymous 4 years ago 2

In order to accommodate the tendency for clients to want to specify which disk log files are written to, it is desirable that the location of log files is made configurable. Presently it appears only the logDaysToKeep property can be set, and I have this at the default 5 value in a shared lab environment. Log files are presently being written to c:\Program Files\UNIFY Solutions\Event Broker\Services\Logs, and so as a mitigation strategy to avoid excessive disk usage I have set this up as a compressed folder.

The Event Broker 3.0 service/scheduler has been in place and running for 3 days now (in what amounts to a shared development environment between DEEWR developers and us the FIM implementors). In that short time we now have 15 Mb across 3 log files, todays presently showing 13,371 log file entries. By the time we stabilize at 5 days of logs, we will have between 25 and 30 Mb of logs in 5 files ... unless we want to increase the number of days ... and it's not beyond the realms of possibility that this could be upwards of 90 days.

All other solution log file locations are configurable, and this should be no different.

No real urgency - just a consideration for the next release, where I imagine the full gammit of logging options available to Identity Broker (including Windows Event logs) are probably going to be considered anyway.

P.S. No work should be billable to the client in this case - the issue is raised by myself and has not been brought to the attention of the client (but will no doubt come up when we do our first deployment).

Hi Bob,

That logging location is not intended to be configurable. The logging mechanism currently present is NOT the same as the CSV logging that's in Identity Broker. It's heavily modified to support querying, filtering, streaming through WCF and some internal things, plus support for making additions in the future. Because of that the logs stay in the same place because they have to have specific file names, we have to ensure we have appropriate permissions to read/write, etc.

Support for all the additional logging mechanisms (configurable CSV, emails, etc) was out of the question due to time constraints. The logging itself isn't a problem, but providing a suitable user interface for configuring every type of logging is much more difficult. It will certainly happen, but it will be 3.1 and not 3.0.1. I'll keep this here as there isn't already an issue for it though, so thank you for reporting it.

(FYI, you don't need to tell us what is and isn't billable. Shane has to approve them all manually and it's his decision... although Adam and I can generally pick up what is and isn't anyway)

This will be completed during UFCORE-33