| Summary: | Need to log user access/actions via SSH | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Jaspreet Kaur <jkaur> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED NOTABUG | QA Contact: | chunchen <chunchen> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.x | CC: | aos-bugs, jkaur, rthrashe, wsun |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-13 18:39:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jaspreet Kaur
2016-04-22 09:34:48 UTC
Jaspreet, Any command run on the system while SSH'd in should be stored to the ./app-root/data/.bash_history file, and can be accessed using the `history` command as well. This can be edited, so it wouldn't be suitable for security purposes. The customer may also find that tailing the logs is helpful. See https://developers.openshift.com/managing-your-applications/log-files.html for more information there. Finally the script command may be useful if the customer needs more information than history provides. Running `script ./app-root/data/foo.txt` will record the current bash session to the specified file, including all output. Hopefully some combination of those options will meet the customer's requirement. If not, a specific example of what the customer is looking to do (such as recording bash commands to later create a script) may help us find another solution. Rory Going to go ahead and close this as the customer case seems to be closed. Please feel free to reopen if the customer has more questions. |