Frequent logging from base_aggregator component

Hi, I’m running an app on Heroku, and every five seconds we’re getting this in our logs:

Jan 10 10:18:46 streetmix-staging app/web.1: {"v":0,"level":30,"name":"newrelic","hostname":"574a985e-0269-419b-b6fd-8421dde485a4","pid":18,"time":"2020-01-10T18:18:46.314Z","msg":"error_event_data Aggregator data send.","component":"base_aggregator"}
Jan 10 10:18:46 streetmix-staging app/web.1: {"v":0,"level":30,"name":"newrelic","hostname":"574a985e-0269-419b-b6fd-8421dde485a4","pid":18,"time":"2020-01-10T18:18:46.316Z","msg":"analytic_event_data Aggregator data send.","component":"base_aggregator"}
Jan 10 10:18:46 streetmix-staging app/web.1: {"v":0,"level":30,"name":"newrelic","hostname":"574a985e-0269-419b-b6fd-8421dde485a4","pid":18,"time":"2020-01-10T18:18:46.316Z","msg":"custom_event_data Aggregator data send.","component":"base_aggregator"

I’m posting this here because “newrelic” is being identified (and we do use this package). But I’m not sure what this base_aggregator component is, what it’s trying to do, and why it’s generating these messages. While our application seems to be running just fine, this is really disruptive to our logs. Any thoughts? Thanks!

[michaelgoin]

@louh just a heads up this logging has been reduced to “debug” level in the most recent agent version, so “info” level in your logs should work fine now.

[michaelgoin]

@louh, “warn” level is probably the easiest for you. We unfortunately don’t log a lot of valuable info at “info” level, so chance of negative impact is super low. Most things we need for researching issues are at the “trace” level.

That being said, that could change in the future. So the other approach might be more future proof so you don’t have to remember to set back with a future release.