tencent cloud

フィードバック

Value-Added Features (Saving Application Logs ‍and Archives)

最終更新日:2024-04-17 10:37:45
    To ensure data security and application stability, the CAR concurrency ‍automatically ‍cleans, ‍resets, and reloads the application after the user disconnects. This is done to ensure that the next user who connects will not access the data of the previous user. Therefore, if no value-added features are configured, the user's operation logs, usage progress, and other files of the cloud application will not be saved.
    To query the log files of a cloud application, you can configure the Application Log Saving feature.
    To save the user's application usage so they can continue next time they reconnect, you can configure the Application Archive Saving feature ‍(in beta test).
    
    
    
    Note:
    Activate COS before using value-added features.
    When you use ‌‍value-added ‌‍features, ‌‍possible charges ‌‍will ‌‍be ‌‍incurred ‌‍by COS ‌‍instead ‌‍of CAR. For more information, see ‌‍COS Billing Overview.

    Saving Application Logs

    With ‍this ‍feature, ‍a ‍specified folder ‍(such as ‍the Log folder) will be automatically uploaded to the COS bucket after a user disconnects from the application. The basic logic ‍is ‍as follows:
    1. In the console, configure the relative path of the folder that needs to be uploaded. Example: WindowsNoEditor\\saved.
    Note:
    Only folder paths in the application package are supported. To use a path outside the application package, such as the system disk path, contact Tencent Cloud's architect or your sales rep for assistance.
    If you upgrade the application, ensure that the file paths used in ‍‍‍the ‍old ‍and ‍new ‍applications ‍are ‍the ‍same; otherwise, the system will be unable to locate the specified file, and the feature will no longer work.
    2. When a user connects to the application, it should write log files to the application package directory and saves them locally on the concurrent instance.
    3. After ‍the user ‍exits the application, the system will automatically search for the specified file based on the path configured in the console and upload it to the COS bucket.
    
    
    

    Saving Application Archives ‍(in Beta Test)

    With ‍this ‍feature, a user's application usage will be archived and can be resumed the next time the user connects to the application. The basic logic ‍is ‍as follows:
    1. In the console, ‍configure the relative path of the archive folder. Example: WindowsNoEditor\\UserArchive.
    Note:
    This feature is in beta test. To try it out, please contact your Tencent Cloud architect or sales rep.
    Only folder paths in the application package are supported. To use a path outside the application package, such as the system disk path, contact us for assistance.
    If you upgrade the application, ensure that the file paths used in ‍‍‍the ‍old ‍and ‍new ‍applications ‍are ‍the ‍same; otherwise, the system will be unable to locate the specified file, and the feature will no longer work.
    2. When a user connects to the application, the system will automatically read previous archives from the COS bucket based on the UserId.
    3. If the user has ‍any archives‍ ‍existing, then before the application starts, the archive folder ‍will be automatically downloaded to the relative path you configured in the console.
    4. The data of all the operations the user performs on the application will be archived locally on the concurrent instance.
    5. After ‍the user ‍exits the application, the system will automatically upload the archived data to the COS bucket.
    
    
    

    How ‍to ‍View ‍the S‍aved Logs ‍or Archives?

    Assume that you have an application with the ApplicationId "app-1234abcd"
    The user's UserId is "user123"
    The RequestId of the last session is ‍"01fdc815-c4e7-4642-819e-a011856dfd5a1"
    The timestamp of the last session is "1709284736"
    Then, the storage path in COS should be:
    Save Application Log: AppLogs/app-1234abcd/01fdc815-c4e7-4642-819e-a011856dfd5a1.zip
    Save Application Archive **(in beta test)**: userData/app-1234abcd/user123-1709284736-tx

    FAQs

    What are UserId and RequestId?

    UserId is the custom unique user identifier passed in to CAR, such as user123456. A RequestId, such as 01fdc815-c4e7-4642-819e-a011856dfd5a1, is returned when ‍CAR ‍requests a TencentCloud API.

    How do I view the RequestId?

    If you are using a test or quick launch link, ‍you can open the debug panel in the toolbar displayed on the application's main page (Ctrl+~) and view the RequestId information at the bottom.
    If you use Chrome DevTools, you can get the RequestId of CreateSession on the Network tab.
    If you have integrated to the CAR SDK, the returned values of the TencentCloud API include RequestId. We recommend you record it on the business backend.
    
    お問い合わせ

    カスタマーサービスをご提供できるため、ぜひお気軽にお問い合わせくださいませ。

    テクニカルサポート

    さらにサポートが必要な場合は、サポートチケットを送信して弊社サポートチームにお問い合わせください。24時間365日のサポートをご提供します。

    電話サポート(24 時間365日対応)