More configuration possibilities for the Agent Mapping

Description

I stumbled over the issue that I had two environment mappings for an Agent. This happens easily if you create a new environment, add a new agent mapping definition and leave the Default Mapping as it is.

e.g.

Active

Agent Name

IP Address

Environment

true

*

*

Default Environment

true

MyAgent*

*

My Environment

This is kind of confusing at the beginning and you will realize it first after an agent start.
I would like if we could think about how we could avoid this small pitfall and how we could avoid the "More Than One Environment For Agent Found exception".

e.g.

  • define which profile will always be used if too many match

  • define an ordering of profile

  • use the most matching profile

  • tell the user that the default mapping needs to be adjusted if a second one is created

  • ...

Environment

None

Status

Assignee

Tobias Angerstein

Reporter

Matthias Huber

Labels

None

Pull Request

None

Integrator

Ivan Senic

Sprint

None

Fix versions

Priority

Medium
Configure