André Mazayev

Hi @Vslava can you please take a look at https://github.com/moleculerjs/moleculer/issues/1065 and see if it's somehow related to the issue that you've reported?

I think that this need further discussion. The overall idea is that events are fire-and-forget, i.e., you don't get any guarantees about the delivery of the event. > I see...

> @AndreMaz, this issue #1065 has a different issue. There, a local call to `emit` and `broadcast` occurs through `await` while waiting for a resolve `Promise`, so it turns to...

As @icebob suggested, adding a `throw` would propagate the error, allowing you to catch and react to it. However, introducing this could be a breaking change. I'm saying *could* because...

How this feature would work? Imagine the following scenario:  and `excludes` field with [`"math.**"`] In this case the `excludes` means that if we call `math.random` directly there won't by...

So, under the hood, it is still necessary to collect all spans and only when pushing or printing them the `mat.**` is excluded?

@imatefx what's the version of `dd-trace-js` that you're using? Can you try the same version as in Moleculer's unit tests (`"dd-trace": "^0.29.1" `) and see if it works?

When streaming the params are placed into `$params`. So for validation you need to set something like this: ```js params: { $params: { type: "object", props: { id: "uuid" }...

After setting your example with NATS I see what you mean by "`$params` are lost". So what do you suggest? Move `$params` into `meta`?

@intech great. Thank you :+1: