Read-only; system-assigned identifier

Read-only; the current feed processing state.

Primary - Flags the Search feed used for all search queries. Only one feed can be Primary. Set from the Feeds command menu.

Open

The name attached to this feed.

Defaults to 100. The maximum number of objects sent concurrently to be processed.

Defaults to 1. The maximum amount of time (in seconds) before a batch is resent to be processed after a timeout. 

Enabled - (default) Swarm storage indexes all object metadata, including baseline and custom metadata fields.
Disabled - Swarm storage indexes only the baseline metadata fields.

See Metadata Field Matching for a list of baseline and custom fields.

The IP addresses or server names are resolvable by DNS. Separate with a comma or space if entering more than one.
DNS must be configured on both the source and target clusters.

Defaults to 9200. The default port for a host.

Read-only; system-assigned name by which Elasticsearch references the Swarm feed.

1. Create a new ES alias pointing to the existing index:

   curl -i -X POST <ES-node>:9200/_aliases \ -d '{ "actions": [ { "add": { "index": "EXISTING·INDEX·NAME", "alias": "NEW·ALIAS·NAME" } } ] }'

2. Create a new index feed and specify the new ES alias created:

   curl -i -X POST --anyauth -u admin:ourpwdofchoicehere <swarm-node>:91/api/storage/feeds \ -d '{ "actions": [ { "add": { "index": "EXISTING·INDEX·NAME", "alias": "NEW·ALIAS·NAME" } } ] }'

1. Create an index feed through the UI as usual.

2. Remap the ES alias to the existing index:

   curl -i -X POST <ES-node>:9200/_aliases \ -d '{ "actions": [ { "remove": { "index": "NEW·INDEX·NAME", "alias": "NEW·ALIAS·NAME" } }, { "add": { "index": "EXISTING·INDEX·NAME", "alias": "NEW·ALIAS·NAME" } } ] }'

3. Delete the new index created for the new feed:

Occasionally it is desirable to pause feed processing to perform system maintenance. Pause the search feed before stopping the Elasticsearch service in the search cluster. Return to the action menu and select the Resume action to resume feed processing after completing system maintenance.

Select the 'Make primary' option from the feed actions menu to change which search feed is the primary feed used for all search queries for Search feeds only.

Object data is sent to the feed target in near real-time (NRT) as they are are written or updated. Any objects unable to be processed immediately are retried each HP cycle until successful, at which point they are marked as complete and are not resent. Select the Refresh option from the feed action menu, which verifies and rehydrates all previously sent content to the Elasticsearch cluster, if a data loss failure occurs on the remote feed target and a restore from backup cannot be completed. This process takes some time, as it must revisit all objects in the cluster.

For search feeds, if an Elasticsearch index for the cluster does not exist, it is created. To recreate an existing index 'fresh' (such as for case-insensitive searching where case-sensitive was previously used), drop the existing index before refreshing the feed. 

When deleting a feed, it frees source cluster resources. To delete a feed, select the Delete option from the feed action menu and verify intention to permanently delete the feed. The deleted feed is removed from the remaining cluster nodes within 60 seconds. Delete the search data previously sent by the feed if desired.

Displays the SNMP Repository Dump for the selected node, for feed diagnostics and troubleshooting (see below).