Serverless invocations details and logging
When you are working on a GitLab Serverless function it is easy to test it locally, but it is difficult to see how it behaves when it actually reacts to events like GitLab Webhooks.
Theses invocations should be visible somewhere. One can install Kibana with Elasticsearch in Knative easily, with only one command:
kubectl apply --filename https://github.com/knative/serving/releases/download/v0.6.0/monitoring-logs-elasticsearch.yaml
but it is still required to run
kubectl proxy locally to access Kibana. Then you need to know how to use Kibana to filter out Kubernetes / Knative noise from function invocations. It is quite cumbersome.
Provide a link to the Kibana dashboard from GitLab serverless tab
- When user installs Knative, automatically install ELK stack along with Knative.
- Set up an Ingress directly to the Kibana page (internet routable using the same base domain as the rest of ingress) and use GitLab OAuth for login.
- how do we communicate to the user that installing this will consume additional resources and may incur additional costs (ie storage)
- Surface access links in serverless or monitoring page
- Have custom queries out of the box