You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
When a value for Global Max Mbps or Global Max Tps is defined through TP these values is not sent to TM and can not be seen at "api/monitor-config", consequently when the amount of traffic which is being delivered for DS reaches those values extra traffic won't be redirected to HTTP or DNS bypass FQDN or IP.
Expected behavior:
Values which are defined for Global Max Mbps or Global Max should be sent to TM. As a result when current DS traffic reaches those values TM is supposed to mark that DS unavailable and sent extra traffic to HTTP or DNS bypass FQDN or IP.
I'm submitting a ...
Traffic Control components affected ...
Current behavior:
When a value for Global Max Mbps or Global Max Tps is defined through TP these values is not sent to TM and can not be seen at "api/monitor-config", consequently when the amount of traffic which is being delivered for DS reaches those values extra traffic won't be redirected to HTTP or DNS bypass FQDN or IP.
Expected behavior:
Values which are defined for Global Max Mbps or Global Max should be sent to TM. As a result when current DS traffic reaches those values TM is supposed to mark that DS unavailable and sent extra traffic to HTTP or DNS bypass FQDN or IP.