Skip to content

Service List

Add a 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. Select the color for this service; it is randomly generated by default, but you can also choose from the dropdown list.

  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 input a new team name and press Enter to create a new one;
    • Contact Information: This will be contacted first if there are any abnormal issues with the current service; supports email, phone, and Slack in three channels; if multiple selections are needed, they must be separated by commas, semicolons, or spaces.

    Note: After successfully creating the service list, the newly created team here will also be synchronized in the Management > Member Management > Team Management list.

  5. Configure related information

    • Application: The application information associated with the current service; same as the User Access Monitoring (RUM) application ID;
    • Tags: Used to associate other configuration information within the current workspace, connecting workspace information via global tags, supporting jump operations for analysis and review.
  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, and after selection, you can view the bound built-in views under the Analysis Dashboard for linked data viewing.
  7. Click Confirm.

View Services

After creation, you can view relevant parameters of the services 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 through frequently viewed, my favorites, and my creations;

    • On the left side of the list, filter accordingly based on creation type, team, and service type.

  3. On the list page:

    • Application: If the application matches the RUM application ID, it supports opening a new page to jump to the Session Explorer upon Hover-click;

    • Team: Supports opening a new page upon Hover-click to view team information;

    • Contact Information: Supports Hovering over to view detailed information about email, phone, and Slack; among these, Slack supports jumping;

    • Repository Configuration & Documentation: Hover over the corresponding icon and click to automatically jump to the associated repository or documentation.

  4. In Actions:

    • Hover over the avatar icon to view the creator, creation time, updater, and update time of this service;

    • Click the button to modify or delete the current service.

  5. Click the button to favorite 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 snapshot is a complete record capturing the state of JVM memory at a specific point in time. You can use the log information in the snapshot to view detailed information about the memory usage of the related application, promptly troubleshoot issues such as memory leaks and performance problems, and further optimize data structures based on understanding memory usage.

For more configurations on the collector side, refer to Collection.

Start Creating

  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 as needed;
  5. Click Confirm.
How is the execution target determined?

Guance queries the tracing data from the past hour and determines whether PODs exist in the tracing data of the current service. If there is a pod_name value, the dropdown lists pod_name; otherwise, it lists host.

Historical Memory Snapshots

All created snapshots can be accessed through the Historical Memory Snapshots entry above the list.

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

Feedback

Is this page helpful? ×