Endpoint Routing for Multiple TangoDBs

The Tango Table widget supports routing different attribute entries to different TangoDB backends.

Use this format in each fullNames entry:

<endpoint-selector>://<device>/<attribute>

Examples:

  • 1://sys/tg_test/1/state

  • 2://sys/tg_test/2/healthstate

  • TANGO_SECONDARY_HTTP_URL://sys/tg_test/3/status

Supported selectors

The <endpoint-selector> can be:

  • A numeric selector such as 1, 2, 3

  • A named selector such as TANGO_SECONDARY_HTTP_URL

The selector value is passed as the GraphQL endpoint variable exactly as written.

Fallback endpoint option

The widget also has a configuration option endpoint:

  • If an entry has an explicit prefix, that prefix is used.

  • If an entry has no prefix and endpoint is set, the fallback endpoint value is used.

  • If an entry has no prefix and endpoint is empty, the default route is used (no endpoint variable is sent).

Notes

  • You can mix prefixed and unprefixed fullNames entries in the same widget.

  • tango://host:port/device/attribute is treated as a Tango host-qualified path, not as an endpoint selector.