Why is a 72-hour rolling history used for the Problems dashboard in Dynatrace?

The use of a 72-hour rolling history for the Problems dashboard in Dynatrace primarily allows DevOps teams sufficient time to analyze issues effectively. In the fast-paced environment of IT operations, incidents may arise and need to be addressed promptly. A 72-hour window ensures that relevant data is available for teams to review and investigate problems as they occur or shortly after, without having to sift through older data that may no longer be pertinent.

Additionally, this timeframe strikes a balance between providing a comprehensive view of recent issues while not overwhelming teams with outdated information. By focusing on the last 72 hours, it increases the likelihood that teams can trace problems back to their source, understand the impact, and implement timely fixes.

While the other options highlight interesting aspects of data management or operational efficiency, they do not capture the core purpose of the 72-hour rolling history in the context of problem resolution and team collaboration.