Versions Compared

Old Version 23

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version Current

changes.mady.by.user Gill Houghton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

The ‘Filters' are applied to the respective server(s) only. If connection is switched to another server within the same server set, filters are not applied and the required Sparkplug B subscriptions will be used.

Ensure that any Access Control Lists (ACLs) configured on the server match the Group or Group/EdgeNode configured in the Namespace Filter


Example 1 for the Sparkplug B namespace

A system with three Edge Nodes publishing data using the Sparkplug B protocol with Groups IDs Edge1, Edge2 and Edge3 where MQTT Engine is only interested in we want to limited MQTT Engine to data coming from Edge2.

We would configure Setting the Sparkplug B Default Namespace Filters for a Group ID of 'Edge2' will ensure that only this Group ID will be included in the MQTT Engine subscription.


Image Added



Example 2 for Sparkplug B namespace

A system with one Edge Node configured with two Server connections - one using the Sparkplug B protobuf format and the other using the Sparkplug B JSON formats.

The Edge Node has two Transmitters, one using each server with unique Sparkplug Group IDs of "Group1JSON" and "Group1".

Setting the Sparkplug B Default Namespace Filters for a Group ID of 'Group1' will ensure that only this Group ID will be included in the MQTT Engine subscription and MQTT engine will never receive the JSON formatted Sparkplug B messages.

Image RemovedImage Added



MQTT Engine Namespaces Custom - Sets

...