Esta página aún no está disponible en su idioma local. Estamos trabajando arduamente para agregar más versiones de idiomas. Gracias por tu apoyo.
Distributed Message Service for RocketMQ
Distributed Message Service for RocketMQ
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of Using RocketMQ
- Creating a User and Granting DMS for RocketMQ Permissions
- Buying a RocketMQ Instance
- Configuring a Topic
- Accessing an Instance
- Managing Messages
- Managing Consumer Groups
-
Managing Instances
- Viewing and Modifying Basic Information of a RocketMQ Instance
- Viewing Background Tasks of a RocketMQ Instance
- Configuring Tags for a RocketMQ Instance
- Exporting RocketMQ Instances
- Diagnosing a RocketMQ Instance
- Restarting Brokers of a RocketMQ Instance
- Deleting a RocketMQ Instance
- Configuring SSL of a RocketMQ Instance
- Modifying RocketMQ Specifications
- Migrating Metadata
- Viewing Monitoring Metrics and Configuring Alarms
- Viewing RocketMQ Audit Logs
- Best Practices
- Developer Guide
- API Reference
- SDK Reference
- FAQs
- Videos
On this page
Show all
Help Center/
Distributed Message Service for RocketMQ/
User Guide/
Managing Instances/
Exporting RocketMQ Instances
Exporting RocketMQ Instances
Updated on 2024-12-25 GMT+08:00
You can export a list of instances on the RocketMQ console.
Prerequisite
A RocketMQ instance has been purchased.
Procedure
- Log in to the console.
- Click
in the upper left corner to select a region.
NOTE:
Select the region where your RocketMQ instance is located.
- Click
and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
- Export the instance list in either of the following ways:
- Select the desired instances and choose Export > Export selected data to an XLSX file to export specified instances.
- Choose Export > Export all data to an XLSX file to export all instances.
Parent topic: Managing Instances
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.