The MeteorUserProcessor can produce very verbose / redundant data, which needlessly increase storage needs, bandwidth, and workload on the logs processing platform (eg BELK stack). As an example, in most cases, the values contained below user.services.resume are irrelevant to logging needs.
The customization needs for this processor are very diverse, so the simplest technique would be to add a optional post-process callback.
fgm
commented
7 years ago
The MeteorUserProcessor can produce very verbose / redundant data, which needlessly increase storage needs, bandwidth, and workload on the logs processing platform (eg BELK stack). As an example, in most cases, the values contained below user.services.resume are irrelevant to logging needs.
The customization needs for this processor are very diverse, so the simplest technique would be to add a optional post-process callback.