Mirth Connect
  1. Mirth Connect
  2. MIRTH-664

Seperate out Mirth.log from Wrapper.log

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 1.8.1
    • Component/s: Server Manager
    • Labels:
      None

      Description

      In the Server Manager it would be helpful to list just the Mirth.log and Wrapper.log file with a checkbox to list the history for each type of log file. This would make it more obvious there are two different log files.

        Activity

        John Lehew created issue -
        Christopher Lang made changes -
        Field Original Value New Value
        Fix Version/s 2.0.0 [ 10056 ]
        Gerald Bortis made changes -
        Component/s Service Manager [ 10102 ]
        Fix Version/s 1.8.0 [ 10100 ]
        Fix Version/s 2.0.0 [ 10056 ]
        Assignee Christopher Lang [ chrisl ] Brendan Haverlock [ brendanh ]
        Brendan Haverlock made changes -
        Fix Version/s 1.8.1 [ 10131 ]
        Fix Version/s 1.8.0 [ 10100 ]
        Hide
        Jacob Brauer added a comment -

        This list will show any files in the logs directory, not just the wrapper and mirth log.

        Show
        Jacob Brauer added a comment - This list will show any files in the logs directory, not just the wrapper and mirth log.
        Jacob Brauer made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Won't Fix [ 2 ]
        Jacob Brauer made changes -
        Workflow jira [ 10886 ] connect [ 14686 ]
        Status Closed [ 6 ] Resolved [ 5 ]
        Jacob Brauer made changes -
        Workflow connect [ 14686 ] jira [ 15697 ]
        Jacob Brauer made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Jacob Brauer made changes -
        Workflow jira [ 15697 ] Editable JIRA Workflow [ 43737 ]

        This list may be incomplete, as errors occurred whilst retrieving source from linked applications:

        • Request to http://www.mirthcorp.com/community/fisheye/ failed: Error in remote call to 'Fisheye / Crucible' (http://www.mirthcorp.com/community/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=MIRTH-664, expand=changesets[0:20].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)

        This list of reviews may be incomplete, as errors occurred retrieving data from the following repositories:

        • Request to http://www.mirthcorp.com/community/fisheye/ failed: Error in remote call to 'Fisheye / Crucible' (http://www.mirthcorp.com/community/fisheye) [AbstractRestCommand{path='rest-service/search-v1/reviews', params={term=MIRTH-664, maxReturn=50}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
        • Request to http://www.mirthcorp.com/community/fisheye/ failed: Error in remote call to 'Fisheye / Crucible' (http://www.mirthcorp.com/community/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=MIRTH-664, expand=changesets[-100:-1]}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)

          People

          • Assignee:
            Brendan Haverlock
            Reporter:
            John Lehew
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: