The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.
When we think about WAN monitoring we usually start from the basics: the behaviour of remote communication links will directly affect the performance of our applications. Therefore, we understand that if traffic over the communications link experiences high levels of latency this will negatively impact the response time that our users observe when accessing the applications.
We've just rolled out a brand new feature: response time monitoring. As well as monitoring websites for uptime and downtime we now monitor the time it takes for each website to respond. The response times are logged and can be viewed in graphical format. Read on to see some pretty graphs of response times...
Our industry has long been relying on microservice-based architecture to deliver software faster and safer. The advent and ubiquity of microservices naturally paved the way for container technology, empowering us to rethink how we build and deploy our applications. Docker exploded onto the scene in 2013, and, for companies focusing on modernizing their infrastructure and cloud migration, a tool like Docker is critical to shipping applications quickly, at scale.
Last week we finished adding more uptime monitoring capacity for our users that are working out of Australia, to provide faster uptime monitoring.
Retune AB manages a variety of Ubiquiti devices -- wireless data communication products for enterprise and wireless broadband providers. Naturally, we wanted to bring these in under monitoring. However, Ubiquiti does not expose real-time CPU or memory metrics through SNMP in a way that we found reliable and these are some of the key values needed to verify the health of the device.
To many IT software teams, the mantra currently in vogue for team practice is “shift-left.” That refers to moving certain activities, such as code integration, build, and testing, earlier in the software development and delivery process. By shifting them to the left, the team knows more about code quality and performance earlier, allowing for corrective action and making them nimbler in response.