aniketio-ctrl
f9a70a3a69
chore: notification routing | added notificaiton routing via expression based routes ( #9195 )
...
* chore: added custom distpatcher
* feat(notification-grouping): added notification grouping
* feat(notification-grouping): addded integration test dependency
* feat(notification-grouping): linting and test cases
* feat(notification-grouping): linting and test cases
* feat(notification-grouping): linting and test cases
* feat(notification-grouping): addded integration test dependency
* feat(notification-grouping): debug log lines
* feat(notification-grouping): debug log lines
* feat(notification-grouping): debug log lines
* feat(notification-grouping): addded integration test dependency
* feat(notification-grouping): addded integration test dependency
* feat(notification-grouping): addded integration test dependency
* feat(notification-grouping): added structure changes
* feat(notification-grouping): added structure changes
* feat(notification-routing): added notification routing
* chore(notification-grouping): added notificaiton grouping
* Update pkg/alertmanager/nfmanager/rulebasednotification/provider.go
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* chore(notification-grouping): added renotification interval
* fix(notification-grouping): added fix for renotification
* chore(notificaiton-grouping): added no data renotify
* chore(notificaiton-grouping): added no data renotify
* chore(notificaiton-grouping): added no data renotify
* chore(notification-grouping): added no data renotify interval
* chore(notification-grouping): removed errors package from dispatcher
* chore(notification-grouping): removed errors package from dispatcher
* chore(notification-grouping): removed unwanted tests
* chore(notification-grouping): removed unwanted pkg name
* chore(notification-grouping): added delete notification setting
* chore(notification-grouping): added delete notification setting
* Update pkg/alertmanager/nfmanager/nfmanagertest/provider.go
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* chore(notification-grouping): removed nfmanager config| notification settings in postable rule
* chore(notification-grouping): removed nfmanager config| notification settings in postable rule
* chore(notification-grouping): added test for dispatcher
* chore(notification-grouping): added test for dispatcher
* chore(notification-grouping): go linting errors
* chore(notification-grouping): added test cases for aggGroupPerRoute
* chore(notification-grouping): added test cases for aggGroupPerRoute
* chore(notification-grouping): corrected get notification config logic
* Update pkg/alertmanager/nfmanager/rulebasednotification/provider_test.go
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* chore(notification-routing): added notification routing policies
* feat(notification-routing): added test cases for dispatcher
* chore(notification-routing): added notification routing policies
* chore(notification-routing): added notification routing policies
* Apply suggestions from code review
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* chore(notification-routing): added notification routing policies
* chore(notification-routing): added notification routing policies
* Update pkg/alertmanager/alertmanagerserver/distpatcher_test.go
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* chore(notification-routing): sorted imports
* chore(notification-routing): minor edit |pr resolve comments
* chore(notification-grouping): corrected dispatcher test cases
* chore(notification-routing): added notification routing policies
* chore(notification-routing): corrected race condition in test
* chore: resolved pr comments
* chore: passing threshold value to tempalte
* chore: completed delete rule functionality
* chore: added grouping disabled functionality
* chore: added grouping disabled functionality
* chore(notification-routing): resolved pr comments
* chore(notification-routing): resolved pr comments
* chore(notification-routing): resolved pr comments
* chore(notification-routing): sorted imports
* chore(notification-routing): fix linting errors
* chore(notification-routing): removed enabled flags
* fix: test rule multiple threhsold (#9224 )
* chore: corrected linting errors
* chore: corrected linting errors
* chore: corrected linting errors
* chore: corrected linting errors
* chore: corrected migration errors
* chore: corrected migration errors
* chore: corrected migration errors
* chore: corrected migration errors
* Update pkg/sqlmigration/049_add_route_policy.go
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* chore: added org_is as foreign key
* chore: resolved pr comments
* chore: removed route store unused
---------
Co-authored-by: Srikanth Chekuri <srikanth.chekuri92@gmail.com>
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
2025-10-03 19:47:15 +05:30
aniketio-ctrl
735b90722d
chore(notification grouping): added custom grouping in signoz dispatcher ( #8812 )
2025-09-26 13:24:58 +00:00
Vibhu Pandey
31e042adf7
feat(alertmanager): deprecate legacy alertmanager ( #9046 )
...
- Deprecate legacy alertmanager. Are the new alert improvements compatible with legacy? I don't think they are. More importantly, I don't think they should be. It will be a pain to manage it at both places.
- Improve msteamsv2 experience. I have taken alertmanager's upstream and merged it with our custom implementation. Note the use of `titleLink` field to propagate the url of the alert.
- Delete the private http server needed for alertmanager. It's cleanup as part of 1.
2025-09-10 08:28:13 +00:00
aniketio-ctrl
c737a7e070
chore: enable alertmanager metrics collection with instrumentation::metrics ( #9020 )
...
* feat(alerts-v2): exposed alertmanager metrics for signozalertmanager
* feat(alerts-v2): exposed alertmanager metrics for signozalertmanager
* feat(alerts-v2): exposed alertmanager metrics for signozalertmanager
* feat(notification-routing): added custom meter provider
* feat(notification-routing): added custom meter provider
* feat(notification-routing): added custom meter provider
* feat(notification-routing): added custom meter provider
* feat(notification-routing): added org id label
2025-09-08 14:41:18 +05:30
Nityananda Gohain
3100d602c4
Revert "feat: adds trace funnels ( #7315 )" ( #7423 )
...
This reverts commit b36d2ec4c6ae6a21068985a0a9a8f890a6b9a083.
2025-03-24 14:00:14 +00:00
Shivanshu Raj Shrivastava
b36d2ec4c6
feat: adds trace funnels ( #7315 )
...
* feat: trace funnels
Signed-off-by: Shivanshu Raj Shrivastava <shivanshu1333@gmail.com>
2025-03-23 22:35:30 +05:30
Shivanshu Raj Shrivastava
efd4e30edf
fix: publish signoz as package ( #7378 )
...
Signed-off-by: Shivanshu Raj Shrivastava <shivanshu1333@gmail.com>
2025-03-20 15:31:41 +00:00
Vibhu Pandey
7118829107
fix(test|lint): fix lint and test in go ( #7346 )
...
### Summary
- fix lint and test in go
2025-03-18 14:01:48 +05:30
Vibhu Pandey
06be0f4330
fix(alertmanager): fix templating ( #7288 )
...
### Summary
- Fix templating of alertmanagerURL to include links to our alerts page
- Return an empty array instead of null in contextlinks
2025-03-12 23:15:58 +05:30
Vibhu Pandey
1f33928bf9
feat(alertmanager): integrate with ruler ( #7222 )
...
### 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
2025-03-09 20:00:42 +00:00
Vibhu Pandey
02865cf49e
feat(sqlstore): add transaction support for sqlstore ( #7224 )
...
### Summary
- add transaction support for sqlstore
- use transactions in alertmanager
2025-03-05 18:50:48 +05:30
Vibhu Pandey
8a01312967
feat(alertmanager): simplify and test e2e alertmanager ( #7217 )
...
* refactor(alertmanager): complete e2e testing and simplify
* fix(alertmanager): fix typo
* fix(alertmanager): set to true for prometheus
2025-03-05 10:01:02 +05:30
Vibhu Pandey
639b9a5a8a
feat(legacyalertmanager): add legacyalertmanager ( #7156 )
2025-02-20 14:14:09 +05:30
