Remove 2019 Remove Infrastructure Remove Java Remove Traffic
article thumbnail

Building Netflix’s Distributed Tracing Infrastructure

The Netflix TechBlog

Now let’s look at how we designed the tracing infrastructure that powers Edgar. This insight led us to build Edgar: a distributed tracing infrastructure and user experience. Our tactical approach was to use Netflix-specific libraries for collecting traces from Java-based streaming services until open source tracer libraries matured.

article thumbnail

OneAgent for Linux on IBM Z (General Availability)

Dynatrace

Having released this functionality in an Early Adopter Release with OneAgent version 1.173 and Dynatrace version 1.174 back in August 2019, we’re now happy to announce the General Availability of OneAgent full-stack monitoring for Linux on the IBM Z platform, sometimes informally referred to as Z/Linux. Dynatrace news.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

OneAgent for Linux on IBM Z now available in Early Adopter Release

Dynatrace

At Dynatrace, where we provide a software intelligence platform for hybrid environments (from infrastructure to cloud) we see a growing need to measure how mainframe architecture and the services running on it contribute to the overall performance and availability of applications. Full-stack and cloud-infrastructure monitoring modes.

article thumbnail

Achieving observability in async workflows

The Netflix TechBlog

Prodicle Distribution Our service is required to be elastic and handle bursty traffic. In late 2019, our team started integrating it with the rest of the ecosystem by writing a thin Java Domain graph service (DGS) to wrap the asynchronous watermarking functionality that was then in Ruby on Rails. Things got hairy.

Traffic 160
article thumbnail

The Show Must Go On: Securing Netflix Studios At Scale

The Netflix TechBlog

Adding to the complexity, many of the checklist items themselves had a variety of different options to fulfill them (“new apps do this , but legacy apps do that”; “Java apps should use this approach , but Ruby apps should try one of these four things”… yes, there were flowcharts inside checklists.

Internet 220
article thumbnail

DBLog: A Generic Change-Data-Capture Framework

The Netflix TechBlog

Nonetheless, we found a number of limitations that could not satisfy our requirements e.g. stalling the processing of log events until a dump is complete, missing ability to trigger dumps on demand, or implementations that block write traffic by using table locks. Blocking write traffic by locking tables. Writing events to any output.

Database 197
article thumbnail

DBLog: A Generic Change-Data-Capture Framework

The Netflix TechBlog

Nonetheless, we found a number of limitations that could not satisfy our requirements e.g. stalling the processing of log events until a dump is complete, missing ability to trigger dumps on demand, or implementations that block write traffic by using table locks. Blocking write traffic by locking tables. Writing events to any output.

Database 212