search

cloudfoundry-attic / ouroboros-release

Apache License 2.0
0 stars 1 forks source link

Volley should write huge envelopes #4

Open poy opened 7 years ago

poy commented 7 years ago

An attack profile that volley is missing is writing very large envelopes. This could cause some of the Loggregator diodes to hold too much memory.

cf-gitbot commented 7 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/148444459

The labels on this github issue will be updated when the story is started.

enocom commented 7 years ago

It would be nice to move volley and its like in a shared repo, in which we can vendor go-loggregator. Having a client available makes writing a hostile writer into loggregator much easier.

poy commented 7 years ago

@enocom What is stopping us from adding go-loggregator as a submodule?

enocom commented 7 years ago

@apoydence Nothing. I would prefer to do so once across a collection of loggregator testing tools. Either way, I propose we leave volley as a downstream consumer and create another job and process as an upstream producer into loggregator. What do you think?

poy commented 7 years ago

@enocom That sounds good to me.

I wonder if these "attack profiles" should move to a fork of https://github.com/cppforlife/turbulence-release that attack loggregator.

Each attack is independent and reported to data dog. It might produce more actionable data.