Remember when you raised a service request and received a delayed solution? The response was so late that you switched to looking for another possible solution. Such delays impact the organization’s overall progress, and we are sure you don’t want to encounter them frequently. This is where Service Level Agreement (SLA) comes to shield organizations from such irregularities.
One of the things we love about working in the cloud is the ease and scalability it brings to application development. It enables us to build out applications, APIs and any infrastructure that is needed from prototyping an idea, through to self scaling deployments. Monitoring and troubleshooting production-level serverless applications is always tricky, Especially working across a number of services and the many logs they can produce.
Configuring applications, services, and environments by modifying plain text files is a standard part of modern software development. Configuration as Code (CaC) takes this one step further by systematically generating, storing, and managing configuration files. CaC allows development teams to automate config management for their applications and environments while ensuring consistency and traceability throughout the development life cycle.
When building serverless applications on AWS Lambda, Amazon CloudWatch provides out-of-the-box metrics that measure the performance, errors, and duration of your functions. Although these standard Lambda metrics provide visibility into your serverless applications, it can also be invaluable to monitor custom metrics that are unique to your use case and application.
Apache Kafka provides an unified, high-throughput, low-latency platform for handling real-time data feeds. Installing Apache Kafka, especially the right configuration of Kafka Security including authentication and encryption is kind of a challenge. This should give a brief summary about our experience and lessons learned when trying to install and configure Apache Kafka, the right way.
Last week we released the final first version of Icinga DB and its web interface module Icinga DB Web. Icinga DB Web offers many new features and a completely new design. The monitoring module has its limitations when managing a role, as it handles permissions and restrictions separately. This means that the permissions for a role are not related to the restrictions of the role To understand this better, here is an example.
We’ve all grown used to logs, metrics and traces serving as the “three pillars of observability.” And indeed they are very important telemetry signals. But are they indeed the sum of the observability game? Not at all. In fact, one of the key trends in observability is moving beyond the ‘three pillars: One emerging telemetry type shows a particularly interesting potential for observability: Continuous Profiling.
With more than 7,000 customers and double the number of employees ServiceNow had four years ago, our digital technology (formerly IT) operations team faced increased demand for compute, storage, and bandwidth. At the same time, we had to maintain tight security controls. We embrace a three-zero strategy: zero unplanned outages, zero physical footprint, and zero user-reported incidents.
