Bug 1329572 - Need to log user access/actions via SSH
Summary: Need to log user access/actions via SSH
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Logging
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: chunchen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-22 09:34 UTC by Jaspreet Kaur
Modified: 2019-10-10 11:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-13 18:39:46 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jaspreet Kaur 2016-04-22 09:34:48 UTC
Description of problem: Need to log access and actions performed by users on the application/gear via SSH. What I need is a daily file (log) of the actions performed by the user.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 6 Rory Thrasher 2016-04-27 20:44:39 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

Comment 7 Rory Thrasher 2016-05-13 18:39:46 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.