On the ARC screen, we have the ability to access the log view and read the log entries related to the exception that was thrown. We access this by clicking on the Log tab while in the ARC screen.
There may be times we run into an error message when accessing this Log section which may prevent us from reading the logs.
In this article, we will review the different error messages that may be displayed when accessing the Log section in the ARC screen.
| ## Error Message | ## Reasoning |
|---|---|
| This snapshot was recorded before log views were introduced. Please try viewing a more recent snapshot. | This hit was received by the backend before the log entry was introduced. |
| Log views were introduced in version 3.22.0. Please upgrade your installation. Upgrade now | The daemon that fired the hit does not support the running version of OverOps running. |
| Log views were introduced in version 3.22.0. Please upgrade your installation. Upgrade now | The agent that fired the hit does not support the running version of OverOps. |
| For on-prem users: No log messages have been recorded for this snapshot. For SaaS/hybrid users: No log messages were logged within the thread of the error. If messages were logged and not captured - Find an Answer in OverOps Community | The agent supports the running version of OverOps, but no messages have been recorded. |
| Log messages were not recorded due to a storage server error at the time of this snapshot. Please check storage server connectivity and status. | An error occurred while storing the data (occurs mostly in hybrid mode). |
| Log messages were not recorded for this snapshot due to memory overhead constraints. | Garbage Collection removed all records. |
| No supported logging framework has been detected. Check out our documentation for a list of supported frameworks. | No logging framework was provided. |
| Oops, something went wrong…An error occurred while recording log messages for this snapshot. Please try viewing a different snapshot. | Some other error occurred while collecting or building the data. |
| No messages were logged during this transaction. This might also occur during new event initialization. In this case, log messages will be captured starting from next snapshot. | No context was present when the hit was recorded. |
| Log view has been disabled or not supported | Logging framework is actively not supported |