Cascading livestatus of several remote sites on a single port

2 votes

We are asking if possibile in future release to introduce this feature:

it's like with cascading livestatus but not quite the same.
In shorts we would like to have an option that gave us the possibility to have a viewer (a site different from the master) that has the same configuration (tag, folder, views, rules) synced with the master without (like we do now) having to link every slave to both master and viewer so with just one connection (no 1 port for each slave like cascading and we can't have synced config by the way).

By now that we had to add each slave on master and slave so it's not much different with cascading.

In the actual configuration I think that each service is counted doubled (because it's like if we have 2 master), so with cascading I think we should at least avoid this right?
And also there's a temporal limit for using the licence, we haven't configured yet for this reason, we have a limit on service so having doubled it's not good.

Under consideration Site management Suggested by: Biagio (06 Jul, '23) • Upvoted: 08 Mar • Comments: 2

Comments: 2

07 Jul, '23
Robin Gierse
Hi Biagio!

Please appreciate, that we cannot discuss commercial or contractual details and specifics here.

So let me try to distill your request into the technical essence:

You want to be able to use Cascading Livestatus in a way, that you do not want each remote site to be accessible on the central site at a different port. Rather you want to have one single port on the central site, where you can query all remote sites including the central site.

Is that about right?
10 Jul, '23
Robert Sander
I do not think that this is technically possible.

Second I do not think that just viewing the services in another instance doubles your subscription usage, but IANAL. Please check that with the sales team.