Managing instances

redirection.io agent instances are in charge of processing each request to find an applicable action to execute (a redirection, a SEO override, etc.). They also log all requests and handle the dialog with redirection.io APIs.

In the manager, you can see your redirection.io agent instances in the "instances" screen:

Each instance box gives details about a configured instance. You can get:

• the agent version. We strongly advise you to keep your agents up to date, so that you can use all the latest features of redirection.io. Our changelog gives informations about new releases.
• the logging status: this section provides details about the last logs reception. If your instance did not log since more than 10 minutes, it will display an alert.
• the rules status: this section explains if the agent is up to date and how many rules is has loaded. If your agent did not update since a long time, this section will display an alert and provide help about how to fix the issue.

The "instances" screen of the manager also allows to attach some parameters to your agent instances:

Allow the instances to log traffic

Each of our plans come with an unlimited number of logging instances. For example, consider that your website infrastructure is replicated and shared accross 8 frontend servers. You could want to replicate the redirection.io agent service across all these servers, and deploy an agent on all of these servers:

Our paid plans come without any limit on the number of agents that you can bind to your project. You can have as many instances as you want, but we limit the number of log lines per day per project to 2M log lines (with temporary bursts and spike protection). If your infrastructure layout uses many agents, or if you use the agents in staging or pre-production environements too, you can choose to (de-)activate the logging feature instance per instance.

To deactivate the logging feature for a given instance, follow these steps:

1. click on the small wheel on the upper right corner of the instance box
2. uncheck the "Logging instance" switch

From now on, this instance will continue to fetch redirection.io rules and properly redirect traffic, but it won't send logs back to the manager.

Activate the "test mode"

When maintaining a web stack, it is quite common to have a pre-production infrastructure, to run tests before deploying in production.

As for other parts of your stack, you may want to test and try redirections in pre-production before applying them to your production. This is exactly what the "test mode" allows: by enabling this mode on an instance, it will load all the rules of the ruleset, even non-published ones.

To enable the "test mode" for a given instance, follow these steps:

1. click on the small wheel on the upper right corner of the instance box
2. check the "Test instance" switch

From now on, this instance will load the "live" ruleset: newly created rules will be applied in seconds on this instance, even if they have still not been published.

Please note, however, that if the "DRAFT" rules in your ruleset exceed the number of allowed rules for your plan, these rules will not be pushed to the "Test instance" instances of your project - so, please check that the unpublished rules stay within the boundaries of the project plan.

Display or hide gone instances

In some infrastructure layouts, servers can have an ephemeral lifetime - think about scalability and on-demand instances. If this happens in your hosting environment, you may want to reduce the burden of seeing many "old" instances, by configuring the way instances are displayed. Simply hit the "Settings" button, at the top right of the instances list, and edit the instances settings.

By default, instances that did not log nor update the ruleset since more than 7 days are hidden - you may want to disable this behavior, or on the contrary to reduce the display duration.