Ownership & scope

Every log server in Xelynx belongs to exactly one company. That ownership decides who can query the server, and — just as importantly — which subscribers its logs can be attributed to. As the main ISP you own and see every server; a reseller only sees the servers granted to it. This page explains that model and how you delegate access down the reseller chain.

Server ownership

A log server is owned by one company at a time: the main ISP by default, or a reseller once it has been handed down. When you view the server list, the ISP sees all servers, while a reseller sees only the servers it owns plus any owned by its own sub-resellers. Servers that sit below you in the tree carry a small owner pill showing the company chain, so you can tell your own servers apart from ones you have delegated.

Attribution follows ownership

Ownership also scopes log matching. When Xelynx resolves a NAT log to a subscriber, it only considers customers of the company that owns the server the log came from. So a reseller's server attributes connections to that reseller's own customers, and the ISP's server to the ISP's direct customers — a log is never matched across a company boundary. This keeps each company's search results limited to its own subscribers.

Delegating to resellers

You grant a reseller access to Syslogs from its detail page. First flip the Syslog Access toggle on — this lets the reseller open the Syslogs area at all. Then, under Assign Syslog Servers, toggle the individual servers you want to hand down; each shows as Assigned or Not Assigned. Assigning a server moves its ownership to that reseller, who can in turn delegate it further to its own sub-resellers. Turning a server off revokes it back to you, and turning the access toggle off revokes every assigned server at once. Servers already assigned to a different reseller aren't offered, so a server can never be in two places at once.