etzel-mes commented on code in PR #27780: URL: https://github.com/apache/camel/pull/27780#discussion_r4275427395
########## components/camel-milo/src/main/docs/milo-client-component.adoc: ########## @@ -127,6 +127,31 @@ However Camel allows to wrap the actual value inside `RAW(…)`, which makes esc milo-client:opc.tcp://user:password@localhost:12345?node=RAW(nsu=http://foo.bar;s=foo/bar) ---- +=== Monitoring several nodes + +A consumer can monitor several nodes with the `nodes` option instead of `node` (the two options cannot be combined). +The consumer creates the monitored items of all nodes together and deletes them together when it stops. Every value +arrives in its own exchange, and the `CamelMiloNodeId` header holds the node ID as it was configured. + +The `nodes` option takes a comma-separated list of <<nodeid, Node IDs>>. The entries are trimmed, empty entries are +skipped and a node that is listed twice is monitored once: + +---- +milo-client:opc.tcp://localhost:12345?nodes=RAW(ns=2;s=line1/temperature,ns=2;s=line1/pressure) +---- + +A string node ID that contains a comma cannot be used in `nodes`; monitor it with the `node` option instead. Long lists +can come from a property placeholder, for example `+nodes=RAW({{tags}})+`. + +All nodes of the list share the `samplingInterval`, `queueSize` and `omitNullValues` options of the consumer and its +monitor filter (`monitorFilterType`, `dataChangeFilter*`). Tags that need a different sampling interval or deadband +need a consumer of their own. + +A node that does not exist on the server does not affect the other nodes. A node that cannot be monitored is +reported once with its status code and is not retried; restarting the route creates the monitored items again. To see +such nodes, set `omitNullValues=false`: the consumer then delivers one exchange with the bad status code for that +node, and the `CamelMiloNodeId` header names it. Review Comment: Regenerated in c91a91fb274, with the optional sentence. _Claude Code on behalf of etzel-mes_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
