Skip to content

Releases: DataDog/lading

0.4.3

05 Aug 03:12
0.4.3
3d2c98e
Compare
Choose a tag to compare
tagging release 0.4.3

0.4.2

27 Jul 20:37
0.4.2
94d5f6e
Compare
Choose a tag to compare
Tagging release 0.4.2

0.4.1

23 Jul 15:23
47dbc83
Compare
Choose a tag to compare
clippy dings, redux

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

0.4.0

12 Jul 21:22
40a2b63
Compare
Choose a tag to compare
Introduce `http_gen` (#52)

* Implement http_gen

This commit introduces a new program into the project, http_gen. It's similar to
file_gen except it works over HTTP. I've pretty substantially reworked the
configuration of file_gen and extracted common code from file_gen / http_gen,
though the two are still quite similar. I haven't tested http_gen against vector
yet and the configuration documentation must be updated.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* Slightly trim depedency list

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* Work on http_gen + vector bug

When I apply http_gen with DatadogLogs as variant vector will sometimes complain
about sheered payloads. I've added tests to confirm that lading_common generates
blocks that deserialize in this regard.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* No longer coordinate omission

As of this commit http_gen will no longer coordinate its throughput with the
target. Total successful throughput is still limited by target capacity but
request generation now is a combination of internal clock and maximum connection
saturation.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* correct test failure

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* Also release http_gen binary

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

0.3.8

07 Jul 15:41
777f075
Compare
Choose a tag to compare
multi-artifact release

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

0.3.7

07 Jul 03:20
84262d3
Compare
Choose a tag to compare
Correct FoundationDB building (#44)

This commit addresses important mistakes in the FoundationDB generator. Firstly,
the size of the serialized FoundationDB json lines will cause some block sizes
to exceed the maximum bytes per second, a problem. Second, the names of fields
were not correct. Numbers are now quoted as in the FDB logs.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

0.3.6

06 Jul 23:24
e2b6bac
Compare
Choose a tag to compare
Add the ability to generate limited FoundationDB logs

This commit adds a limited ability to generate FoundationDB logs. There's more
variants to be added and any fields in the existing variants that have an
internal complex structure have been dropped.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

0.3.5

01 Jul 21:24
45511f1
Compare
Choose a tag to compare
Crash when a worker crashes (#38)

* Crash when a worker crashes

We have discovered situations where file_gen runs out of disk space and then
quietly stop. This happens when testing vector once vector falls behind.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

* Always truncate files on startup

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

0.3.4

01 Jul 19:34
cdd9dc0
Compare
Choose a tag to compare
Make generated data less blank (#37)

This commit ensures that the data we generate from Ascii and Json has a definite
size to it, primarily by selecting from a fixed array of sizes. This is... a
little less arbitrary than I would have liked but it's better than a file full
of blank lines.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>

0.3.3

01 Jul 18:25
ed568b2
Compare
Choose a tag to compare
Use less CPU for slow targets (#36)

This commit re-introduces buffered writing, using less CPU when we have slow
targets. Once we have a need for GB/s range writing we'll need to figure
something else out but for now this is good enough. I'm more interested in
addressing generated data quality.

Signed-off-by: Brian L. Troutwine <brian@troutwine.us>