This repository has been archived by the owner on Jun 1, 2024. It is now read-only.
feature: add option to skip sending oversized data to Elasticsearch #169
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- New option : SingleEventSizePostingLimit (default to 0: no limit) - Remove redundant overload method in LoggerConfigurationElasticSearchExtensions.cs
|
Hey, just started using this sink and I am using AWS Elasticsearch and I have had oversized logs being posted before so this is an issue for me. Could anyone advise me on when this PR will be merged into the sink? Is there a work-around for now? |
|
Merged now to dev. Should be available in https://www.nuget.org/packages/Serilog.Sinks.ElasticSearch/6.5.0-unstable0039 @MinhNguyenDev sorry it took so long. I m not actively using this sink anymore. Thanks for the PR! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What issue does this PR address?
Does this PR introduce a breaking change?
Other information: