* feat(ui): Add matching rules card to alert builder
* feat(checks): Add tags from query results to NR matching query parameters
* feat(ui): Update changelog
* feat(nr): Change api function to match import convention
* fix(ui): Fix changelog update mistake
* Click submit button after typing in time machine
* feat(notification rules): Add feature flag to matching notification rules
* feat(checks): Add custom check type
* feat(checks): Remove alert builder from custom check
* feat(checks): Add AlertBuilderAction to list of possible actions
* feat(checks): Query visualization does not make sense for custom check
* feat(check): check editor should only reexecute queries if view query changes
* Update ui/src/timeMachine/components/TimeMachineFluxEditor.tsx
Co-Authored-By: Bucky Schwarz <hoorayimhelping@users.noreply.github.com>
* Address PR review
Co-authored-by: Bucky Schwarz <hoorayimhelping@users.noreply.github.com>
issue here is that the unique by name index for variables was implemented
and has the same functionality about it that this orgs index has. The duplicative
orgs index was nuked. The migration to hydrate the org/name index never
happened. This is a stop gap until that migration is in place.
this is work moving us towards more reusable components that add some
rigidity around handling indexes and the entity bucket. The behavior
is very common across much of the kv pkg. This can be reused throughout.
adding some easy wins for tracing(eventually metrics) that enable more
insight that what is currently possible. It normalizes these concerns
across the kv store.
With `/health`, it is possible to override the overall status reported.
This change adds the same functionality to `/ready`. This allows
incident responders to take an unhealthy pod out of a service without
killing it—giving them time to gather meaningful forensic data from the
pod. The new contract is:
Force not ready:
GET /ready?force=true&ready=false
Force ready:
GET /ready?force=true&ready=true
Disable override:
GET /ready?force=false
feat(ui): added last run status checks for notification rules and check rules, readded updateCheck to fix linter and functionality issues with program and added tests to ensure check creation and update stability
this provides influxdb.Errors whenever possible from the pker service layer.
the behavior that caused the error is somewhat implicated in the errro code.
it is not perfect but is a big step forward. using the http server/client to
run pkger stuff makes it abundantly clear the errors need to be communicated
better.
closes: #16313
* refactor: use replace select group with tabs in save as dialog
* refactor: replace local RightClick with Clockface RightClick
* refactor: delete local RightClick code
* refactor: replace ResponsiveGridSizer with SquareGrid
* chore: delete local grid sizer components
* fix: repair broken e2e tests
* fix: attempt to fix e2e test
* fix: repair query builder e2e test
* fix: don't call stop propagation because there is no event object
* refactor: extend DragAndDrop to support custom classnames
* refactor: use OverlayFooter
* refactor: remove WizardOverlay from CollectorsWizard
* refactor: redesign and simplify line protocol wizard
* refactor: remove WizardOverlay from telegraf instructions
* fix: repair affected e2e test
* refactor: use vscss ariable to ensure height consistency between steps
* refactor: extract helper text into component to ensure consistency