This page describes the support channels for Realtime Compute for Apache Flink and the scope of what technical support covers.
Contact support
Choose the channel that matches your need:
| Channel | Best for |
|---|---|
| Submit a ticket | Product issues, defects, and technical questions — the primary support channel |
| Join the DingTalk group | Peer discussion and general communication |
| Document feedback | Suggestions on documentation content |
Submit a ticket
RAM users cannot submit tickets by default. An Alibaba Cloud account holder must attach the AliyunSupportFullAccess policy to the RAM user before the RAM user can submit tickets. For instructions, see Use RAM to manage the permissions of O&M engineers.
Go to the New Ticket page.
Click View all products in the Product Catalog drop-down list and choose Big Data Computing > Realtime Compute for Apache Flink.
Enter the required information on the New Ticket page.
Click Submit.
Join the DingTalk group
Scan the QR code below to join the Realtime Compute for Apache Flink DingTalk group for peer discussion.
The DingTalk group is for communication only. For product issues and technical questions, submit a ticket.
Document feedback
To suggest improvements to a documentation topic, click Feedback in the lower-right corner of the page.
Scope of support
What's covered
Console operations: Purchasing, creating, and scaling workspaces, and creating and managing namespaces.
Product consulting: Questions about Realtime Compute for Apache Flink features, product defects, and cluster stability issues.
Associated Alibaba Cloud services: Help coordinating issues with services that integrate with Realtime Compute for Apache Flink — such as Object Storage Service (OSS) and Application Real-Time Monitoring Service (ARMS). The service teams of those products handle the resolution.
What's not covered
Custom code: Writing SQL, DataStream, or Python deployments; building custom user-defined functions (UDFs), custom formats, or custom connectors; troubleshooting data correctness; handling performance issues; or assisting with business migration.
Unsupported features: Issues related to features or connectors not provided by Realtime Compute for Apache Flink.
Third-party components: Issues in upstream or downstream storage systems, such as message queues, databases, or data lakes.
Cluster issues caused by unexpected operations: Cluster instability or unavailability resulting from operations outside the documented guidelines. For details, see Limits.
SLA
For the service level agreement (SLA) applicable to your support plan, see Service level comparison.Service Level Comparison