Monitor applications¶
Consistently monitoring applications allows you to proactively detect issues, troubleshoot performance bottlenecks, and quickly respond to service disruptions, minimizing downtime and improving the overall user experience. To access monitoring information, go to the Applications page and click on the app you want to view.
From here, you can access the following monitoring options:
- Service health: Provides a dashboard that displays memory, CPU, and network usage.
- Activity log: Allows you to view access, runtime, build, and version history logs.
Resource usage¶
Permissions to view service health
Only users with Owner permissions for the application and DataRobot administrators can access service health.
The Service health tab allows you to monitor usage, service health, and resource consumption for individual applications. Monitoring resource consumption is essential for cost management to ensure that resources are used efficiently, helping optimize cost.
To access application monitoring capabilities, on the Applications page, click the app you want to view and select Service health. From here, you can:
| Element | Description | |
|---|---|---|
| 1 | Range/Resolution | Adjusts the range and resolution of the chart. The options in the Resolution dropdown are based on your Range selection. |
| 2 | Refresh | Instantly refreshes usage information—usage information automatically updates every minute. |
| 3 | Resource usage | Displays average CPU, memory, and network usage for the specified range, as well as live usage values. Click on a tile to visualize usage information in the chart below. |
| 4 | Usage chart | Visualizes usage information over time for the selected usage tile and specified range. For CPU usage, you can also display a line representing the average usage. |
Activity logs¶
Permissions to view logs
Access to logs for an application requires Owner or Editor permissions for the application. Owners can view all logs, while Editors can only view build and runtime logs, not access logs.
DataRobot records the following activity logs for custom applications:
| Activity log | Description |
|---|---|
| Access logs | Displays which users have accessed the application and when. |
| Runtime logs | Displays a real-time record of the application's tasks during execution. |
| Build logs | Displays a history of the application's deployment process. |
| Version history logs | Displays a time-stamped, chronological record of the application's versions. |
To access these activity logs, from the Applications page, click the app you want to view, and select Activity log.
Build and runtime logs¶
From the Build logs and Runtime logs tabs, you can browse logs that detail the history of compiling, building, and executing the custom application. This includes dependency checks, packaging, and any warnings or errors thrown.
Access logs¶
From the Access logs tab, you can monitor the history of users who have opened or operated a custom application.
You can also view access logs directly from an application source. Navigate to Registry > Application sources, locate the application source for your custom application, and expand the dropdown to view the applications built from the source. Then, click the custom application you want to view the access logs from to access a detailed view.
On the Overview tab, scroll down to the Access logs section.
The access logs detail users' visits to the application, including their email, user ID, time of visit, and their role for the application.
Usage logging interval
In addition to the initial access event, every 24 hours of continuous access or use is recorded as an individual visit to the application. For example, when a user opens an application, an access event is logged, then, when that user session exceeds 24 hours of continuous access or use, another access event is logged. This results in two access events logged during a 24-hour and 1-minute custom application visit. In Self-Managed AI Platform environments, this interval is configurable through the CUSTOM_APP_USAGE_METRIC_PUBLISH_MAX_FREQ in the application configuration.