Skip to content
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

Serilog.Sinks.NewRelic.Logs objects does not dispose when the throughput is high #8

Open
PratikPatel-Mtech opened this issue Jul 7, 2021 · 0 comments

Comments

@PratikPatel-Mtech
Copy link

PratikPatel-Mtech commented Jul 7, 2021

Status

BUG REPORT

Steps

The services are talking higher memory than usual when throughput is high. We have been observed that when we integrate the NewRelic login it is working fine with normal throughput. However, when throughput is high then it takes too much memory.

Seems like Serilog.Sinks.NewRelic.Logs objects do not dispose when throughput is high. On the other hand, services are working fine after removing logging.

Expected behavior

Serilog.Sinks.NewRelic.Logs objects should be disposed whatever the throughput.

Actual behavior

Serilog.Sinks.NewRelic.Logs objects not disposing when throughput is high.

Environment

Services are hosted in the Kubernetes cluster.

image
Memory Issue

Actions RPM(Average) Memory
Enable Logging(Blue) 1.7 K Around 2.31 GB
Disable Logging(Green) 2.31 K Around 1 GB
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant