polaris
polaris copied to clipboard
Service Discovery and Governance Platform for Microservice and Distributed Architecture
**What is the feature you want to add?** ![image](https://user-images.githubusercontent.com/4991116/176341995-58e08070-e279-4712-9971-b91ffa6295aa.png) 如果上图所示,目前需要用户手动输入 * 才可以模糊搜索,但是页面上又没有任何提示,所以用户很难使用模糊搜索的能力。 是否可以默认就是模糊搜索,前端自动加 *? **Additional context** Add any other context or screenshots about the feature request here.
**Please provide issue(s) of this PR:** Fixes #422 **To help us figure out who should review this PR, please put an X in all the areas that this PR affects.**...
**Please provide issue(s) of this PR:** Fixes #453 - docker-compose-based development environment, contains `redis-sentinel`、`redis-cluster`、`mysql`、`prometheus`、`grafana`、`polaris-console`. - polaris-server support hot reload when code or config files changed. - append golang runtime metrics...
配置中心支持鉴权
**What is the feature you want to add?** 1. 针对配置中心的控制台接口、客户端接口分别鉴权 2. 前端需要参考开启鉴权后,服务信息编辑、修改页面涉及鉴权的功能需要迁移至配置模块 **Why do you want to add this feature?** **How to implement this feature?** **Additional context** Add any other...
请问北极星是否能单独使用动态路由、负载均衡、健康检查、熔断降级、访问限流功能?因为我们目前使用的 是 etcd ,再换 注册中心成本比较大,我只想使用北极星 动态路由、负载均衡、健康检查、熔断降级、访问限流功能,怎么能做到呢?还是配置中心也可以不用配置中心能使用这些功能吗?怎么接入呢
测试限流demo 但是监控显示灰色,没有数据,看了其他监控也是灰色,没有数据,安装的是集群版 ![image](https://user-images.githubusercontent.com/1912452/180395206-4035e4dc-2e89-4418-af60-ad44137b752e.png) promethues 和pushgateway 日志: ![image](https://user-images.githubusercontent.com/1912452/180394880-5dc762e5-29b1-41b0-bee4-ac6256537f83.png)
**What is the feature you want to add?** 配置分组(配置文件)的导入和导出 **Why do you want to add this feature?** 该功能非常实用,因为项目配置需要经常备份 和 多环境配置 **How to implement this feature?** 在配置文件显示处增加导出功能,可以将单个配置文件导入 根据文件尾椎确定具体格式 **Additional context** Add...
**What is the feature you want to add?** Mutual TLS or mTLS, as the name suggests, establishes a secure connection between the client and the server after they both validate...
一个场景: 1. 实例注册时带上 metadata `env: prod` 2. 然后在 console 将其改为 `env: test` 3. 实例心跳失败重新注册就会将其恢复为 `env: prod` 是否符合预期? console 修改的优先级是否要高于注册接口?