To have checks and notifications happen transactionally we need to be
able to alert the task system when a new task was created using the checks and notifications systems.
These two new middlewares allow us to inform the task system of a update
to a task that was created through the check or notification systems.
* refactor(ui): extend url activator to check on deeper URLs
* refactor(ui): create load data nav and page components
* refactor(ui): update telegrafs, scrapers, and buckets to use load data nav
* refactor(ui): update side nav and router to expose load data tab
* chore(ui): update changelog
* refactor(ui): update link to telegrafs page from status page
* refactor(ui): fix broken routes
* refactor(ui): make settings page tabs consistent with load data tabs
* refactor(ui): appease the linter gods
* refactor(ui): attempt to fix e2e tests
* adding new templates; removing calls to create templates
* fixing quickstart dashboard creation
* Type dashboard template
* bump templates repo version
* add templateID to template meta in swagger
* Add templateID to document meta type in UI
* add templateID to telegrafPlugin and telegrafplugin info types
* Instantiate templates from static templates
* Get tests to pass
* Fix type conflicts
* Bump templates version
* update changelog
If client requests with Accept-Encoding: gzip, then
compress response and return with Content-Encoding: gzip.
This increases the server-side load by about 12%, but saves network bandwidth.
benchmark old ns/op new ns/op delta
Benchmark_Query_no_gzip-4 123609 137885 +11.55%
benchmark old allocs new allocs delta
Benchmark_Query_no_gzip-4 149 150 +0.67%
benchmark old bytes new bytes delta
Benchmark_Query_no_gzip-4 14297 15205 +6.35%
* Report errors found when iterating over flux query in task
* Add failing test for tasks executor result iterator exhaust failure
* Ensure errors exhausting tasks query result iterator are surfaced as task failure
* Update CHANGELOG with task result iteration error surfacing fix
* Add scatter to visualization types dropdown
* Add initial scatter options
* Add scatter visualization to view switcher
* Add scatter to VEO
* Add scatter type to graph types
* Expand scatter options
* Update changelog
* Change scatter color type to strings
* Assume fluxgroupkey is set
* Regularize scatter options
* Place scatter behind feature flag
Co-authored-by: Jade McGough <jade@influxdata.com>
* Add session renew option to launcher and use in middlewhere
* pass session options to services
* Update SessionAutoRenew to SessionRenewDisabled
* Add test for service constructor defaults
* Update changelog
The method we used to compute a single stat / gauge value previously did
account for missing data. If the latest value in a response was part of
a numeric column but was null/NaN/not defined, the single stat
computation would fail and a user would see an error message "Could not
display single stat because your values are non-numeric".
This commit updates the single stat computation to find the latest
*defined* numeric values.
If no latest valid numeric values are found, we will either:
- Display an error message if using the compuation within a single stat
visualization
- Display nothing if using the computation within a within a line +
single stat visualization (i.e. display the line vis only)
If multiple latest values are found, we make an arbitrary selection
(same as previous behavior). The goal is to eventually expose UI
elements to the user so they can make this selection themselves.
This commit also updates the single stat computation to use the
@influxdata/vis `Table` format as an intermediate/parsed representation
of a Flux CSV response. This unlocks the possibility for performance
gains in our CSV parsing. See #13852.
Closes#13824