Page 2 of 2. Showing 18 results (0,019 seconds)
Systemload Feature
information to the rest information service endpoint: http://localhost:8888/services/information/systemload_cpuWebSocketClient
This transport handler connects to a websocket server. See Reading Query Results via REST/Websocket for an example.OdysseusSource
It is always possible to access any output of any sink in Odysseus (same or other instance) with Reading Query Results via REST/Websocket. Because the URL changes everytime when the serving query changes, this operator allows to login to the (other) Odysseus instance and retrieve the necessary values to accessGrafana
) Configuration -> Data Sources Select Others -> odysseus Server URI: ws://localhost:8888/ (REST-port of a (here local) odysseus server) Leave API Key empty 5Pattern 1: Preprocessing
'], ['sublist(splittedName,1)','nameAsList2'], ['rest(splittedName)','allLastElements'] ] }, presplitted ) Remark: In some casesOdysseusNet Configuration
">filestore</entry> <entry key="net.nodemanager.filename">C:/Users/Marco/odysseus/store/nodes.store</entry> <entry key="net.node.communicator">rest</entry> <entryConsole Commands
with the REST based communication in a Master/Worker scenario. The following commands are supported: Configuration of OdysseusNet Command Description ExampleJenkins
eine Basis-Platform als Hauptanwendung gibt, die nicht aktualisierbar ist und der Rest - als das komplette eigentliche Odysseus - als ein zusätzlichen Feature