Nice write-up @Richard Faulkner!
Isn't the biggest downside of the built-in agent that you have all individual NetScaler instances communicate to Citrix Cloud, instead of consolidating traffic?
c
Christian Jöns
12/05/2024, 10:52 AM
Nice write Up. 🙂 Thanks
r
Richard Faulkner
12/05/2024, 11:23 AM
It would be. But this is more for those who need an HA pair of NetScaler's just for gateway. We have small customers running workloads in AWS or Azure with a single HA pair that were looking at having to pay ~$50 per month for a 4cpu/8gb RAM instance just to license their NetScaler's. This will let them avoid that.
👍 5
💯 3
e
Eric Spicer
12/05/2024, 3:21 PM
Very nice, thanks for documenting that.
h
Henry Heres
12/14/2024, 9:42 AM
Feature parity is my gap for the builtin, the extra insights is very useful imho with the agent, would rather see it more simplistic and that it all works natively instead of depending on an agent. Wishful thinking for the future
j
Jan Tytgat
12/14/2024, 10:55 AM
Depending on the agent is purely from a processing/performance aspect. You don’t want to degrade NetScaler performance for the sake of depending on the agent.
The agent could be more lightweight as well, though…