* build: integrate sql migrations for clickhouse
* feat: support error/exception attributes for trace
* chore: fixing dependencies for docker go client libs
* feat: get trace filter api checkpoint
* chore: fixing dependencies for go-migrate
* feat: add new columns
* feat: move mirgate run from docker to code
* fix: migration file 404 issue
* feat: getSpanFilter API
* fix: migrate version naming bug
* chore: change url param format to array
* feat: add getTagFilter API
* feat: add getFilteredSpans API
* fix: using OFFSET in sqlx driver
* feat: aggregates API on getFilteredSpan, use IN and NOT IN for tag filtering
* feat: add more function support to span aggregate API
* fix: null component edge case
* feat: groupBy support for filteredSpanAggregate
* feat: add function param to span aggregate API
* feat: add support to return totalSpans in getFilteredSpans API
* fix: don't return null string as keys in span filters
* chore: remove SQL migrations(moved to otel collector)
* fix: null string issue in aggregate API
* Merge main
* fix: trace API db query param
* fix: signoz sql db path
* fix: case when both error and ok status are selected
Co-authored-by: Ankit Nayan <ankit@signoz.io>
There are other files that can affect the correctness of the code rather
than the src files like the deployment yamls, Makefile etc.
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
This workflow will push up to 2 images with 4 tags, depending on
if they changed since the last image.
* query-service:<git sha>
* query-service:master
* frontend:<git sha>
* frontend:master
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
As of now, the 'e2e-k3s' workflow will require the 'ok-to-test' label in
order to get triggered.
In addition to that, on each change to the PR on the relevant files,
Github will remove the label from it and it will be required again.
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
* ci: adding 'e2e' GH workflows
The flow contains of multiple steps:
* build 'query-service' and 'frontend' images and push them to the image registry
* deploy a disposable k3s cluster
* deploy the app on the cluster
* set a tunnel to allow accessing the UI from the web browser
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
* ci: requiring the 'ok-to-test' label for running some workflows
As of now, the 'e2e' workflow will require the 'ok-to-test' label in
order to get triggered.
In addition to that, on each change to the PR, Github will remove the
label from it and it will be required again.
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
The flow contains of multiple steps:
* build 'query-service' and 'frontend' images and push them to the image registry
* deploy a disposable k3s cluster
* deploy the app on the cluster
* set a tunnel to allow accessing the UI from the web browser
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
query-service job is currently building flattener and flattener job is
currently building query-service.
This PR should fix that mix.
Signed-off-by: Yoni Bettan <ybettan@redhat.com>
