Skip to main content

Introduction

Revision History​

DateAuthorSummary
06-NOV-2022TSgt. BernadotteInitial draft
19-JAN-2024TSgt. BernadotteAdded instructions for changing deployment directory
04-FEB-2026CW2 BernadotteAdded fix to import data into Elasticsearch 9+

Purpose​

This SOP is intended to instruct an operator on how to configure Metasponse in one of the following configurations:

  • Standalone
  • Semi-Centralized

Requirements​

  • Metasponse installer

Considerations​

Review the following table to help determine the best configuration for your mission:

ConfigurationDescriptionProsCons
CentralizedOnly the Metasponse server is used (via its Web interface).
  • Central view of all job data from all operators
  • Changes to custom plugins occur at one location
  • Multiple concurrent jobs are bottlenecked by server resources
Semi-CentralizedMetasponse is installed and executed from the MIP. The Metasponse server is used as a central database by Metasponse clients, but can still be used via its web interface.
  • Central view of all job data from all operators
  • Parallel execution from multiple MIPs increase speed
  • Connection to Metasponse server required to execute jobs/view data
  • Changes to custom plugins must be manual performed on all MIPs
StandaloneMetasponse is installed and executed from the MIP. The Metasponse server is not used.
  • Parallel execution from multiple MIPs increase speed
  • Distributed job data/no central view of all job data
  • Changes to custom plugins must be manual performed on all MIPs