Service List¶

Add Service¶

1. Define the specific name of the service.

2. Select the service type; the options include: app, framework, cache, message_queue, custom, db, web.

3. Select the color for the current service; it is randomly generated by default, or you can choose from the dropdown.

4. Configure team information

   • Team: The team to which the current service belongs; you can select an existing team in the current workspace, or manually enter a team name and press Enter to create a new team.
   • Contact: The first point of contact when an exception or failure occurs in the current service; supports email, phone, and Slack; if multiple options are needed, they must be separated by commas, semicolons, or spaces.
   Note

   After the current service list is successfully created, the new team created here will be synchronized in the Manage > Member Management > Team Management list.

5. Configure associated information

   • Application: The application information associated with the current service; same as the RUM application ID.
   • Tags: Used to associate other configuration information within the current workspace, linking information across the workspace through global tags, supporting actions like jumping to view and analyze.

6. Configure help links

   • Repository Configuration: Fill in the display name, provider name, and repository code URL in sequence.
   • Help Documentation: Fill in the display name, provider name, and other related document URLs in sequence.
   • Views: You can bind the required built-in views for the current service, and after selection, you can view the bound built-in views under the Analysis Dashboard for data viewing.

7. Confirm.

View Service¶

After creation, you can view the relevant parameter information of the service in the following three lists:

Manage List¶

You can refer to the following operations to manage the service list:

• Search: In the search bar, you can enter keywords to search for service names.

• Filter:

  • In the full list, you can quickly filter and find corresponding services by frequently viewed, my favorites, and my creations.
  • On the left side of the list, you can filter by creation type, team, and service type.

• In the list page:

  • Application: If the application filled in matches the RUM application ID, it supports Hover and click to open a new page and jump to the Session Explorer.
  • Team: Supports Hover and click to open a new page to view team information.
  • Contact: Supports Hover to view detailed information of email, phone, and Slack; Slack supports jumping.
  • Repository Configuration & Documentation: Hover to the corresponding icon, click to automatically jump to the associated repository or documentation.

• In Options:

  • Hover to the avatar icon to view the creator, creation time, updater, and update time of the service.
  • Click the button to modify or delete the current service.

• Click the button to favorite the current service.

• Click the button to export the current page data as a JSON file.

• You can save the current page data as a Snapshot.

Memory Snapshot¶

For Java services, you can configure JVM memory snapshots.

Concepts¶

JVM (Java Virtual Machine) memory snapshot is a complete record of the JVM memory state at a specific point in time. You can view detailed information about the memory usage of related applications through the log information in the snapshot, timely troubleshoot memory leaks, performance issues, and other exceptions, and further optimize data structures based on the understanding of memory usage.

For more collector-side configurations, refer to Collector.

Create¶

1. Enter the task name.
2. The system automatically fills in the current service for you.
3. Select the execution host or Pod.
4. Add a description as needed.
5. Click Confirm.

Historical Memory Snapshots¶

All created snapshots can be viewed through the Historical Memory Snapshots entry at the top of the list.

In the historical memory snapshot list, you can view the execution logs of the task and evaluate the execution results and logs.