You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Way:
Deleting all the config files in the config view filetree (the ocelot default config cannot be deleted, so this was the only directory left there).
With this method I could not reproduce the bug.
Way:
Deleting all the agent mappings in the agent mapping view. This resulted the agent not having any mapping at all and throw an error.
It sounds reasonable, that when there is no agent mapping, no agent mapping can be found, so I believe that this way is the intended way how things should work.
Way:
Deleting the working_directory folder in the inspectit-ocelot folder.
The working_directory got created again after restarting the config server and the agent could find the default mapping.
Also with this method I could not reproduce the bug.
In regard to 2. : I think we should discuss if having no Agent Mappings at all is even a valid state for the configuration server, as the server does not really fulfil its use case-without Agent Mappings.
Describe the bug
When there are no files in the working directory of the config server, the default mapping does not work for inspectIT Agents.
Expected behavior
The default mapping should be usable when no custom files are in the file system.
The text was updated successfully, but these errors were encountered: