Routing commands

To list every ruleset with its revision and priority:

To print the current document for one ruleset:

To read a past revision instead of the current one:

To create or replace a ruleset in full:

To write only while the ruleset is still at a known revision, pass --if-revision. The write fails if another author has changed the ruleset in the meantime:

To retire a ruleset:

The record of a retired ruleset survives its deletion.

To add or replace one rule without sending the rest of the ruleset:

To remove one rule:

To see what a ruleset would decide for a sample request, with no traffic involved:

Rulesets are evaluated in priority order. To read the order set for a ruleset:

To change it:

To list every change made to a ruleset, with its revision and who made it:

To list what is registered, with retired entries omitted:

To print one classifier as it is stored:

To register a classifier:

Registration is immutable. Sending the same document again under the same id succeeds, and reinstates the entry if it had been retired. Sending a different document under an existing id is refused. A retrained model is registered under a new id.

To retire a classifier:

Retirement is unconditional. Nothing checks whether a rule still names the classifier, so repoint any rule that selects it before retiring it. The command asks for confirmation first.

To list the registration, retirement, and reinstatement of a classifier, with who made each change and when:

akka optimize use-cases covers the use cases discovered in traffic. The aliases use-case and uc are accepted. Discovery runs against live traffic. The working set is what has been discovered so far, and a manifest fixes that set so it can enforce routing. See Defining use cases for what a use case is and how one is discovered.

akka optimize routing-policies states what serves a use case, and in what share. The aliases routing-policy, policies, and policy are accepted.