Open
Description
It's useful to provide a generic way to apply multiple parsers on the same message. So far, we've faced this issue for DLT messages containing SomeIP traces in their payload and we solved that as a special case for DLT parser only in #2073.
However, it would be much better to provide a generic way to nest parsers of any kind of the level of producer making this issue portable and even configurable by users.
This would be really useful combined with the plugin system to allow users to provide their special parsers for special payload as plugins as well.
We've already provided with multiple approaches:
- Allow nested parsers on MessageProducer level #2077
- Allow nested parsers on MessageProducer level (v2) #2078
- Allow nested parsers on MessageProducer level (v3) #2084
- Allow nested parsers on MessageProducer level (v4) #2087
This issue is related to #2071