Versions Compared

Old Version 22

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version 23

changes.mady.by.user Gill Houghton

Saved on

Key

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

...

In this instance the Access Control Lists (ACLs) on Servers B and C may not allow for the subscriptions required by MQTT Engine for the Sparkplug B protocol. Associating the Sparkplug B namespace only with Set 1 will disable the namespace for the two server connections associated with Set 2.


Anchor
NamespaceDefaultFilters
NamespaceDefaultFilters
MQTT Engine Namespaces Default - Filters

The MQTT Engine Namespaces > Default > Filters tab allows for specific Group or Group/EdgeNode combinations to be included in the MQTT Engine subscriptions to specific MQTT Servers. 

This allows you to exclude incoming messages from being parsed at Engine using the configured namespace.

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 for the Sparkplug B namespace

Setting the Group ID to 'Location1' will limit the subscriptions on the specific server to:

  • spBv1.0/Location1/#
  • spBv1.0/STATE/primary_host_id

Setting the Group ID to 'Location1' an Edge Node ID to 'Stream1'  will limit the subscriptions on the specific server to:

...

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 data coming from Edge2.

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


Image Added

...



MQTT Engine Namespaces Custom - Sets

...