* add opentracing section and otelCollectorEndpoint * initialize OTLP exporter * pkg/controller: changes for context propagation * pkg/executor: changes for context propagation * pkg/fetcher: changes for context propagation * pkg/router: changes for context propagation * pkg/storagesvc: changes for context propagation * set no default value for otel collector endpoint * update readme and add notes to charts * move common code to pkg/utils/otel * adding fn and env as attributes * don't use otelhttp transport for websocket * URL ignore with common filter UrlsToIgnore Note: The web socket example does not work when using OTEL HTTP. Here is an issue related to that on open-telemetry/opentelemetry-js-contrib. Signed-off-by: Gaurav Gahlot <gauravgahlot0107@gmail.com> Co-authored-by: Sanket Sudake <sanketsudake@gmail.com>
StorageSvc
StorageSvc consists of 3 components
- Storage http request handler
- StowClient
- ArchivePruner
StorageSvc
This is the HTTP handler that serves requests to :
- upload archive into a storage
- fetch an archive from storage
- delete archive from storage
StowClient
This is the storage interface layer that interacts with stow package. It provides methods to:
- write a file to storage
- retrieve a file from storage
- delete a file from storage
- get all files on storage
ArchivePruner
This acts like a cron job to clean up orphaned archives from storage. By default configured to run every hour. The value can be set in Values.yaml to any preferred interval.