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

readme: add notes about sending test data to FireLens #328

Open
wants to merge 1 commit into
base: mainline
Choose a base branch
from

Conversation

matthewfala
Copy link
Contributor

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@matthewfala matthewfala requested a review from a team as a code owner April 6, 2022 21:27
@@ -205,6 +205,10 @@ Then run `make cloudwatch-dev` or `make kinesis-dev` or `make firehose-dev` to b

To run the integration tests on your code, execute `make integ-cloudwatch-dev` or `make integ-kinesis-dev` or `make integ-firehose-dev`.

#### Sending Test Data to FireLens

Sometimes, an application generates logs at a particular throughput or format that reveals problems with FireLens. It may be difficult to isolate and reproduce the issue, due to sporadic errors, or inconsistent application state that result in varying log content over time. In these cases, the [FireLens Datajet](https://github.com/aws/firelens-datajet) highly configurable mock application can be used to deliver customizable logs at varying throughputs to various Fluent Bit input plugins, helping to reproduce an issue quickly and repeatably. It can be configured via a JSON file, or environment variables, to deliver logs to various input plugins asynchronously, with adjustable content and rates. FireLens Datajet can run locally or be dockized into a container image.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"dockized"

Also, please add this new section in the table of contents at the top

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

Successfully merging this pull request may close these issues.

2 participants