Manage applications¶
The Applications page in the Registry lists all custom applications available to you from the All applications tab. The table below describes the elements and available actions from this page:
| Element | Description | |
|---|---|---|
| 1 | Application name | The application name. |
| 2 | Version | Lists the version number of the application or source. |
| 3 | Open | Click to open an application or source. |
| 4 | Actions menu | Shares, controls, or deletes an application. |
| 5 | Search | Use to find a specific application in the list. |
| 6 | Application tabs | Choose to view built applications or application sources. |
| 7 | Add dropdown | Use the Add dropdown to upload a custom app or create a new application source. |
Share applications¶
The sharing capability allows you to manage permissions and share an application with users, groups, and organizations, as well as recipients outside of DataRobot. This is useful, for example, for allowing others to use your application without requiring them to have the expertise to create one.
Warning
When multiple users have access to the same application, it's possible that each user can see, edit, and overwrite changes or predictions made by another user, as well as view their uploaded datasets. This behavior depends on the nature of the custom application.
To access sharing functionality in the All applications tab, click the Actions menu next to the app you want to share and select Share ().
This opens the Share dialog, which lists each associated user and their role. Editors can share an application with one or more users or groups, or the entire organization. Additionally, you can share an application externally with a sharing link.
-
To add a new user, enter their username in the Share with field.
-
Choose their role from the dropdown.
-
Select Send notification to send an email notification and Add note to add additional details to the notification.
-
Click Share.
-
Select either the Groups or Organizations tab in the Share dialog.
-
Enter the group or organization name in the Share with field.
- Determine the role for permissions.
- Click Share. The app is shared with—and the role is applied to—every member of the designated group or organization.
To share a custom app with non-DataRobot users, toggle on Enable external sharing. The link that appears beneath the toggle allows you to share custom with end-users who don't have access to DataRobot. Before you can share that link with end users, you must specify the email domains and addresses that are permitted access to the app. Email invitations expire one hour after they are sent to a user. After a user accepts authentication, the authentication token created expires after 14 days. You can revoke access to a sharing link by modifying this list. Remove the domains or addresses that you no longer want to have access to the app.
Self-managed external sharing
For self-managed users externally sharing an application, note that you need to configure a Simple Mail Transfer Protocol (SMTP) server in order to share the application with external users.
You can also programmatically share custom applications using the DRApps CLI.
The following actions are also available in the Share dialog:
- To remove a user, click the X button to the right of their role.
-
To re-assign a user's role, click the assigned role and assign a new one from the dropdown.
Link to a Use Case¶
To link a custom application to a Workbench Use Case, in the application's actions menu , click Link to Use Cases:
In the Link to Use Case modal, select one of the following options:
| Option | Description |
|---|---|
| Select Use Case | Click the Use Case name dropdown list to select an existing Use Case, then click Link to Use Case. |
| Create Use Case | Enter a new Use Case name and an optional Description, then click Create Use Case to create a new Use Case in Workbench. |
| Managed linked Use Cases | Click the minus icon next to a Use Case to unlink it from the asset, then click Unlink selected. |
Delete an application¶
If you have the appropriate permissions, you can delete an application by opening the Actions menu and clicking Delete ().
Application logs¶
DataRobot records two types of logs for custom applications: build and runtime logs and access logs. Through these logs, you can monitor an application's build and runtime tasks and review the user access history for an application.
Permissions to view logs
Access to logs for an application require Owner or Editor permissions for the custom application. Owners can view all logs, while Editors can only view build and runtime logs, not access logs.
Build and runtime logs¶
You can browse logs that detail the history of build and runtime tasks for a custom application. From the Applications page, open the actions menu for the app you want to view logs for, and click View logs.
The logs modal details the history of compiling, building, and executing the custom application. This includes dependency checks, packaging, and any warnings or errors thrown.
Access logs¶
Browse access logs to monitor the history of users who have opened or operated a custom application. To view access logs, navigate to the Applications page, open the actions menu for the app you want to view logs for, and click View access logs.
You can also view access logs directly from an application source. Navigate to the Application sources page, locate the application source for your custom application, and expand the dropdown to view the applications built from the source. Then you can click the custom application for which you want to view the access logs to access a detailed view.
From the detailed view for a custom application, 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.