* bugfix: 'state:storeInSessionStorage' doesn’t take effect for dashboard without full page reload
* add test “changing 'state:storeInSessionStorage' also takes effect without full page reload”
* Initial move of public and setup of server skeleton
* Fix public paths and types
* Use new usage stats dependency directly in tracker also mark as an optional dependency
* WiP on getting server side working
* Restore proxy route behaviour for base case, still need to test custom proxy and SSL
* Add new type and lib files
* Clean up legacy start up code and add comment about issue in kibana.yml config for console
* Move console_extensions to new platform and introduce ConsoleSetup API for extending autocomplete
Add TODO regarding exposing legacy ES config
* Re-introduce injected elasticsearch variable and use it in public
* Don't pass stateSetter prop through to checkbox
* Refactor of proxy route (split into separate files). Easier testing for now.
Refactor file name of request.ts -> proxy_request.ts. This is consistent with the exported function now
Started fixing server side tests for the proxy route
- Migrated away from sinon
- Completed the body.js -> body.test.ts. Still have to do the rest
* headers.js test -> headers.test.ts and moved some of the proxy route mocking logic to a common space
* Finish migration of rest of proxy route test away from hapi
Add test for custom route validation
* Bring console application in line with https://github.com/elastic/kibana/blob/master/src/core/CONVENTIONS.md#applications
Change log from info level to debug level for console_extensions plugin
* Update i18nrc file for console
* Add setHeaders when passing back error response
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Set the height of the service map dynamically
* Move the loading overlay from the outside to the inside of the Cytoscape container
* Remove the EUI spacer from the Home and ServiceDetailTabs components and add it to the individual components that use them
* Add unit test for missing geo on named location.
* WIP writing a functional test.
* New named-location with no geo data test is functioning.
* Update snaps for functional test attribute.
* Rename test.
* Remove unnecessary async syntax.
* Delete unneeded symbols.
* Remove unnecessary boolean conversion.
* Fix typo in a comment.
* [Maps] tighten default map zoom
* rework using bounds to work on multiple screen resolutions
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
This makes the "Log rate" and "Categories" tab visible on clusters with a suitable license for users which don't have the the `machine_learning_admin` role.
* Shim the default_editor
* Update paths in vis_default_editor
* Update paths in dependent plugins
* Update the dependent plugins
* Create an entry point
* Wrap the editor with kibana context
* Fix circular re-renders
* Update sub aggs mapping
* Move schemas and agg_groups to agg_types, update jest tests
* Use services from kibana context, other fixes
* Fix useEffect maximum update depth
* Create i18n namesapce for visDefaultEditor, rename translations
* Fix tests
* Resolve paths
* Remove ui/vis/vis_types
* Fix vis import
* Move editor_config_provider to ui/vis
## [SIEM] Overview page feedback
Implements feedback and fixes to the Overview page
### Overview (default theme)
![01-overview-default-theme](https://user-images.githubusercontent.com/4459398/73315509-899c5500-41ed-11ea-9949-82853dd4ba59.png)
### Overview (dark theme)
![02-overview-dark-theme](https://user-images.githubusercontent.com/4459398/73315527-902acc80-41ed-11ea-9701-6a2c5fa40cce.png)
## Highlights
* The new order of widgets is Signals, Alerts, Events, Host Events, Network events, per https://github.com/elastic/siem-team/issues/494
* Changed the default `External alerts count` `Stack by` to `event.module` https://github.com/elastic/siem-team/issues/491
* Added `event.module` to the `Events count` histogram https://github.com/elastic/siem-team/issues/491
* Widget titles will no longer include the currently selected `Stack by option`. The widgets will use the same static title text that appears on the other pages (i.e.. `Signals count`, `External alerts count`, and `Events count`) https://github.com/elastic/siem-team/issues/491
* The `Signals count` includes a `Stack by` that defaults to `signal.rule.threat.tatic.name`
* Standardized on a 300px widget height for all histograms in the app (thanks @MichaelMarcialis for paring on this!)
* The `Open as duplicate timeline` action is `Recent timelines` is now only shown when hovering over a recent timeline
## Loading States
* The `Recent timelines` and `Security news` widgets now use the horizontal bar loading indicator
* The `Host events` and `Network events` widgets now use the horizontal bar loading indicator
* The `Host events` and `Network events` Showing _n_ events subtitles are now hidden on initial load
* The counts in the `Host events` and `Network events` Showing _n_ events subtitles are now hidden on initial load
* We no longer hide some histogram subtitles after initial load, to prevent shifting of content when a user makes a `Stack by` selection
## News Feed Error State
![news-feed-error-state](https://user-images.githubusercontent.com/4459398/73316060-1e538280-41ef-11ea-83f5-b8d6e9fa3741.png)
* Fixed an issue where the `Security news` header was hidden when an invalid URL is configured
* Added a space between the word `via` and the `SIEM advanced settings` link
* Removed the capital “N” from "News" in the error message
## Misc Visual Changes
* Fixed text truncation of the `Severity` column in the `Detections` page's `Signals` table
* Added the “showing” subtitle to the `Signals count` histogram on the Detections page
* Increased the `Stack by` histogram selector and the `View signals | alerts | events' buttons from 8 to 24px
* Tweaked the border rendering in the Overview `Host Events` and `Network events` widget headers
* Added 8px of spacing between the Overview `Host Events` and `Network events` widget accordion headers and their contents
* Fixed an issue where the `Host events` and `Networ events` widgets didn't render in ie11 https://github.com/elastic/siem-team/issues/499
## Non-Visual Fixes
* Removed an incorrect usage of `usememo`
* Removed the placeholder client-side username query from `x-pack/legacy/plugins/siem/public/components/recent_timelines/index.tsx`
* Updated the query of the Overview `Host events` widget to filter by "host.name exists"
* Updated the query of the Overview `Network events` widget to filter by "source.ip exists or destination.ip : exists"
* Use src/plugins/inspector instead of ui/inspector
* Remove unused ui/inspector
* Use `inspector` plugin directly to register view
* Fix path
* Use inspector from NP
* Revert view registration to a separate file
* sets up initial grid and data type
* data feeds in from backend but doesnt update
* sample data feeding in correctly
* Fix combineReducers issue by importing Redux type from 'redux' package
* Add usePageId hook that fires action when user navigates to page
* Strict typing for middleware
* addresses comments and uses better types
* move types to common/types.ts
* Move types to endpoint/types.ts, address PR comments
blah 2
Co-authored-by: Pedro Jaramillo <peluja1012@gmail.com>
* Always return a contract from the newsfeed plugin
Without a contract, dependent plugins have no way of knowing whether the
plugin is enabled or not as the contract will always be undefined.
* Export newsfeed contract types from public index
So that dependent plugins can use them.
* Declare newsfeed as an optional dependency of SIEM
We're going to use the availability of the newsfeed plugin as part of our
determination for whether or not to show the security newsfeed. If users
set `newsfeed.enabled: false`, the plugin will be unavailable and the
security feed will not be shown.
* Respect global newsfeed.enabled config in Security newsfeed
The presence of the newsfeed plugin means that newsfeed.enabled is true.
If both that and our local setting are true, we will show the Security
feed.
* Prefer object type over empty interface
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Put the notice for rules in comment block
This comment block marked by `@notice` is picked up by automation and included
in the Kibana NOTICE.txt that we ship with the tar.gz.
Follow up for #56090.
* utilize createdAt and updatedAt from the alerting saved object
* revert accidental change to test rule
* updatedAt is not a part of savedObject attributes passed back from alerting, it's at the top level