Skip to content
This repository has been archived by the owner on Sep 27, 2019. It is now read-only.

Support function logging #16

Open
yqf3139 opened this issue Mar 24, 2017 · 2 comments
Open

Support function logging #16

yqf3139 opened this issue Mar 24, 2017 · 2 comments
Assignees

Comments

@yqf3139
Copy link
Contributor

yqf3139 commented Mar 24, 2017

Commit a13015e in fission adds function logging.
Fission-ui will add a tab to display logs of a specific function.
The mockup ui will be discussed to deliver a better user experience. Some ideas:

  • The tab can float on the function edit tab or is fixed inside the logging tab. Otherwise the user will need to switch back and forth to update function / invoke function / see the result and logs.
  • Add filters to logs because the logs can provide many fields like time, function-id, pod, stream(stderr, stdout)
  • User can select to follow the logs or just see a snapshot of logs.

Currently fission cli connects to influxdb and polls the logs.
Fission controller may provide a common api to fetch logs for cli and ui. This enhancement can wait until the controller api is ready.

@yqf3139
Copy link
Contributor Author

yqf3139 commented May 12, 2017

This feature is implementing in the func-log branch.
Some modifications:

  • UI directly talks to influxdb service on port 31315 instead of a proxy in the middle
  • Currently the log is placed in a form under the code editor
  • Poll new function logs of current version every 3 seconds
  • The logs produced by draft mode are currently not fetched and shown

@yqf3139 yqf3139 self-assigned this Jun 9, 2017
@yqf3139
Copy link
Contributor Author

yqf3139 commented Jun 9, 2017

Fission has set up a proxy in controller for logs in this commit.
UI will use the controller api to query logs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant