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

Eventhub Stress Test Onboarding #28320

Merged
Merged
Changes from 1 commit
Commits
Show all changes
33 commits
Select commit Hold shift + click to select a range
31ef454
stress test initial setup
m-redding Mar 28, 2022
2c97223
initial setup of publish test after refactoring/app insights integration
m-redding Apr 6, 2022
7e67bda
added basic buffered test
m-redding Apr 11, 2022
bcf27f8
deployment infrastructure update
m-redding Apr 12, 2022
32d1a79
updated buffered producer test
m-redding Apr 15, 2022
99f6135
buffered producer test cleanup
m-redding Apr 15, 2022
d68b9a8
buffered producer test
m-redding Apr 15, 2022
3bb3cfc
buffered producer test
m-redding Apr 15, 2022
72de30e
Adding more scenarios and switching to event producer test
m-redding Apr 21, 2022
8e3ee3f
restructuring metrics
m-redding Apr 21, 2022
9c24f75
more metrics updates
m-redding Apr 21, 2022
7f63000
Merge branch 'Azure:main' into eventhub-stress-tests
m-redding Apr 21, 2022
2ee7f56
README updates
m-redding Apr 21, 2022
52bfa86
Merge branch 'eventhub-stress-tests' of https://github.com/m-redding/…
m-redding Apr 21, 2022
78cc71b
Update sdk/eventhub/Azure.Messaging.EventHubs/stress/README.md
m-redding Apr 22, 2022
a798c8f
Update sdk/eventhub/Azure.Messaging.EventHubs/stress/src/Infrastructu…
m-redding Apr 22, 2022
25ec412
initial refactoring
m-redding Apr 25, 2022
f16edd8
deploy yaml file updates
m-redding Apr 25, 2022
8c6ac6d
readme updates
m-redding Apr 26, 2022
dbb7258
Delete stress-test-resources.json
m-redding Apr 26, 2022
1013982
dockerfile updates
m-redding Apr 26, 2022
ae204ce
Delete stress-test-resources.json
m-redding Apr 26, 2022
bf4230b
comment and main updates
m-redding Apr 28, 2022
925888e
Update sdk/eventhub/Azure.Messaging.EventHubs/stress/README.md
m-redding Apr 28, 2022
a86d0a6
Update sdk/eventhub/Azure.Messaging.EventHubs/stress/src/Infrastructu…
m-redding Apr 29, 2022
518aa6d
Update sdk/eventhub/Azure.Messaging.EventHubs/stress/src/Configuratio…
m-redding Apr 29, 2022
eafe6a5
Update sdk/eventhub/Azure.Messaging.EventHubs/stress/src/Configuratio…
m-redding Apr 29, 2022
da89c76
feedback updates
m-redding Apr 29, 2022
c5cd920
Added Azure Event Listener
m-redding Apr 29, 2022
3dab67c
buffered producer options
m-redding Apr 29, 2022
02ce4ee
typo
m-redding Apr 29, 2022
2161001
Event Hubs Stress Test Onboarding
m-redding Apr 29, 2022
ca66f38
Event Hubs Stress Test Onboarding
m-redding Apr 29, 2022
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions sdk/eventhub/Azure.Messaging.EventHubs/stress/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,3 +49,15 @@ This test requires an event hub namespace, an event hub, and an application insi
All metrics and logging are sent to App Insights via the Instrumentation Key provided during the initialization of the test. A brief explanation of the metrics collection approach is described below.
- Any exceptions that occur are tracked by the telemetry client as exception telemetry. They can be accessed through the logs by filtering for exceptions, or through the application insights portal in the "Exceptions" blade. If an exception occured during send, the exception telemetry will include a "process" property containing "send"
- Successful enqueues and sends are tracked through Metrics. For the buffered producer, the total number of enqueues is tracked, and the actual sends include the ability to separate counts into partition Ids.
m-redding marked this conversation as resolved.
Show resolved Hide resolved

## Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.

Please see our [contributing guide](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/eventhub/Azure.Messaging.EventHubs/CONTRIBUTING.md) for more information.

![Impressions](https://azure-sdk-impressions.azurewebsites.net/api/impressions/azure-sdk-for-net%2Fsdk%2Feventhub%2FAzure.Messaging.EventHubs%2stress%2FREADME.png)
Copy link
Member

Choose a reason for hiding this comment

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

This png fails to load on the readme.

Copy link
Member

@jsquire jsquire Apr 26, 2022

Choose a reason for hiding this comment

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

Loads for me; it's one of our tracking pixels, so it will look like nothing. @benbp: Are you seeing it 404 or just nothing show up?

Copy link
Member

@benbp benbp Apr 26, 2022

Choose a reason for hiding this comment

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

@jsquire it looks like the problem is a missing F character in the url encoding: EventHubs %2 stress. I added a commit suggestion below.

image

It looks like this on the readme, that's how I caught it:

image

Copy link
Member

Choose a reason for hiding this comment

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

ahhh.... I see it now. Yeah, that's on me. Thanks for the catch!

Copy link
Member

Choose a reason for hiding this comment

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

Chrome/Edge do a nice job of fixing the malformed encoding. Checking in the browser worked.

m-redding marked this conversation as resolved.
Show resolved Hide resolved