This year's DevOpsDays Tel Aviv (co-located with Cloud Native & OSS Tel Aviv and Statscraft, will be a two-day, TWO TRACK event - with the main stage being the DevOpsDays track, and the additional track being dedicated to either Cloud Native + OSS and Statscraft on each day.

This year's DevOpsDays Tel Aviv will have a primary theme of engineering horror stories, in the spirit of Halloween. 

To this end we would like to receive talk submissions that focus on the following categories:

• Production Impairment - Cases in which the end result was downtime or an impairment of the system, with focus on the ingredients that caused the issue and how the issue was resolved.
• Costly Mistakes - Cases in which the end result was an unexpected or extreme cloud cost, with a focus on what caused the rise in costs, and what was done in response to try and lower costs.
• Technical Debt - Cases where short/mid-term decisions were made, with focus on what were the long-term consequences on the system’s architecture and on the company’s culture.
• Near Miss - Cases where the system could have been impaired, but was saved at the last minute by the last piece of dangling dry duct tape, and what was that duct tape.

While the central theme of the conference will be Horror Stories, we know that some people have their own compelling non-spooky stories to tell too. As long as your session is related to DevOps, Cloud Native, OSS, and/or monitoring and observability, feel free to submit an interesting session on any relevant topic.

What you should think about before you submit.

Ask yourself questions like:

• Why this talk? What makes it a must see for those attending the audience?
• Is this talk related to the subjects the conference covers?
  
• Have I proofread the content and done a grammatical review?
  
• Does this content already exist online? (DevOpsDays makes an effort to bring new content to its audience).
• Does this talk focus on a specific tool? We are of the opinion that the tooling changes and implementation details evolve. Therefore, the higher order the concept of the talk, the better.  (Demos with a specific stack are welcome - however, specific tooling talks will likely be passed over, unless for an ignite session, which they are more relevant for).
• Is the topic of the talk directly related to a product or service my company offers? (Hint: If you answered yes, it probably is not the right fit.)

~/ talk language

For inclusivity purposes, as we often times have attendees from all over the globe, DevOpsDays Tel Aviv talks are expected to be delivered in English.

~/ talk formats

This year’s talk formats include:

SHORT & LONG SESSIONS. 25-Minute sessions in tracks or 40-Minute deep dives (reserved for 4 sessions total - one per track per day) 

IGNITES. A 5-Minute fast-paced talk with (up to) 20 slides (There's the traditional ignite with auto-advancing slides, and the lighter, freestyle ignite - let us know which you are willing to do).

~/ talk level

In an effort to be able to provide attendees with a better classification of talks, we are requesting both a Track categorization and proficiency - so folks can choose sessions to attend based on their knowledge and level.

~ / suggested topics

DEVOPSDAYS TEL AVIV covers the intersection between development and operations, with a focus on the culture, core technologies, systems, protocols & principles that are the backbone of scalable, resilient, robust, and secure systems. In this year’s horror stories theme the focus would be on cases where the issues and solutions were derived from the culture, architecture & principles of DevOps.

CLOUD NATIVE DAY TEL AVIV is the mirror image of DevOpsDays Tel Aviv, where the focus is indeed on modern cloud native tool chains, open source projects that power the cloud native world, serverless, containers, networking, service mesh and more. In this year’s horror stories theme the focus would be on cases where the issues and solutions were derived from adoption of new technologies and tools.

STATSCRAFT is focused on helping engineers understand how to make monitoring easier for humans with content that dives into the tools & methods, insights on how to derive more from your data, and ensuring systems are built to empower and enable the humans behind them to have a good quality of life. In this year’s horror stories theme the focus would be on cases where monitoring masked issues, and how monitoring was used to uncover those masked issues.

~/ guidelines - The Finer Print

Like every year we are looking to include:

• Diversity: We embrace diversity and encourage proposals from people in underrepresented parts of our community
  
• Original content: content not yet presented at other conferences, or a new angle to an existing problem
• New presenters: people who are new to the space and have insightful stuff to say; we want to hear everybody’s voice
• No vendor pitches: we value vendors and sponsors, but vendor promotional talks won’t be accepted.