-
Data Discarded from Buffer
Hello everyone, I have a question regarding the buffer's handling of discarded data. Some time ago, the hard disk capacity of the Historian server (Receiver) reached its limit,…
-
Could not start SAF Sender Service
I've been getting this error: Could not start the "SAF Sender Service" with administration endpoints. Even after restarting the sender service multiple times , the error doesn't go away.…
-
Unable to connect to receiver endpoint issue
Hello Everyone. I can't get a computer (with a logger installed) in my fleet to communicate with my Historian computer . This is the 26th dataset I've created,…
-
Data Security (version 23)
The following article describes how data is secured In transit from Collector to Historian At rest in the Historian When accessed from the Historian Security In Transit Each Canary Collector is…
-
How to Configure a Proxy Server (version 23)
A proxy server may be needed when a stream of data needs forwarded through an intermediate level in the network, such as in the Purdue Model shown below where there is no direct path from Level 3 to…
-
How to Backup Buffered Sender Sessions (version 22)
By default, after a buffered session is processed by the Sender service, the session file is deleted. Configuring the system to backup the buffered files allows the data to be stored in a temp…
-
How to Backup Buffered Sender Sessions (version 23)
By default, after a buffered session is processed by the Sender service, the session file is deleted. Configuring the system to backup the buffered files allows the data to be stored in a temp…
-
Sender Tile (version 23)
The Sender service is responsible for sending data to the local or remote Receiver which, in turn, hands it off to the Historian to be stored. In the event that the Sender cannot connect to the…
-
Sender Tile (version 24)
Sessions - number of Sender sessions that logging data Tags - total number of tags being logged across all sessions Buffer - total number of TVQs that are waiting to be sent to a destination.…
-
Sender Tile (version 22)
The Sender service is responsible for sending data to the local or remote Receiver which, in turn, hands it off to the Historian to be stored. In the event that the Sender cannot connect to the…
-
Sender/Receiver Troubleshooting Guide (version 22)
The Sender & Receiver services are used to route data from the Collectors to the Historian. The data may flow through multiple Sender/Receiver nodes if proxy servers are in place before reaching the…
-
Sender/Receiver Troubleshooting Guide (version 23)
The Sender & Receiver services are used to route data from the Collectors to the Historian. The data may flow through multiple Sender/Receiver nodes if proxy servers are in place before reaching the…
-
Sender/Receiver Troubleshooting Guide (version 24)
The following article mentions the Sender & Receiver services that may still be used if a Collector is running a pre-24 version. Although the Historian is still compatible with the Sender & Receiver,…
-
Sender Credentials: Identity vs. User (version 23)
When the Sender service makes a secure connection to a remote Receiver service using the 'Net.TCP - Username' endpoint (55256), credentials are passed in to verify who the Sender is.…
-
Sender Credentials: Identity vs. User (version 22)
When the Sender service makes a secure connection to a remote Receiver service using the 'Net.TCP - Username' endpoint (55256), credentials are passed in to verify who the Sender is.…
-
How to Configure a Proxy Server (version 22)
A proxy server may be needed when a stream of data needs forwarded through an intermediate level in the network, such as in the Purdue Model shown below where there is no direct path from Level 3 to…
-
Data Collector Overview and Methodology (version 22)
What are Data Collectors? Data Collectors are the components of the Canary System responsible for transferring the process data from a client's data source to the Canary Historian.…
-
Data Collector Overview and Methodology (version 23)
What are Data Collectors? Data Collectors are the components of the Canary System responsible for transferring the process data from a client's data source to the Canary Historian.…
-
Configuring Disk Space Limit For Sender/Historian (version 23)
By default, the Sender and Historian will buffer or store data until there is only 1024 MB of disk space left, at which point, new data will be discarded.…
-
Configuring Disk Space Limit For Sender/Historian (version 22)
By default, the Sender and Historian will buffer or store data until there is only 1024 MB of disk space left, at which point, new data will be discarded.…
-
Installing Necessary Data Logging Components (version 22)
Methodology Understanding best practice architecture is important prior to installation. Whenever possible, Canary Collectors and the Sender should be installed local to the data source.…
-
Installing Necessary Data Logging Components (version 23)
Methodology Understanding best practice architecture is important prior to installation. Whenever possible, Canary Collectors and the Sender should be installed local to the data source.…
-
User Experience on the Latest Version 21.4.0.-273
Hello everyone, Anyone here who has upgraded their system to this latest version? Have you experienced/noticed some bugs/issues on it? Kinldy share it to us.…
-
Purge all messages in sender
Is there a way to purge all the buffered messages in the sender? I can purge single messages but when I try to select all and purge it seems like as the sender is processing the buffer,…
- Answered
-
Installation and Configuration of the Canary System (v21)
Topics in this session include: Architecture review of best practice system implementation Installation demo Canary Admin review Licensing your system Basic flow of data
Welcome to the community!