* feat(user): support sso and api key
* feat(user): remove ee references from pkg
* feat(user): remove ee references from pkg
* feat(user): related client changes
* feat(user): remove the sso available check
* feat(user): fix go tests
* feat(user): move the middleware from ee to pkg
* feat(user): some more error code cleanup
* feat(user): some more error code cleanup
* feat(user): skip flaky UI tests
* feat(user): some more error code cleanup
* feat: added order by span_count in traces tab
* feat: added order by span_count in traces tab
* feat: added order by span_count in traces tab
* feat: added order by span_count in traces tab
* feat: added order by span_count in traces tab
* feat: added order by span_count in traces tab
---------
Co-authored-by: Nityananda Gohain <nityanandagohain@gmail.com>
### Summary
Integrate the new implementations of the alertmanager along with changes to the ruler. This change can be broadly categoried into 3 parts:
#### Frontend
- The earlier `/api/v1/alerts` api was double encoding the response in json and sending it to the frontend. This PR fixes the json response object.
For instance, we have gone from the response `{
"status": "success",
"data": "{\"status\":\"success\",\"data\":[{\"labels\":{\"alertname\":\"[platform][consumer] consumer is above 100% memory utilization\",\"bu\":\"platform\",\"......
}` to the response `{"status":"success","data":[{"labels":{"alertname":"[Metrics] Pod CP......`
- `msteams` has been changed to `msteamsv2` wherever applicable
#### Ruler
The following changes have been done in the ruler component:
- Removal of the old alertmanager and notifier
- The RuleDB methods `Create`, `Edit` and `Delete` have been made transactional
- Introduction of a new `testPrepareNotifyFunc` for sending test notifications
- Integration with the new alertmanager
#### Alertmanager
Although a huge chunk of the alertmanagers have been merged in previous PRs (the list can be found at https://github.com/SigNoz/platform-pod/issues/404), this PR takes care of changes needed in order to incorporate it with the ruler
- Addition of ruleId based matching
- Support for marshalling the global configuration directly from the upstream alertmanager
- Addition of orgId to the legacy alertmanager
- Support for always adding defaults to both routes and receivers while creating them
- Migration to create the required alertmanager tables
- Migration for msteams to msteamsv2 has been added. We will start using msteamv2 config for the new alertmanager and keep using msteams for the old one.
#### Related Issues / PR's
Closes https://github.com/SigNoz/platform-pod/issues/404
Closes https://github.com/SigNoz/platform-pod/issues/176
* feat: bug fix for the issue in span filtering feature. No spans returned in traces tab
* feat: bug fix for the issue in span filtering feature. No spans returned in traces tab
* fix: use common timeout middleware
* fix: use apiserver factory for config
* fix: add backward compatibility for old variables
* fix: remove apiserver provider and use config directly
* fix: remove apiserver interface
* fix: address comments
* fix: address minor comments
* fix: address minor comments
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: add search span scope in the list view tab to add the scope at per query level
* feat: update clickhouse reader to support new trace schema
* fix: minor fixes
* fix: address comments
* fix: add changes to overview function
* fix: add changes to overview function
* fix: use hardcoded true
* fix: address comments
* feat: support for new enrichment logic in traces
* fix: default test added
* fix: update func name in links
* Update pkg/query-service/utils/logs_test.go
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
---------
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* feat: support for window based pagination in new trace v4
* fix: update pagination logic
* fix: update comment
* fix: substract correct length
* fix: revert changes
* fix: add tests for querier
* fix: rename matcher
* fix: handle offset inmemory for list queries in traces
* fix: correct var name
* fix: add max pagination limit for traces
* feat: trace V4 QB
* fix: update get column name and remove id
* fix: handle contains and update tests
* fix: remove unwanted step interval calculation
* fix: add test cases
* fix: add tests for static columns in QB
* fix: add more order by tests
* fix: update order by logic
* fix(query): #5861 Changes query which improves performance
* fix(test): fixed all the build test
* fix(test): fixed all the build test
* fix(test): fixed all the build test
* fix(test): fixed all the build test
* fix(test): fixed all the build test
* fix(test): fixed all the build test
* feat: logsV4 initial refactoring
* feat: filter_query builder with tests added
* feat: all functions of v4 refactored
* fix: tests fixed
* fix: update select for table panel
* fix: tests updated with better examples of limit and group by
* fix: resource filter support in live tail
---------
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* chore: put together helper for fetching values for multiple attributes
* chore: poc: use helper for filter suggestions
* chore: add a working impl for getting attrib values for multiple attributes
* chore: start updating integration test to account for new approach for getting log attrib values
* chore: use a global zap logger in filter suggestion tests
* chore: fix attrib values clickhouse query expectation
* chore: only query values for actual attributes when generating example queries
* chore: update clickhouse-go-mock
* chore: cleanup: separate params for attributesLimit and examplesLimit for filter suggestions
* chore: some test cleanup
* chore: some more cleanup
* chore: some more cleanup
---------
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
* chore: stash initial work with API signature
* chore: put together setup for integration testing filter suggestions
* feat: filter suggestions: suggest attribs using existing autocomplete logic
* chore: filter suggestions test: add expectation for example queries
* feat: filter suggestions: default suggestions when data yet to be received
* feat: finish plumbing basic example queries
* chore: add test for filter suggestions with an existing query
* feat: filter suggestions: don't suggest attribs already included in existing filter
* chore: generate example queries by including existing filter first
* chore: upgrade ClickHouse-go-mock
* chore: some cleanup of reader.GetQBFilterSuggestionsForLogs
* chore: some cleanup of filter suggestion tests
* chore: some cleanup to http handler and request parsing logic for filter suggestions
* chore: remove expectation that attrib suggestions won't contain attribs already used in filter
