Closed Toparvion closed 4 years ago
The problem was in TailEventHandler#processFileTailingEvent
method, which used to extract the event source's log path from toString()
method of the corresponding bean (please don't ask me why 😄). From now on it uses ContainerTargetFile#getAbsolutePath
method whose result is controlled by our preceding logic (for example see TailingFlowProvider#newTailAdapter4Docker
method) and thus should be protected from changes in upcoming versions of frameworks.
I asked our teammates to check the fix in their AnaLog deployment. Will proceed with this PR when they reply.
Out teammates reported they don't see any changes to the popups' behavior. Will investigate it further...
Found the source of the reported problem and fixed it. Waiting for the feedback again.
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells
So, I've finally fixed the problem and eventually added unit tests to the TailEventHandler
(thanks to SonarCloud that forced me to do it).
This issue appeared to be not so simple as it seemed at the beginning. Nonetheless we've fixed it. Another good experience 🙂
Fixes #26 .
Changes summary:
toString()
method anymoreContainerTargetFile
as the provider of information about event sourceLocalizedLogger