apolloconfig/apollo

如何在 「管理员工具」-> 「系统信息」查看部署到多机房（集群）的 Config/Admin Service？

Open

#3638 opened on Apr 16, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (29,769 stars) (10,177 forks)batch import
area/metaserverarea/portalfeature requesthelp wanted

Description

你的特性请求和某个问题有关吗？请描述

这个问题和 apollo.portal.meta.servers 相关，如果某环境部署了多个集群，这个配置应该怎么写，「管理员工具」-> 「系统信息」就可以展示多个集群的 Config/Admin Service？

比如有 local, dev, st, pro, ali-pro 等 5 个环境，配置如下：

{
    "local":"http://localhost:8080,",
    "dev":"http://meta-server.dev.s.example.com:8080",
    "st":"http://meta-server.st.s.example.com:8080",
    "pro":"http://meta-server.pro.s.example.com",
    "ali-pro":"http://apollo-aliyun.pro.s.example.com"
}

「管理员工具」-> 「系统信息」只能看到 default 集群的 Config/Admin Service。除了数据库里的 ApolloConfigDB.ServerConfig 的 Cluster 字段能看出来该环境部署了几个集群，Apollo Portal 的 Web 页面似乎没有什么集群相关的信息，也看不到集群下的 Config/Admin Service。

清晰简洁地描述一下你希望的解决方案 如果部署了多集群，希望可以通过所有集群的 Meat Server 展示所有集群的 Config/Admin Service。

清晰简洁地描述一下这个特性的备选方案 暂无

其它背景

3.2.1 eureka.service.url - Eureka服务Url 的 注3 。

Contributor guide

Tech stack
javaspring
Domain
full stack
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Apollo's multiple clustersJava developmentSpring Boot
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Start by examining the Portal's system info page implementation, likely in the `portal` module. Look for how `apollo.portal.meta.servers` is parsed and how the current cluster info is displayed. Consider modifying the backend to aggregate data from multiple clusters and updating the frontend to display them. The `ApolloConfigDB.ServerConfig` table can be referenced to identify all clusters. Refer to the linked documentation for context.