* refactor(ui): add default values for deadman condition
* refactor(ui): limit values to 2 decimal places when dragging thereshold handles
* refactor(ui): prevent system buckets from being deleted or renamed
* refactor(ui): indicate which buckets are system buckets
* refactor(ui): prevent user from creating buckets starting with _
* refactor(ui): remove system bucketes from generate token overlay
* refactor(ui): remove system buckets from bucket dropdowns
* chore(ui): update changelog
At times snowflake id generation would create org and bucket IDs with
characters that had special meaning for the storage engine.
The storage engine concats the org and bucket bytes together into a
single 128 bit value. That value is used in the old measurement
section. Measurement was transformed into the tag, _measurement.
However, certain properties of the older measurement data location
are still required for the org/bucket bytes. We cannot have
commas, spaces, nor backslashes.
This PR puts a specific ID generator in place during the creation of
orgs and buckets. The IDs are just random numbers but with each
of the restricted chars incremented by one. While this changes the
entropy distribution somewhat, it does not matter too much for our
purposes.
... because now org and bucket ids are checked for previous existence
transactionally in the key-value stores. If the ID does already exist
then we try to generate a new key up to 100 times.
Semantically, we've done the following:
// name of the client sending the alert.
client: "influxdata"
// url of the client sending the alert.
client_url: the endpoint URL for now (needs to change to rule)
// The class/type of the event, for example ping failure or cpu load
class: check's name
// Logical grouping of components of a service, for example app-stack
group: source measurement
Co-authored-by: Alirie Gray <alirie.gray@gmail.com>
* refactor(ui): move check message to its own card
* refactor(ui): ensure builder cards fill width of overlay
* refactor(ui): make conditions boxes fill width of parent
* refactor(ui): allow check properties card to grow
* refactor(ui): remove matching rules card
* chore(ui): update changelog
Remove unused action
Co-Author: Deniz Kusefoglu <deniz@influxdata.com>
add Limits and LimitsStatus to cloud types
Add asset limits for checks, rules and endpoints
Filter blocked endpoint types
fix: type error
Co-Author: Deniz Kusefoglu <deniz@influxdata.com>
This adds the _version: 1 correctly to the body of the HTTP POST.
Additionally, this fixes the imports when using secrets.
The POSTed JSON body now is:
```json
{
"_check_id": "046cac59e2aa3000",
"_check_name": "High CPU User Usage",
"_level": "crit",
"_measurement": "notifications",
"_message": "High CPU User Usage: rsavage.prod is crit",
"_notification_endpoint_id": "046cad0c83aec000",
"_notification_endpoint_name": "HTTP Endpoint",
"_notification_rule_id": "046dff53d4183000",
"_notification_rule_name": "HTTP Notification",
"_source_measurement": "cpu",
"_source_timestamp": 1567797375000000000,
"_start": "2019-09-06T19:15:59Z",
"_status_timestamp": 1567797376416632300,
"_stop": "2019-09-06T19:16:20.362006739Z",
"_time": "2019-09-06T19:16:20.609629338Z",
"_type": "threshold",
"_version": 1,
"cpu": "cpu-total",
"host": "rsavage.prod",
"usage_user": 91.12278069517379
}
```