Customer can integrate Sinefa with Active Directory in order to view traffic information associated with AD User Details. Sinefa can provide support to partners on how to integrate with Active Directory via Live Chat available in Sinefa App.
Partner can also review this link to understand
how to integrate Sinefa with Active Directory.
Sinefa is not engineered to be used in internal LAN environment. Sinefa is best suited for internet facing or WAN facing traffic. To further understand how Sinefa can work in your environment, please check out the Sinefa Overview video below
Yes, 12 months historical data is the default setting currently. Sinefa is looking at introducing a chargeable service to extend this in the future but do not have details on it just yet.
Please feel free to contact your
rhipe Account Manager
if you need more information on this.
No, NQS can only be calculated between two Sinefa Probes so you would need to install a probe in ISP site to get that information.
For NQS to work, it will require probe at both ends of the traffic, such as
Branch A – Branch B
Branch A – Public Probe
This is because it uses a proprietary protocol that was sent between the Sin...
The Sinefa probe in Azure is currently used for Network Quality Service (NQS) only. Sinefa is working towards enabling traffic visibility for the Azure probe.
To learn more about
Sinefa Network Quality Service
One of the Azure NQS use case is for customer who has critical apps running in Azure environment to be able to chec...