Introduction

Within the ARC screen, you can get all the information you need to understand and fix an error - including the state, stack, and source code that led to it. In addition, OverOps also displays an environment (Env) view for each event and exception, including the internal state of the environment at the moment of event, which facilitates the work with OverOps' code (“classic”), log and environment data - without leaving the application.

#Opening the Env View
The main way to reach the Env view is by clicking the Env tab, located in the error header.

Clicking this tab takes you from code view to the Env view, and back.

Env View Basics

The Env view contains the internal state of the environment at the moment of the event.

In the Env view the OverOps Micro-Agent captures the state of the environment at the moment of the event, including:

• Memory usage (both heap and non-heap)
• Basic system information
• CPU usage
• Process information
• JIT compilation stats
• Class loading stats
• Thread information

📘

Features and Functionalities

All the advanced features and functionalities that are available in the ARC screen are also available in the Env view - such as handling the event (archiving, resolving, labeling), sharing it (via Jira or OverOps' notes) and searching within it.

Related Articles

Automated Root Cause (ARC) Screen
Opening the ARC Analysis Screen