Gateway Hub Connection

Enables/disables publishing to Gateway Hub.

Gateway Hub and Publish to Kafka and Nanomsg can be enabled at the same time. Errors generated by attempting to publish to Gateway Hub do not affect the operation of Publishing. Similarly, errors generated by attempting to publish using Publishing do not affect the operation of Gateway Hub.

Note: Gateway Hub publishing is not available from shared Gateways. Instead, you must enable publishing from the source Gateways.

Caution: After you have started publishing to Gateway Hub, be aware that temporarily disabling publishing may result in Gateway Hub containing references to obsolete or deleted items. For example, if a managed entity is deleted, the Gateway cannot buffer this information and the Gateway Hub is not notified of the deletion when publishing is resumed. It is recommend that once started you do not disable publishing from the Gateway to Gateway Hub.

Specifies a comma-separated list of host/port pairs to use for establishing the connection to Gateway Hub. The adapter makes use of all servers irrespective of which servers are specified here for bootstrapping - this list only impacts the initial hosts used to discover the full set of brokers. Please refer to the description of bootstrap.servers in the Kafka documentation for more information.

Note: The technology used to publish from Gateway to Gateway Hub is internal and may change in the future.

These additional settings control how the adapter is loaded, or are settings interpreted by the adapter itself.

Each setting is entered on one line, and each line specifies one key-value pair. Each setting (key) starts with one of two prefixes:

• adapter. — control the way the adapter is loaded.
• kafka. — settings interpreted by the adapter.

Settings with the prefix adapter. are:

• adapter.library.path — specifies the location of the shared library that implements the adapter. The default location is the lib64 sub-directory of the Gateway's working directory. An alternate location can be specified as a path relative to the Gateways's working directory, or as an absolute path (as in the example above).
• adapter.gateway.name — used with the topic prefix to construct a unique consumer group id for the gateway. The default group id is <topicprefix><gatewayname>, e.g. geneos-DevGateway. If necessary, you can override the gateway name part with this setting.

Settings with the prefix kafka. used for secure publishing are :

• kafka.security.protocol — protocol used to communicate with brokers. Value is always ssl when used with Gateway Hub.
• kafka.ssl.ca.location — file or directory path to CA certificate for verifying the broker's key.

This section allows settings that cannot be set in cleartext, such as passwords, to be encrypted in the Gateway setup file. This has two fields:

• Name — name of the secure setting.
• Value — value of the secure setting. This can either be:
  • stdAES — AES 256-bit encryption. The password is entered in the Set password box.
  • var— a reference to a variable that provides a password in Operating Environment. References to invalid variables, or variables that are not AES-encrypted, are treated as errors.

Data type of the headline that appears in the dataview.

The data types include: string; boolean; float32; float64; int32; int64; date; dateTime. 32-bit types should be specified unless the data is of a size or precision that requires 64-bit types.

Specifies the units of measure of the data type that appears in the dataview.

Only certain data types have specified units of measure.

Name of the column that appears in the dataview.

Data type of the column that appears in the dataview.

The data types include: string; boolean; float32; float64; int32; int64; date; dateTime. 32-bit types should be specified unless the data is of a size or precision that requires 64-bit types.

Note: Columns declared as dateTime not in the form yyyy-mm-ddThh:mm:ss require an entry in Standardised Formatting.

Specifies the units of measure of the data type that appears in the dataview.

Only certain data types have specified units of measure.

This option should only be used for dataviews that display one value per row with values of a variety of types. For example, a Toolkit sampler with a summary dataview containing two columns - Name and Value, and three rows of varying data types - dateTime, int32, and float32, would be a good candidate for pivoting.

If enabled, the dataview is pivoted so row names become column headings and the heading of the single data column becomes the name of a single data row.

Specifies a name to uniquely identify the strategy.

Specifies what type of strategy to use. The following options are available:

• include filter — publish only the data items specified by the targets, their ancestors, and their descendants. The metrics, severity messages, snooze messages, and user assignment messages of all data items not explicitly or implicitly targeted are not published. Severity is propagated through published data based only on included data items.
• exclude filter — do not publish the data items specified by the targets or their descendants. Metrics, severity messages, snooze messages, and user assignment messages are not published for any targeted data items. Severity is propagated through published data based only on data items which are not excluded.

Note: If you specify both include filters and exclude filters, a data item is published if it is selected (directly or as an ancestor or descendant) by at least one include target and it is not selected (directly or as a descendant) by any exclude target.