DongTai
DongTai copied to clipboard
[Feature]: Manually bind the project name to match the agent
Preflight Checklist
- [X] I agree to follow the Code of Conduct that this project adheres to.
- [X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
Problem Description
1.When there are many application services and it is not easy to bind the project name when starting the agent one by one.
2.When manually binding the agent, there may be many agents, or the agent names are the same, and the relationship between the agent and the project name cannot be directly distinguished .
3.However, the engine management office can obtain the value of the service address. Generally, project deployment will have a list of service addresses, and different services correspond to different service addresses.
Proposed Solution
4.In the manual binding place, you can now select the agent to bind, but as mentioned above, it is difficult for the agent to distinguish the correspondence between items. In the manual binding form or the corresponding item adding interface, add a field for the service address. This field You can select the service address of the online agent that is not bound, or manually add the service address in the project add interface, so that the corresponding relationship between the agent and the project name can be well matched and managed .
Alternatives Considered
No response
Additional Information
No response
Or add a configuration switch in the system configuration module to set the agent name definition, the option is to use the service address naming for the agent name
Or add a configuration switch in the system configuration module to set the agent name definition, the option is to use the service address naming for the agent name
Thanks for the suggestion, a discussion will be arranged to discuss whether this feature needs to be added. Please waiting for notification.