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.
Actions | RPM(Average) | Memory
-- | -- | --
Enable Logging(Blue) | 1.7 K | Around 2.31 GB
Disable Logging(Green) | 2.31 K | Around 1 GB
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.
Actions | RPM(Average) | Memory -- | -- | -- Enable Logging(Blue) | 1.7 K | Around 2.31 GB Disable Logging(Green) | 2.31 K | Around 1 GB