You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR is a POC for the content management "metadata events".
Goal
We want to add a new sorting capability to the saved object list view tables to help our users quickly find the content they are looking for. We want to be able to sort by “Total views” (ASC and DESC) and also “Total views in the last 30 / 15 / 7 days” (ASC and DESC).
In this PR I demo how we could add views counters (for last "7_days", "14_days", ...) and be able to sort the Dashboard list view table with those counters.
How to test
Add the sample data (this will add 3 dashboards)
Navigate to the dashboard list view. There should be a column with the view count + a drop down in the table header to change the granularity of the counts
Click a dashboard to view it and go back to the dashboard list. Its counter should now be 1
In order to test the granularity we need to manually add an event in the past. In a terminal send the following curl command (note: set the correct url of your local dev Kibana)
curl -X "POST" "http://localhost:5601/<unique>/api/user_content/event/viewed:kibana" \
-H 'kbn-xsrf: kibana' \
-H 'Content-Type: application/json; charset=utf-8' \
-u 'elastic:changeme' \
-d $'{
"@timestamp": "2022-05-15T10:00:00.000Z", # change this date if needed
"soId": "1bcfb990-d859-11ec-8a6b-b125ca46a567", # change if needed
"soType": "dashboard"
}'
You should now have an event in the past and be able to test the other granularity ("30 days", "45 days"...)
The reason will be displayed to describe this comment to others. Learn more.
I am not sure why we have duplicate mappings definition with the server. This would probably need to be refactored to have a single mappings declaration
[job][logs] Jest Tests #3 / after fetch initialFilter
[job][logs] Jest Tests #3 / after fetch renders all table rows
[job][logs] Jest Tests #3 / after fetch renders call to action when no dashboards exist
[job][logs] Jest Tests #3 / after fetch renders call to action with continue when no dashboards exist but one is in progress
[job][logs] Jest Tests #3 / after fetch renders warning when listingLimit is exceeded
[job][logs] Jest Tests #3 / after fetch showWriteControls
[job][logs] Jest Tests #3 / after fetch When given a title that matches multiple dashboards, filter on the title
[job][logs] FTR Configs #5 / analytics analytics service analytics service: public side should see both events enqueued and sent to the shipper
[job][logs] FTR Configs #5 / analytics analytics service analytics service: public side should see both events enqueued and sent to the shipper
[job][logs] FTR Configs #26 / apis saved_objects _bulk_create should return 200 with individual responses
[job][logs] FTR Configs #26 / apis saved_objects _bulk_create should return 200 with individual responses
[job][logs] Jest Integration Tests #1 / Fleet preconfiguration reset Preconfigured cloud policy Adding APM to a preconfigured agent policy after first setup Create a .fleet-policies document with the APM package policy
[job][logs] Jest Integration Tests #1 / Fleet preconfiguration reset Preconfigured cloud policy Adding APM to a preconfigured agent policy after first setup Create correct package policies
[job][logs] Jest Integration Tests #1 / Fleet preconfiguration reset Preconfigured cloud policy Adding APM to a preconfigured agent policy after first setup Works and preconfigure correctly agent policies
[job][logs] Jest Integration Tests #1 / Fleet preconfiguration reset Preconfigured cloud policy Adding package policy id to a preconfigured package policy after first setup Create correct package policies and use the name of package policies instead of id
[job][logs] Jest Integration Tests #1 / Fleet preconfiguration reset Preconfigured cloud policy Adding package policy id to a preconfigured package policy after first setup Works and preconfigure correctly agent policies
[job][logs] Jest Integration Tests #1 / Fleet setup preconfiguration with multiple instances Kibana preconfiguration setup sets up Fleet correctly when multiple Kibana instaces are started in serial
[job][logs] Jest Integration Tests #1 / Fleet setup preconfiguration with multiple instances Kibana preconfiguration setup sets up Fleet correctly when multiple Kibana instances are started at the same time
[job][logs] Jest Tests #6 / SavedObjectsClient #create makes HTTP call with ID
[job][logs] Jest Tests #6 / SavedObjectsClient #create makes HTTP call without ID
[job][logs] Jest Tests #6 / SavedObjectsService #setup() #addClientWrapper registers the wrapper to the clientProvider
[job][logs] Jest Tests #6 / SavedObjectsService #setup() #getTypeRegistry returns the internal type registry of the service
[job][logs] Jest Tests #6 / SavedObjectsService #setup() #registerType registers the type to the internal typeRegistry
[job][logs] Jest Tests #6 / SavedObjectsService #setup() #setClientFactoryProvider registers the factory to the clientProvider
[job][logs] Jest Tests #6 / SavedObjectsService #setup() #setClientFactoryProvider throws if a factory is already registered
[job][logs] Jest Tests #6 / SavedObjectsService #setup() calls registerRoutes with the correct kibanaVersion
[job][logs] Jest Tests #6 / SavedObjectsService #setup() register the deprecation provider
[job][logs] Jest Tests #6 / SavedObjectsService #setup() registers the deprecation provider with the correct kibanaVersion
[job][logs] Jest Tests #6 / SavedObjectsService #start() #createInternalRepository creates a repository using the admin user
[job][logs] Jest Tests #6 / SavedObjectsService #start() #createScopedRepository creates a repository including hidden types when specified
[job][logs] Jest Tests #6 / SavedObjectsService #start() #createScopedRepository creates a repository scoped to the user
[job][logs] Jest Tests #6 / SavedObjectsService #start() #getTypeRegistry returns the internal type registry of the service
[job][logs] Jest Tests #6 / SavedObjectsService #start() calls KibanaMigrator with correct version
[job][logs] Jest Tests #6 / SavedObjectsService #start() resolves with KibanaMigrator after waiting for migrations to complete
[job][logs] Jest Tests #6 / SavedObjectsService #start() skips KibanaMigrator migrations when migrations.skip=true
[job][logs] Jest Tests #6 / SavedObjectsService #start() skips KibanaMigrator migrations when pluginsInitialized=false
[job][logs] Jest Tests #6 / SavedObjectsService #start() throws when calling setup APIs once started
[job][logs] Jest Tests #6 / SavedObjectsService #start() waits for all es nodes to be compatible before running migrations
[job][logs] Jest Tests #4 / TableListView render list view
[job][logs] Jest Integration Tests #2 / trace execution context does not affect "x-opaque-id" set by user
[job][logs] Jest Integration Tests #2 / trace execution context does not break on non-ASCII characters within execution context
[job][logs] Jest Integration Tests #2 / trace execution context execution context is the same for all the lifecycle events
[job][logs] Jest Integration Tests #2 / trace execution context execution context is uniq for concurrent requests
[job][logs] Jest Integration Tests #2 / trace execution context execution context is uniq for concurrent requests when "x-opaque-id" provided
[job][logs] Jest Integration Tests #2 / trace execution context execution context is uniq for sequential requests
[job][logs] Jest Integration Tests #2 / trace execution context parses the parent context if present
[job][logs] Jest Integration Tests #2 / trace execution context passes "x-opaque-id" if no execution context is registered
[job][logs] Jest Integration Tests #2 / trace execution context propagates context to Elasticsearch scoped client
[job][logs] Jest Integration Tests #2 / trace execution context propagates context to Elasticsearch unscoped client
[job][logs] Jest Integration Tests #2 / trace execution context sets execution context for a sync request handler
[job][logs] Jest Integration Tests #2 / trace execution context sets execution context for an async request handler
[job][logs] Jest Integration Tests #2 / trace execution context withContext sets execution context for a nested function
[job][logs] Jest Integration Tests #2 / trace x-opaque-id can be overridden during Elasticsearch client call
[job][logs] Jest Integration Tests #2 / trace x-opaque-id ExecutionContext Service is disabled does not pass context if ExecutionContext Service is disabled
[job][logs] Jest Integration Tests #2 / trace x-opaque-id ExecutionContext Service is disabled passed to Elasticsearch scoped client calls even if ExecutionContext Service is disabled
[job][logs] Jest Integration Tests #2 / trace x-opaque-id generated and attached to Elasticsearch scoped client calls if not specifed
[job][logs] Jest Integration Tests #2 / trace x-opaque-id generated and attached to Elasticsearch unscoped client calls if not specifed
[job][logs] Jest Integration Tests #2 / trace x-opaque-id passed to Elasticsearch scoped client calls
Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.
Total count of every any typed public API. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats any for more detailed information.
Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is a POC for the content management "metadata events".
Goal
We want to add a new sorting capability to the saved object list view tables to help our users quickly find the content they are looking for. We want to be able to sort by “Total views” (ASC and DESC) and also “Total views in the last 30 / 15 / 7 days” (ASC and DESC).
In this PR I demo how we could add views counters (for last "7_days", "14_days", ...) and be able to sort the Dashboard list view table with those counters.
How to test
1
In order to test the granularity we need to manually add an event in the past. In a terminal send the following curl command (note: set the correct url of your local dev Kibana)
You should now have an event in the past and be able to test the other granularity ("30 days", "45 days"...)
Issue related: #9202