Vlink monitoring provides visibility into the performance of destination URLs and rules. Its purpose is to help users understand:

• Which destination URLs are included in API responses.
• How often rules are triggered.
• How effectively rules cover destination URLs.

This insight allows users to optimize rules, improve link selection, and ensure API responses are relevant.

Destination URLs #

On this page, you can also see which URLs have been returned by the API in the past 30 days, how often and by which rules. The URL distribution column indicates the number of times a URL was included in API responses during this period.

• Green badge: If the URL appeared at least once in responses over the past 30 days. Clicking it opens a pop-up showing which rules returned the URL and how many times each rule included it.
• Red badge: : If the URL never appeared in responses over the past 30 days.

The destination URLs export includes:

• Included in response: True/False depending on whether the URL appeared in responses.
• Number of times in response: Number of times the URL appeared.
• From rules: Rules that returned the URL in the last 30 days.

Rules screen #

The rules screen provides insights into how each rule has performed over the past 30 days. In the table, you find the following columns :  

• #Triggers : It’s the number of times a rule has been triggered in API responses during the past 30 days calculated from cache miss and hit logs whether it returned enough links or not. 
• #Responses with links :  It’s the number of times a rule has been triggered in API responses and returned enough links (as defined in the settings) during the past 30 days calculated from cache miss and hit logs.
• Rule coverage : Percentage of destination URLs returned by the rule (Number of unique destination URLs returned by a rule / total number of destination URLs x 100).

Coverage is dynamic, if URLs are added or deleted, percentages may change even if a rule’s output remains the same.

📝The API usage count is calculated from the 1st to the last day of the month and resets at the start of each new month. Additionnaly, the total API usage counts every successful request and response (HTTP 200), regardless of whether the response yielded enough results or not. Trigger frequencies displayed in the table are based on a rolling 30-day window, independent of calendar months. These metrics should not be directly compared.

30-day window calculation #

📝All monitoring data and statistics are based on a 30-day window. Vlink uses caching to optimize API performance. Each API response (hit or miss) is included in calculations for the 30-day period.

• Cache miss: When a request has no cached response, Vlink rules are executed and results are saved for future requests.
• Cache hit: If a cached response exists, it is served directly, and rules are not re-executed.