{"action":"closed","issue":{"url":"https://api.github.com/repos/fact-project/shifthelper_webinterface/issues/23","repository_url":"https://api.github.com/repos/fact-project/shifthelper_webinterface","labels_url":"https://api.github.com/repos/fact-project/shifthelper_webinterface/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/fact-project/shifthelper_webinterface/issues/23/comments","events_url":"https://api.github.com/repos/fact-project/shifthelper_webinterface/issues/23/events","html_url":"https://github.com/fact-project/shifthelper_webinterface/issues/23","id":210425288,"number":23,"title":"Log for users","user":{"login":"dneise","id":8200858,"avatar_url":"https://avatars2.githubusercontent.com/u/8200858?v=4","gravatar_id":"","url":"https://api.github.com/users/dneise","html_url":"https://github.com/dneise","followers_url":"https://api.github.com/users/dneise/followers","following_url":"https://api.github.com/users/dneise/following{/other_user}","gists_url":"https://api.github.com/users/dneise/gists{/gist_id}","starred_url":"https://api.github.com/users/dneise/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dneise/subscriptions","organizations_url":"https://api.github.com/users/dneise/orgs","repos_url":"https://api.github.com/users/dneise/repos","events_url":"https://api.github.com/users/dneise/events{/privacy}","received_events_url":"https://api.github.com/users/dneise/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2017-02-27T09:09:15Z","updated_at":"2017-10-19T10:22:46Z","closed_at":"2017-10-19T10:22:46Z","author_association":"OWNER","body":"Adrian @abiland and me recently discussed that it is needed for users to see what the shifthelper is doing at the moment. For example whom it is calling at the moment. \r\nI think this is connected to a request by @dadorner  as well.\r\n\r\nAt first there was the wish expressed to have this on the shifthelper website itself, but we found it might be easier to have this in a log file and present this logfile **somehow** on the shifthelper website (or a site linked from the shifthelper website). \r\n\r\nWe used log.io for presenting logfiles on a website once, but it had no way to show the last 100 lines of a file, but only show new entries since loading time of the page, so a user who wants to see, if the shifthelper is currently calling the fallback or the flare expert, there is no chance .. one has to wait *minutes* until the next call goes out, so log.io is not suitable.\r\n\r\nHowever, the general approach to create a logstream much smaller than the current logstream, e.g. only logging which calls go out, is imho very very easy. \r\nAlso adding log entries to this stream in case certain users say: Well, I would also like to see if this or that check fires ... (not sure why, but let's say they want it)  is much easier than putting more stuff onto the website, I think. So providing such a log-stream is imho the way to go.\r\n\r\nHow to present this stream on a website ... well ... I'm not sure. \r\n\r\nI think currently the webinterface container has no access to the log file folder of the shifthelper, correct? \r\n\r\nI think as a start I would create a simple page which prints the entire (dayly!) logfile and that's it.\r\nJust like the showlog pages, also this page would need to be refreshed manually. \r\n\r\n@MaxNoe would you deal with the part of giving the webinterface container access to the shifthelper logfiles? then I would create such a simple page."}}
{"actor":{"display_login":"dneise"}}