Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POST resquests have not been logged #264

Open
Truja opened this issue Dec 11, 2013 · 2 comments
Open

POST resquests have not been logged #264

Truja opened this issue Dec 11, 2013 · 2 comments
Milestone

Comments

@Truja
Copy link
Contributor

Truja commented Dec 11, 2013

When you perform POST requests like storagepool (de)activation or network (de)activation, the request is not logged in the stdout or in the log files.

As an admin, I think this kind of log/output is important, to track problems or other things.

@sming56
Copy link

sming56 commented Dec 11, 2013

When I activated/deactivated the storage pool, I got these two messages logged.
9.181.193.205 - tmp [11/Dec/2013:01:58:54] "GET /storagepools/nfs-1 HTTP/1.1" 200 225 "https://9.181.129.157:8001/" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0"
9.181.193.205 - tmp [11/Dec/2013:01:58:54] "GET /storagepools HTTP/1.1" 200 568 "https://9.181.129.157:8001/" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0"

It seems cherrypy logged the GET method.after the successful POST action.

@Truja
Copy link
Contributor Author

Truja commented Dec 11, 2013

Yes, and it is not possible to know which action was performed. I need to look deeper on this. If cherrypy does not log the POST automatically, then we must improve our kimchi.logs

@alinefm alinefm added this to the Backlog milestone Dec 3, 2014
@alinefm alinefm modified the milestones: Kimchi 1.4.1, Backlog Dec 24, 2014
@cd1 cd1 modified the milestones: Kimchi 1.4.1, Backlog Mar 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants