-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is seq-forwarder a via way to introduce durable log shipping into Mobile Apps in C# #72
Comments
Hi John! I don't think Seq Forwarder will cut it in this scenario, it's really designed around running as a separate process with an HTTP API etc., which I'm guessing will be a challenge on mobile devices. Does Serilog.Sinks.Seq's durable mode work for you, or would some alternative to the file-backed log buffer be needed? |
Hi Nick,
I think it does for us internally as we are coming back to Seq as our observation platform.
I was forward planning when a client asks us to plug into one of their platforms of choice if we don’t manage the running environment for them as well.
I was kicking around this dump area of a durable wrapper sink which took another sink as an option and handled all of the offline / online but that’s duplication not just in the Seq sink but I think I remember back in the day we’ve got other syncs which also do some level of durability.
Seq Sink will do us for now I think – the current project I’m think of is 100% managed by us.
Great work mate – really enjoying the new work – just what we needed.
JK
From: Nicholas Blumhardt ***@***.***>
Sent: Wednesday, February 7, 2024 12:39 AM
To: datalust/seq-forwarder ***@***.***>
Cc: John Kattenhorn ***@***.***>; Author ***@***.***>
Subject: [EXTERNAL]:Re: [datalust/seq-forwarder] Is seq-forwarder a via way to introduce durable log shipping into Mobile Apps in C# (Issue #72)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi John! I don't think Seq Forwarder will cut it in this scenario, it's really designed around running as a separate process with an HTTP API etc., which I'm guessing will be a challenge on mobile devices.
Does Serilog.Sinks.Seq's durable mode work for you, or would some alternative to the file-backed log buffer be needed?
—
Reply to this email directly, view it on GitHub<#72 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEWOOJBZJOWDANMMVUNGLTYSLELLAVCNFSM6AAAAABC3VM6WSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRGAZDQNJZGE>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Fantastic - thanks, @johnkattenhorn 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Has anyone tried to implement durable log shipping to occasionally connected dotnet apps (specifically Uno Mobile Apps) using the seq-forwarder - would there be any advantage to doing this over using durable sink options from the seq sink ?
The text was updated successfully, but these errors were encountered: