Service List¶

Add Service¶

1. Define the specific name of the service.

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

3. Choose the color for the current service; defaults to a randomly generated color, but can also be selected from a dropdown.

4. Configure team information

   • Team: The team to which the current service belongs; you can choose an existing team within the current workspace or manually enter a new team name and press Enter to create a new team.
   • Contact Information: This will be contacted first when the current service encounters an issue; supports email, phone, and Slack channels; multiple entries should be separated by commas, semicolons, or spaces.

   Note: After successfully creating the service list, any new teams created here will be synchronized in the Manage > Member Management > Team Management list.

5. Configure associated information

   • Application: Information related to the application associated with the current service; this is the same as the RUM Application ID.
   • Tags: Used to associate other configuration information within the current workspace, linking workspace information through global tags, supporting operations such as jumping to view and analyze.

6. Configure help links

   • Repository Configuration: Enter the display name, provider name, and repository code URL sequentially.
   • Help Documentation: Enter the display name, provider name, and other related document URLs sequentially.
   • View: You can bind required built-in views to the current service. Once selected, you can view the bound built-in views under the Analysis Dashboard for the current service.

7. Click Confirm.

View Service¶

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

Manage List¶

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

1. Search: In the search bar, you can input keywords to search for service names.

2. Filter:

   • In the entire list, quickly filter and find corresponding services by frequently browsed, my favorites, and my created services.
   • On the left side of the list, filter based on creation type, team, and service type.

3. On the list page:

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

4. In Operations:

   • Hover over 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.

5. Click the button to bookmark the current service.

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

7. 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 snapshots are complete records capturing the state of JVM memory at a specific point in time. You can use the log information within the snapshot to view detailed information about the memory usage of the associated application, promptly identify issues such as memory leaks and performance problems, and further optimize data structures based on understanding memory usage.

For more collector-side configurations, refer to Collection.

Start Creation¶

1. Input 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 if needed;
5. Click Confirm.

Historical Memory Snapshots¶

All created snapshots can be viewed by clicking the Historical Memory Snapshots entry above the list.

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