Summary

Existing log events cover a lot of ground and the IS logging infrastructure generously handles the general logging case, but it's a broad brush and doesn't always get as detailed as you'd like. There are situations in which there is no way to log specific information. For example, you might want to log the parameters to event handlers, the LocaleID of a specific container, or task execution values. This logging mechanism can be used for those and just about any other type of custom logging you'd like at any time during the execution of the package and is great for one off, surgical logging of custom data that the existing log infrastructure doesn't support. If you ever run into a situation in which you wished something got logged, but it didn't, this method might fill in the gaps.