QueueEventsProducer/QueueEvents support for telemetry

[swhiteman]

Not sure if custom Queue Events are supposed to work with OT/Jaeger or not, but right now I don't see anything (though the custom event stream is working).

Producer side:

const { QueueEventsProducer } = require("bullmq");
const { BullMQOtel } = require("bullmq-otel");

const queueEventsProducer = new QueueEventsProducer("custom", {
    telemetry: new BullMQOtel('simple-guide'),
    connection : dotEnv.$.redis.connection
});

queueEventsProducer.publishEvent({
    eventName: "customExample",
    custom: 'value1'
})

Consumer side:

const { QueueEvents } = require("bullmq");
const { BullMQOtel } = require("bullmq-otel");

const queueEvents = new QueueEvents("custom", {
    telemetry: new BullMQOtel('simple-guide'),
    connection : dotEnv.$.redis.connection
});

queueEvents.on('customExample', async ({ custom }) => {
    console.log("custom",custom);
});

Output from consumer is custom value1 as expected but Jaeger doesn't show anything (OT overlay & Jaeger are working for standard queue.add and worker).

[swhiteman]

QueueEventsOptions includes telemetry:
https://api.docs.bullmq.io/interfaces/v5.QueueEventsOptions.html

QueueEventsProducer takes a QueueBaseOptions and that includes telemetry too:
https://api.docs.bullmq.io/interfaces/v5.QueueBaseOptions.html

[manast]

The telemetry option works because QueueEvents is derived from a base class that accepts telemetry. However we do not add any spans for events. I do not know if this is so useful, but maybe it is. Can you tell us a bit more about your scenario so that I can get a better idea of the usefulness of a feature like this?

[swhiteman]

Honestly not that useful but if it's supposed to work, I wanted to see it in Jaeger.

With the nature of events it probably doesn't make sense to support telemetry. Maybe instead <omit> it so that's clear?