[FEATURE] Support for Failure Sink in Elasticsearch.Serilog.Sink #500
Labels
enhancement
New feature or request
Comments
|
Could you please assist with this? We are planning to incorporate it for production support and are checking if there is a way to capture the Failures. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Team,
In the earlier Serilog.Sinks.Elasticsearch package, there was support for a failure sink mechanism. This was extremely useful — when there were issues pushing logs to Elasticsearch (e.g., network failures, serialization issues), the failure sink or failure callback would be triggered, allowing us to route the failed logs to alternative destinations (e.g., a file sink or another fallback system).
However, in the newer Elasticsearch.Serilog.Sink package, it seems this feature is missing or not clearly documented.
Request:
Could you please confirm whether there is an equivalent option in the new package for handling failed log events (such as a failure sink or a failure callback)? If not, would it be possible to consider adding this feature? It is critical for production environments where log loss is unacceptable, and having a fallback mechanism is essential for observability and troubleshooting.
Thanks for the great work on the package!
The text was updated successfully, but these errors were encountered: