Skip to content
Carolina Code Conference
Served by C++ (cpp-httplib) in 16ms

2026 speaker

Yamank Vashishtha

Yamank Vashishtha

Michelin NA Lead Software Engineer

Yamank Vashishtha is a Lead Software Engineer at Michelin North America with more than 18 years of experience delivering and modernizing mission-critical enterprise systems on IBM Mainframe platforms. His expertise spans COBOL, CICS, DB2, IMS, IDMS, batch processing, and large-scale business integrations that power core operational workloads. Throughout his career, he has led modernization, migration, and automation initiatives that enhance system reliability, scalability, and operational efficiency.

Yamank is passionate about transforming traditional operations into proactive, data-driven ecosystems through observability and intelligent automation. Leveraging deep mainframe expertise, he has developed solutions that improve visibility into batch operations, automate file freshness validation, strengthen SLA monitoring, and accelerate incident detection and resolution. His work demonstrates how mainframes continue to serve as a strategic foundation for innovation, resilience, and business continuity in modern enterprises.

A recognized advocate for operational excellence, he focuses on bridging legacy platforms with modern engineering practices to deliver measurable business value. Through his conference presentations, Yamank shares practical strategies for building proactive operational frameworks that reduce risk, improve customer outcomes, and maximize the value of mission-critical systems.

2026 · intermediate

Proactive Batch Observability: Automate File Freshness and SLA Monitoring

Modern observability focuses on APIs and microservices, yet many business-critical workflows still depend on batch jobs and file-based data pipelines. When these systems fail, they often do so silently only becoming visible after business impact.

This talk introduces a practical, tool-agnostic approach to batch observability by applying Site Reliability Engineering (SRE) principles. The core idea is simple but powerful:

In batch systems, data freshness is the equivalent of latency in real-time systems.

If data is late or missing, the system is effectively down from a business perspective.

Attendees will learn how to model batch workflows using event-driven observability, define expected vs. actual delivery SLAs, and measure reliability using a good event vs. total event SLI approach. These signals can then be translated into meaningful SLOs aligned with business outcomes.

The session also includes a brief real-world walkthrough demonstrating how these principles can be implemented to track end-to-end workflows, detect delays proactively, and provide a single, business-aligned view of reliability.

Why Attend

If your systems rely on batch jobs, scheduled workflows, or file transfers, this talk will help you:

  • Make batch systems observable and measurable
  • Detect issues before business impact occurs
  • Move beyond job-level monitoring to true reliability measurement
  • Apply SLI/SLO thinking to non-real-time systems

Key Takeaways

  • Model data freshness as a reliability signal (SLI)
  • Define and enforce SLAs based on data delivery
  • Connect technical signals to business impact
  • Apply a tool-agnostic framework across any observability stack

From the talk