strapline - putting your complex web systems to the test Home Search Contact

Services

Service intro
SV-Access
SV-Function
SV-Monitor 24/7
SV-Monitor new features
SV-Monitor Onsite
SV- Load
Why test?

e-Government Priority Outcome R25

 

  sv-monitor logo

24/7 Website Monitoring and Functionality Testing

Onsite Injector Monitoring - When external monitoring just isn't enough ...

sv-monitor example screen shot

There may be times when external monitoring services simply don’t provide you with the metrics you need. ISP problems particularly sporadic errors and Intranet performance are two such areas. But now monitoring ISPs and Intranets are not a problem with Onsite Monitoring.

Problems with your ISP? How can you prove it?

When your website isn’t performing well, it’s not always easy to identify the cause. Nor whether the problem is under your direct control. Load balancing systems, software applications coding, web and application servers are all things that you can readily influence. However, there’s one important area that you will often have little power over – the network, managed by the ISP or Hosting supplier.

With a sporadic error it’s is often difficult to prove whether it is due to the network, load balancing or session handling issues. So if you think that it’s down to your ISP, how can you prove it?

Onsite Injector Monitoring

SciVisum has developed Onsite Injector Monitoring to help to quickly identify and investigate differences between internal and external performance. An extension to the SV-Monitor User Journey monitoring service, we run a network of multiple injectors externally on the Internet, together with an onsite sampling injector outside of the load balancing and firewalls, but not outside the ISP’s or hoster’s network. Then by monitoring the same multi-page User Journeys on both injectors you can identify any differences in performance giving you the evidence you need if it’s a network issue with the ISP/hoster.

Errors that can be seen externally but not internally can’t be due to the client’s load balancing, web and application servers or software coding. The root cause is more likely to be the network between the data centre and the external Internet.

 

 

Are your Intranet services slow or error prone? Do you even know?

A recent survey by Evans Data of 400 IT managers and developers found that web-based applications for their internal staff and/or workflow processes are often unavailable - some for up to a day. And with the Service Orientated Architecture (SOA) approach - multiple services interacting to link applications or to perform a specific business process – on the increase Intraney performance is becoming increasingly cirtical.

However, monitoring the performance of internal web services can be more complex than traditional system monitoring.

We’ve developed an onsite test injector box to provide performance metrics for key Intranet applications and to analyse sporadic Intranet errors - errors that can be very difficult to identify in any other way.

Intranet testing can help you to decide which hardware upgrades will achieve the best ROI, whether any network WAN issues may need to be addressed and which elements of which applications will benefit from software re-factoring.

Key Intranet journeys might cover:

  • Call centre systems - and web-based booking
  • CRM systems used by call centre staff
  • Staff systems - time logging, or to handle the timesheets of temporary staff
  • Online Learning management systems
  • Web based warehousing
  • Specialist workflow or knowledge management portals – such as those used in the legal profession

>> More about SV-Monitor
>> More about SV-Monitor new features