Operations | Monitoring | ITSM | DevOps | Cloud

This post was originally published in JAXenter.com. Serverless is a relatively novel concept and cloud architectural model but has been advancing very quickly over the past 5 years. In this article, we’ve compiled a list of recent changes that are likely to shape how development teams use Serverless in practice. In this article, we’ll be heavily focussing on AWS serverless services. The cloud provider has been investing heavily in the advancement of Serverless.

Though there is an entire industry devoted to telling you otherwise, most people prefer to work for large organizations. On the one hand, their appeal makes perfect sense. Big employers offer higher salaries, better benefits, and a longer employee tenure. Yet, there are some noticeable wrinkles that come with life in a large organization. Chief among them, bigger companies often exhibit a poor overall Digital Employee Experience.

With the digital landscape shifting everything on the web, and companies fighting for better user experiences, your sites and applications are no longer just a part of your business, it is the business. But how do you to go about it and remain successful? This is where monitoring and performance management comes into the picture. Not only just for business people, IT teams have also a significant role to play in business growth and revenue optimization.

It’s been a long journey since I decided that the current version of Monitive is just not good enough for our customers. That it doesn’t scale how it should. That its interface isn’t responsive or suitable for mobile devices. That the inner workings are not flexible enough to allow further extensions and features. All this, because it was the very first usable iteration of Monitive, crafted around 2011.

Data ingestion and data analysis are the yin and yang of a time series platform. There are many resources to help you ingest data. Typical ingestions are agent-based, imports via CSVs, using client libraries, or via third-party technologies. Once your time series data arrives, analysis completes the circle and often leads to additional data collection, and so on and so forth.

The new NiCE Active 365 Management Pack 3.10 comes with tons of stunning new features. Register now for the public preview version.

Continuous integration is the first half of the acronym CI/CD, with Continuous Delivery completing the second half. In this three-part article, we look at the two halves of CI/CD to define and understand them, and then, in part three, we talk about how Uptrends fits into your CI/CD processes. Let’s get started at the beginning with continuous integration.

Earlier in the year, we launched the request details page in Raygun Real User Monitoring. This update brought the instance-level insights into page performance to help you understand exactly what caused poor performance and how to improve it. To complement instance-level insights, this latest launch brings the Latest slowest requests module to Real User Monitoring. Now, when viewing performance data for a specific URI, you can easily jump into the instance-level diagnostics for a specific slow request.

Network device monitoring with Simple Network Management Protocol (SNMP) gives you complete visibility into the health and availability of your network devices. Monitoring tools conduct periodic checks to gather device status and performance metrics. The device's status is updated only when a check is initiated by the monitoring system in the defined time interval. Any fault that happens in between polls is only captured when the next check is initiated.

REST has reigned for a long time in the world of web services. It’s easy to implement, allows standardization through RESTful patterns and has lots of libraries that support and facilitate its development. Then came GraphQL, the famous query language for APIs.