On 1 September 2021, 4 new filters will be released that better help Pulsar make intelligent decisions when steering traffic. Because the Pulsar Sort and Pulsar Stabilize filters are being deprecated, you should transition to the new filters as soon as possible. You have 3 options to complete the migration:
- Transition with the assistance of NS1: Contact us to set up a session to learn more about the new features, then migrate to the new filters with our help. You can reply to the announcement ticket or reach out to your CSM to schedule.
- Transition without NS1’s assistance: Explore the new filters and configure them on your own.
- Automatic transition by 1 October 2021: Do nothing, and NS1 will automatically transition your existing filter configuration to use the new filters.
This update provides filters that utilize performance and availability metrics for decision-making in your Filter Chain. These filters are more flexible than the current Pulsar Sort and Pulsar Stabilize filters in that they allow you to use performance and availability metrics in separate filters so that you can determine the order in which you want the filters to be executed. The 4 new filters were designed to replace the existing filters, both of which will be deprecated on 1 October 2021.
Table of Contents
- How do these filters affect my current threshold settings?
- What is the equivalent of the Pulsar Stabilize filter?
- What is the equivalent of the Pulsar Sort filter?
- Am I billed differently if I use the new filters?
- Will this impact the performance of Pulsar decisions?
- How will reporting work?
- How do I make the transition to use the new filters without NS1’s help?
- If NS1 completes the transition, when will that process be complete? How will I be notified of the changes?
- Will there be an interruption in service if NS1 completes the transition?
- What if I use Terraform?
How do these filters affect my current threshold settings?
You can now set thresholds at the filter level. These thresholds apply globally to all answers that have Pulsar metadata attached. If you need to override these settings, you can override the threshold at the answer level in the pulsar metadata of the answer.
What is the equivalent of the Pulsar Stabilize filter?
The Pulsar Availability Threshold and Pulsar Performance Stabilize filters are intended to replace the Pulsar Stabilize filter. These filters do not have to be used in tandem with each other. If you are concerned about availability, these two filters work best together; if you’re concerned about performance, you can use the Performance Stabilize filter on its own.
To make the most of both filters, you must:
- Attach a Pulsar job to the metadata of the answer.
- Set the availability or performance thresholds for the filter at the filter definition level.
- Set a Pulsar Performance Stabilize threshold.
- (Optional) If you want to specify a different threshold for specific answers, define that threshold in the answer metadata.
What is the equivalent of the Pulsar Sort filter?
The Pulsar Availability Threshold and Pulsar Performance Sort filters are intended to replace the Pulsar Sort filter. You should use the Availability Threshold filter before the Performance Sort filter in that order; the Availability Threshold filter removes the answers with availability values that fall under the set threshold, and the Performance Sort filter prioritizes the best-performing answers.
You can optionally enable the Sort from the worst value configuration option to reverse the sorting behavior. If sorting by the default behavior, any answer that is above the threshold is removed. This can be useful if, for example, you are setting a threshold for latency, where a higher value can slow the flow of traffic. Conversely, your threshold could be based on bandwidth. if you sort from lowest to highest, the lowest-performing answer will be discarded.
To make the most use of these filters, you must:
- Specify the threshold for availability.
- Ensure that a Pulsar job is attached to the metadata of the answers that you want to be steered by the filter.
Am I billed differently if I use the new filters?
There will be no changes to how Pulsar is billed. If at least one Pulsar filter is included in the Filter Chain, NS1 considers that a single Pulsar query or decision. You will be charged by the number of filter chains per record and not the number of filters per record.
Will this impact the performance of Pulsar decisions?
These changes will not change the performance of Pulsar decisions. The new filters simply make it easier to create a policy that meets your needs.
How will reporting work?
Decision reporting has not changed. To support existing semantics, we ensure that decisions are recorded as the winning answer of the last Pulsar filter in a Filter Chain.
How do I make the transition to use the new filters without NS1’s help?
You can follow the instructions in this article.
Contact us via Support if you have any questions.
If I want to migrate to the new filters without NS1’s assistance, how soon must I transition to the new filters? When does NS1 recommend that we migrate?
You must transition to the new filters by 1 October 2021.
If NS1 completes the transition, when will that process be complete? How will I be notified of the changes?
The migration process will be complete on or before 1 October 2021. We will inform you before the migration takes place to ensure a smooth migration, and Support will contact you when the migration is complete.
Will there be an interruption in service if NS1 completes the transition?
No. NS1 aims to complete transitions when there is the least amount of traffic on your account.