Sentry Logs for `sentry-slog`

[szokeasaurusrex]

The slog crate does not support Sentry logs, but probably should. Instead it only supports events and breadcrumbs.

Let's add logs support.

[linear-code]

RUST-277

[reneleonhardt]

PR closed, not improvable?

[szokeasaurusrex]

@reneleonhardt not necessarily, the closure was not a technical judgment that the feature is impossible to implement.

Issues in this repository primarily track our team’s backlog, and we are not currently seeking external implementation work on any of them. I closed #1307 because this issue is not currently prioritized. Had the PR author aligned with us before opening the PR, as we ask contributors to do, we could have discussed whether they had a concrete need for the proposed feature and whether the work should be prioritized before they invested time in an implementation. If there was no concrete use case, we could have explained that we were not seeking a contribution for this backlog item.

If you personally use slog and would benefit from this feature, please comment with your use case or add a 👍. That would help us assess whether the issue should receive priority.

[szokeasaurusrex]

Some additional context: I opened this issue because I noticed a feature gap, not because of any user request to add logs support for sentry-slog. That is why we consider the issue low priority, and also why feedback from users that they want this would be a strong signal for us to increase the priority.

[reneleonhardt]

Thank you, I added 👍 sentry-rust should support Sentry logs in addition to events and breadcrumbs.
If you need a rework and polish of the proposed PR, I could give it a shot, it is tiny.
But I understand that it would only ever be accepted if your team decides to prioritize this issue above low.

[szokeasaurusrex]

Thanks @reneleonhardt, and thanks for the 👍!

Even relatively small but nontrivial changes like this one can take about as much maintainer time to review and polish as to implement, so I’d generally prefer to tackle this one myself. Now that I know there’s interest in the feature and that the work is likely fairly small, I’ll try to get to it sooner.

That said, if you’d enjoy taking a pass at it to learn more about the SDK, I’d be happy to help where I can, but please don’t feel you need to do so to make the feature happen sooner, and don't expect a speedy review.

If you haven’t heard from me after a month, feel free to poke me. It’s possible this could get buried amongst our other priorities, and a reminder would help us remember that there’s continued interest 🙏