[Queue dashboard] Queues always show 100% error rate even with no errors

[Fwang36]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

SUMMARY - docs should be updated to show that the transaction's status must be set to 'ok', instead of the just the span. Reference comment: #11050 (comment)

SDK version 2.5.0

1. Follow the docs to create a queue monitoring transaction
2. Open up the Queue monitoring dashboard and see 100% error rate.

3. See that transaction has no errors

Link to my Queue dashboard

Expected Result

Error rate should not be 100%

Actual Result

Error rate is 100%

Product Area

Insights

Link

No response

DSN

No response

[getsantry]

Routing to @getsentry/product-owners-insights for triage ⏲️

[getsantry]

Auto-routing to @getsentry/product-owners-dashboards for triage ⏲️

[edwardgou-sentry]

Hi @Fwang36 looks your trace.status is being captured as unknown:

Any status other than ok is considered an error, hence the 100% error rate.

Since you are manually instrumenting your queues, can you try using the following to set your trace as successful:
span.set_status("ok")

[Fwang36]

hey thanks!

Where do I add span.set_status("ok")? I have it set currently below the #Set span data section of the code example in the docs. In the span it looks like it gets added as a Tag but the Trace still shows an unknown status. Here is what I have in the sentry_sdk.start_span() section

    # Create the span
    with sentry_sdk.start_span(
        op="queue.publish",
        description="queue_producer",
    ) as span:
        # Set span data
        span.set_data("messaging.message.id", message_id)
        span.set_data("messaging.destination.name", queue)
        span.set_data("messaging.message.body.size", len(message.encode("utf-8")))
        span.set_status("ok")
        # Publish the message to the queue (including trace information and current time stamp)
        now = int(datetime.now(timezone.utc).timestamp())
        connection.publish(
            queue=queue,
            body=message,
            timestamp=now,
            headers={
                "sentry-trace": sentry_sdk.get_traceparent(),
                "baggage": sentry_sdk.get_baggage(),
            },
        )

Link to the transaction

[edwardgou-sentry]

Hmm, I think your code example looks right. It could be a bug in the sdk not setting the trace status, or maybe it's not intended behaviour.
@getsentry/owners-python-sdk What's the intended way to set the trace status to ok?

@Fwang36 Maybe we can we try using setContext:

sentry_sdk.set_context("trace", {
    "status": "ok",
})

[Fwang36]

I tried calling that within the start_span and the start_transaction. Both times led to the transaction being dropped serverside with an InvalidTransaction outcome.

I'll wait to see what the sdk team says, thanks!

[getsantry]

Routing to @getsentry/product-owners-insights for triage ⏲️

[Fwang36]

hey, I was able to get this to work with before_send_transaction() and adding the context 'status': 'ok' directly to the event. I'm going to move this to the SDK repo since I think it might be an issue with span.set_status("ok")