Operations | Monitoring | ITSM | DevOps | Cloud

Every day, organizations face external threats as a consequence of exposing their services over the internet. An estimated 2,200+ attacks occur in a 24-hour period—or one attack every 39 seconds. Add the fact that an average data breach (one of many potential consequences of poor security) costs companies $4.45 million, and the need for strong security is impossible to ignore. Web application and API security is key to protecting your infrastructure, data, and users.

Large-scale organizations typically collect and manage millions of logs a day from various services. Within these orgs, many different teams may set up processing pipelines to modify and enrich logs for security monitoring, compliance audits, and DevOps. Datadog Log Pipeline let you ingest logs from your entire stack, parse and enrich them with contextual information, add tags for usage attribution, generate metrics, and quickly identify log anomalies.

This is the second post in a 3-part series about shifting Observability left. If you have not had a chance to read the first, you can find it here. In today’s complex microservices deployments, gaining visibility into deployments is vital for optimal system performance and scalability. This has become even more important as the tech industry has moved toward microservice architecture reliance. Navigating through logs has become increasingly complex as requirements have grown.

Logging on embedded devices comes with a host of interesting and unique challenges that aren’t found on servers — devices are generally more memory, bandwidth, space, and CPU constrained, and devices often take weeks, months, or years to update, rather than days or hours.

Calico v3.27 is out 🎉 and there are a lot of new features, updates, and improvements that are packed into this release. Here is a breakdown of the most important changes.