LogServer
Introduction
The LogServer serves Datastore data using the same protocol as CDPLogger's built-in server. Useful to for example publish LogWriter data to Database Graph Widget or ValueLogReader and EventLogReader blocks.
Datastore to Serve
Datastore is the backend used by LogWriter, usually some database. To serve the data from the datastore, copy the configuration from the LogWriter block to the LogServer block.
Properties
| Property | Description |
|---|---|
| ServerInterface | A network interface defined in the application node. The LogServer component will listen on the selected interface. Leave empty to listen on all interfaces. |
| ServerPort | The port the LogServer listens on. The default is 17000. |
Viewing Served Data
There are several options to view logged data through the log server:
- Using CDP Studio Analyze mode Historic Data functionality which will detect a running CDP Logger or LogServer and connect to it. The Analyze mode can also be used to export the logged data to CSV format.
- Making your own GUI application that includes Database Graph Widget.
- Python code can query values from a running CDP Logger or LogServer using the PythonCDPLoggerClient.
- The ValueLogReader and EventLogReader sequencer blocks can be used to extract and process logged data.
The selected Datastore might provide other custom ways to view logged data. See the manual for the selected datastore to get specific information on that.
Note: CDP does not currently provide any widgets for browsing logged event data (e.g. CDPAlarm Set, Clear and Acknowledge events). Datastore-specific third-party tools must be used. If necessary, use the EventLogReader sequencer block and connect it to a LogWriter block to export event data to a different datastore, for example to CSV - see the example here.
Get started with CDP Studio today
Let us help you take your great ideas and turn them into the products your customer will love.