Operations | Monitoring | ITSM | DevOps | Cloud

Latest News

PyCon 2019 - Scout brings APM for Python

The 2019 edition of PyCon USA takes place over the next few days in Cleveland, Ohio. Scout is delighted to be there, sharing our APM tool with the Python community. Plus, we'll have great t-shirts and stickers for you, and we love to get geeky - one of our lead product engineers, plus two of our smart support engineers, are working the booth, ready to help you figure out your Python performance problems.

Infrastructure Ops in 2019 - How Legacy Technology Compounds Technical Debt (1/2)

In today’s software-driven economy, every organization faces an imperative to modernize the way they deliver software in order to adapt and enable the digital era — or perish. Digital transformation across industries is driving the need for IT to enable Cloud-Native applications. This has led enterprises to adopt Kubernetes as the most effective way to support cloud-native architectures and to modernize their applications and IT infrastructure.

Monitor Microsoft Hyper-V with Datadog

Hyper-V is a hardware virtualization platform used to create and run virtual machines on Windows host systems. Hyper-V allocates resources from the physical hosts it runs on to the virtual machines it creates. If those resources are spread too thin, virtual machines may encounter slow performance and startup failures. With our new integration you can monitor the health of every layer of your Hyper-V stack: physical hosts, virtual machines, and all of the applications and services running on them.

Cloud Comparison: Oracle, IBM, Alibaba

Each year we eagerly await the publication of the RightScale (now Flexera) State of the Cloud report to see which technologies and players are trending in the cloud ecosystem. In this year’s report (2019) one of the interesting takeaways is that in 2018 public cloud spending grew three times faster than private cloud and companies intend to spend almost 25% more on public cloud in 2019 than they did in 2018.

The Lifecycle of a Request

Most Rails developers should be pretty familiar with this work flow: open up a controller file in your editor, write some Ruby code inside an action method, visit that URL from the browser and the code you just wrote comes alive. But have you thought about how any of this works? How did typing a URL into your browser's address bar turn into a method call on your controllers? Who actually calls your methods?