Shoppers will scan their Amazon Go app at the store’s entrance, and the technology will track which items they pick up and add them ...
In time for spring training and site traffic spikes, the makers of the Louisville Slugger are implementing web application performance monitoring services from TeaLeaf Technology. The technology shrinks application failure fixes from days to minutes.
The makers of the Louisville Slugger are implementing web application performance monitoring services from TeaLeaf Technology Inc. in time for the start of spring training next week – and an anticipated seasonal spike in retail activity on the company’s web site. Hillerich & Bradsby Co., makers of the famed baseball bat as well as PowerBilt golf and Louisville Hockey products, is seeking to extend the reach of the Louisville Slugger brand online by tuning up performance at its year-old retail site, Sluggergifts.com.
The monitoring solution, TeaLeaf IntegriTea, which identifies, recreates and diagnoses web application failures, has been in use at the site for about two months, says Christopher Caudill, web developer at Hillerich & Bradsby. Prior to implementing the technology, failed transactions on the site might go unidentified and unaddressed for days, until the company heard from customers about applications failures and then tracked them down.
“Since deploying IntegriTea we’re able to recreate exact customer web sessions, reducing the time it takes to identify and fix problems from days to minutes,” says Caudill. The service also is helping the company understand and fix other performance issues, such as why ISPs had some difficulty creating secure socket layers on the site, and understanding when the home page stopped directing traffic to the site’s commerce pages.
The technology bridges the gap between traditional applications performance monitoring and system management tools, says Goeff Galat, vice president of marketing and product management at TeaLeaf. The software pinpoints and identifies within a unique user session where a problem occurs, critical to rapidly identifying applications failures. “No two customer interactions are alike,” he says.