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: Refer to lumigo Platform instead of Dashboard #488

Merged
merged 2 commits into from
Sep 11, 2023
Merged

docs: Refer to lumigo Platform instead of Dashboard #488

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0cbbaf9
docs: Refer to lumigo Platform instead of Dashboard
sagivoululumigo Sep 11, 2023
8916ef8
docs: lowercase platform
sagivoululumigo Sep 11, 2023
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
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -345,7 +345,7 @@ Without the scope provided by the iterator over `response["Messages"]`, `span_1`

A common pattern in SQS-based applications is to continuously poll an SQS queue for messages,
and to process them as they arrive.
In order not to clutter the Lumigo Dashboard with empty SQS polling messages, the default behavior is to filter them
In order not to clutter the Lumigo platform with empty SQS polling messages, the default behavior is to filter them
out from being sent to Lumigo.

You can change this behavior by setting the boolean environment variable `LUMIGO_AUTO_FILTER_EMPTY_SQS` to `false`.
Expand Down
Loading