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

fix config field - events notifier #779

Merged
merged 1 commit into from
Dec 22, 2023
Merged

fix config field - events notifier #779

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
14 changes: 9 additions & 5 deletions docs/sdk-and-tools/notifier.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,6 +175,10 @@ file that can be used to configure the service.
There are some general configuration options, which should be fine with their default values:
```toml
[General]
# CheckDuplicates signals if the events received from observers have been already pushed to clients
# Requires a redis instance/cluster and should be used when multiple observers push from the same shard
CheckDuplicates = true

# ExternalMarshaller is used for handling incoming/outcoming api requests
[General.ExternalMarshaller]
Type = "json"
Expand All @@ -188,15 +192,12 @@ There are some general configuration options, which should be fine with their de
Type = "bech32"
Prefix = "erd"
Length = 32

# CheckDuplicates signals if the events received from observers have been already pushed to clients
# Requires a redis instance/cluster and should be used when multiple observers push from the same shard
CheckDuplicates = true
```

:::info
Starting with release `v1.2.0`, `CheckDuplicates` field has been moved from `ConnectorApi` section to
the newly added `General` section.
the newly added `General` section. Please make sure to put `CheckDuplicates` field before other inner
struct fields in `General` section.
:::

There are 2 ways to connect observer node with events notifier service:
Expand Down Expand Up @@ -231,6 +232,9 @@ There is a separate config section `WebSocketConnector` that has to be aligned w
# Signals if in case of data payload processing error, we should send the ack signal or not
BlockingAckOnError = false

# Set to true to drop messages if there is no active WebSocket connection to send to.
DropMessagesIfNoConnection = false

# After a message will be sent it will wait for an ack message if this flag is enabled
WithAcknowledge = true

Expand Down
Loading