Home→Orchestration

Testing and Deploying Your System

Before deploying to production, it's crucial to thoroughly test each component and their interactions. Testing on Naptha involves three main steps: Local testing without Node, Testing on local Node with local Hub, and Testing on hosted Node with hosted Hub.

1. Testing the Orchestrator

The orchestrator test verifies the coordination between components and proper data flow through the system.

Note: In order to test on a local or hosted node, you'll need to add version tags to your module and push them to your GitHub repository. You'll also need to update your deployment.json file with the latest configuration ensuring it has a name, description, parameters, module_type, module_version, module_entrypoint, and execution_type fields.

2. Testing on Local or Hosted Node

This involves running your own Naptha Node and Hub locally. The module template readme has a Test the Module on a Local Node (with a Local Hub) section with the most updated instructions on how to do this.

3. Deploying to Naptha

Creating and Installing the Orchestrator

Running Analysis

Monitoring and Maintenance

System Status Commands

Troubleshooting Common Issues

  1. Agent Connection Issues

    • Verify worker node availability
    • Check API keys and permissions
    • Review network connectivity

  2. Data Flow Problems

    • Verify data formats
    • Check agent response structures

  3. Performance Issues

    • Monitor resource usage
    • Review concurrent request handling
    • Check rate limits on external APIs
Production Best Practices

  1. Regular Testing

    • Schedule periodic test runs
    • Validate data quality
    • Monitor response times

  2. Version Management

    • Track component versions
    • Document dependencies
    • Plan updates carefully

  3. Error Handling

    • Implement comprehensive logging

Need deployment support? Join our community where we discuss advanced deployment patterns →

PreviousNext