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.

Sign up for GitHub

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

docs: update telemetry design wording for clarity #126

Merged
merged 1 commit into from
Apr 11, 2024
Merged

docs: update telemetry design wording for clarity #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/docs/design/telemetry-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@

It is expected a large numbers of messages will be going through a system using the AWS Message Processing Framework for .NET moving from publishers to subscribers.
Users of the library need access to telemetry that shows how messages traverse through their messaging system. For example, if an alarm goes off for a message that
failed to process users need to be able to see where the message came from and how it got to the point it failed. Another need is total processing time for a message
exceeds an SLA the user needs to be able see where the bottlenecks are for messages being processed.
failed to process, users need to be able to see where the message came from and how it got to the point it failed. Another need is total processing time for when a message
exceeds an SLA, the user needs to be able see where the bottlenecks are for messages being processed.

### Tenets

Expand Down
Loading