Failover Console Guide

This page provides a guide to the Failover entity in the Namirasoft Inference Console. It defines the concepts and configuration fields used when creating and managing Failovers. Use this guide to understand the purpose and behavior of each setting available during Failover configuration.

What Is a Failover?

A Failover in Namirasoft Inference tries its targets in a set order, so requests keep moving. It sends a request to the first target, and if that target does not respond within its timeout, it moves on to the next target, and so on, until one responds. Each target is an inferencer, which can be a Model or another routing configuration.

 

A Failover is used by supported Namirasoft applications, such as Namirasoft Expert and Namirasoft Job Arranger, in the same way as a Model. When a supported application sends a request, the Failover works through its targets in order until it receives a response.

The Challenge a Failover Solves

When an application depends on a single model, a slow or unavailable provider leaves requests without a response and no defined path to continue.

 

Common challenges include:

 

• Single point of dependence: With only one model, there is no alternative to turn to when a provider is slow or unavailable.
• Provider interruptions: A provider outage or a delayed response can hold up requests with no automatic next step.
• Manual recovery: Switching to another model during an interruption would otherwise require changing each application.

How Namirasoft Inference Solves the Problem

A Failover lets you define an ordered list of targets and a timeout for each. Requests try the first target, and when a target does not respond in time, the Failover automatically continues with the next available target. This keeps requests moving during a provider interruption, without changing the applications that use the Failover.

Overview of Failover Fields and Options

Below is a detailed explanation of the fields available when creating or managing a Failover. Understanding these fields helps ensure your Failover is configured correctly for your requirements.

• ID (String): This is a unique identifier automatically assigned to the Failover when it is created. The system uses it to track, reference, and manage this specific Failover. This value is auto-generated and cannot be modified.

• User ID (Namirasoft Account’s ID): This is the unique identifier of the Namirasoft Account user who owns this Failover. It is used internally for permission control, audit logging, and access management.

• Workspace ID (Namirasoft Workspace’s ID): This is the identifier of the workspace this Failover belongs to, as defined in Namirasoft Workspace. A workspace is a shared organizational space where teams group their configurations, projects, and members.

• Name (String): This is a label used to identify this Failover in the console. A good name clearly describes its purpose, for example: “Primary with Backups” or “High Availability Chain”.

• Description (String, optional): An optional note describing this Failover and its purpose. It is for your reference and does not affect routing.

• Targets (List): The inferencers this Failover tries, in order. Add one or more targets, each with the following:
  • Type (Enum): The kind of target, one of Model, Load Balancer, Failover, or Race. Because a target can itself be a routing configuration, Failovers can be combined with other strategies.
  • Target: The specific inferencer, of the chosen Type, that receives the request when it is this target’s turn.
  • Timeout (Integer): The maximum time to wait for this target to respond before moving on to the next target.

• Created At (DateTime): This is the date and time when this Failover was created. This value is automatically generated and cannot be modified.

• Updated At (DateTime): This is the date and time when this Failover configuration was last modified. This value is updated automatically whenever any field is changed.