6. Usage

• 6.1. Monitoring and Management
  • 6.1.1. Managing Ngenea Hub with systemd
  • 6.1.2. Using the Command-Line Tool: ngeneahubctl
  • 6.1.3. Docker Containers
  • 6.1.4. Hub Task Metrics
  • 6.1.5. Health Endpoints
• 6.2. Custom Workflows
  • 6.2.1. Defining workflows
    • 6.2.1.1. Filter Rules
    • 6.2.1.2. Runtime fields
  • 6.2.2. Running Workflows
    • 6.2.2.1. Discovery Steps
      • 6.2.2.1.1. Discovery Options
  • 6.2.3. Includes and Excludes
• 6.3. Jobs
  • 6.3.1. Housekeeping
• 6.4. Site Sync
  • 6.4.1. Troubleshooting
• 6.5. Bidirectional Site Sync
  • 6.5.1. Schedule
  • 6.5.2. Workflow
  • 6.5.3. Troubleshooting
• 6.6. Search
  • 6.6.1. Submitting a query
    • 6.6.1.1. Filters
  • 6.6.2. Retrieving results
    • 6.6.2.1. Proxies
    • 6.6.2.2. Parameters
    • 6.6.2.3. Merged results
    • 6.6.2.4. Results grouped by name
  • 6.6.3. Max Results
  • 6.6.4. Housekeeping
• 6.7. Controlling Bandwidth Usage
  • 6.7.1. Bandwidth configuration in the UI
  • 6.7.2. Checking Node status
  • 6.7.3. Registering Datastores
    • 6.7.3.1. Cloud IPAddresses
    • 6.7.3.2. Using manual IP addresses
  • 6.7.4. Linking a Datastore to a Site
  • 6.7.5. Applying the bandwidth
• 6.8. Configuration
  • 6.8.1. Global Configurations
    • 6.8.1.1. Available Settings
    • 6.8.1.2. REST API
    • 6.8.1.3. Settings Migration
  • 6.8.2. Site-specific Configurations
    • 6.8.2.1. Available Settings
      • 6.8.2.1.1. File Batching
      • 6.8.2.1.2. Dynamic File Batching
    • 6.8.2.2. REST API
• 6.9. Certificate Lifetime
  • 6.9.1. Viewing the Certificate Lifetime
  • 6.9.2. Modifying the Certificate Lifetime
  • 6.9.3. Summary
• 6.10. Feature Flags
  • 6.10.1. REST API
  • 6.10.2. ngclient
• 6.11. Actions
  • 6.11.1. Available Actions
    • 6.11.1.1. discover_nodes
  • 6.11.2. REST API
• 6.12. Limitations
  • 6.12.1. Site Sync
    • 6.12.1.1. Site Sync must only be used in one direction
    • 6.12.1.2. Site Sync only considers changes within an applicable time window for synchronisation
    • 6.12.1.3. Site Sync supports Independent Filesets
    • 6.12.1.4. Destination site Independent Filesets must exist prior to synchronisation
    • 6.12.1.5. Directory deletion is not supported
  • 6.12.2. Bidirectional Site Sync
    • 6.12.2.1. Bidirectional Site Sync implements eventual consistency
    • 6.12.2.2. Bidirectional Site Sync is only supported via schedules
    • 6.12.2.3. Bidirectional synchronisation is sequential
    • 6.12.2.4. Swapping files / Last write wins
    • 6.12.2.5. Renaming or deleting files and directories causes re-sending of data
    • 6.12.2.6. Renaming or files and directories on both bidirectional Site Sync sites causes duplication of data
    • 6.12.2.7. Creation or deletion of empty directories on site 1 does not synchronise to site 2
• 6.13. Iris
  • 6.13.1. Spaces API: Iris Integration and User Filtering
  • 6.13.2. Iris state
  • 6.13.3. Filtering Spaces by Username
  • 6.13.4. REST API
  • 6.13.5. Example Response with Iris Spaces
  • 6.13.6. Example Response When User Has No Accessible Spaces
  • 6.13.7. Summary