[EPM] Store map visualizations from the package registry and use saved object ID#62059
Conversation
|
Pinging @elastic/ingest-management (Feature:EPM) |
| 'index-pattern': 'indexPatternApp', | ||
| search: 'searchProfilerApp', | ||
| visualization: 'visualizeApp', | ||
| map: 'mapApp', |
There was a problem hiding this comment.
Not sure if these need to be actual names of icons or something? @jen-huang @neptunian @jfsiii
There was a problem hiding this comment.
I believe this is only used in the AssetsFacetGroup component to get the icon. We have a prototype of an assets section in the package detail page, but its been pushed back for a while as its not really important. so you can keep this and when we bring it back, we'll fix it if its not working.
There was a problem hiding this comment.
Ah ok, thanks Sandra!
|
@jonathan-buttner Can you include instructions for how to test this? |
| const savedObject: SavedObjectToBe = { | ||
| type, | ||
| id: file.replace('.json', ''), | ||
| id: asset.id, |
There was a problem hiding this comment.
IIRC, EPM initially stored the ID given by the registry/package. However, IIRC, it was removed because we couldn't count on it(upgrades?). I believe we were going to have EPM maintain a mapping(?).
/cc @ruflin @skh @neptunian
I guess we can add this now and fix the broken case you show, then deal with the other issues if/when they show up.
There was a problem hiding this comment.
My long term preference would be that we use our "own" ids to make sure we don't conflict with other assets and keep a list.
+1 on adding this now to make it work and figure out the exact renaming.
@skh @neptunian Your input on where we are standing here would be great.
There was a problem hiding this comment.
|
@jonathan-buttner Thanks for taking this on. This will close #60353 |
Yeah sorry about that I'll add some instructions. |
|
@elasticmachine merge upstream |
|
Pinging @elastic/endpoint-app-team (Feature:Endpoint) |
|
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
| 'index-pattern': 'indexPatternApp', | ||
| search: 'searchProfilerApp', | ||
| visualization: 'visualizeApp', | ||
| map: 'mapApp', |
There was a problem hiding this comment.
I believe this is only used in the AssetsFacetGroup component to get the icon. We have a prototype of an assets section in the package detail page, but its been pushed back for a while as its not really important. so you can keep this and when we bring it back, we'll fix it if its not working.
* master: [APM] Change custom link from EuiListGroupItem to EuiLink (elastic#62742) [Remote Clusters] Update callout and move server_name field (elastic#62352) Removes Pitch Presentation Template from Canvas (elastic#62688) FTR: Enable w3c for chromedriver (elastic#62542) [ML] Disable functional tests [ILM] Skip failing API integration test (elastic#62779) [SIEM] Update beat doc (elastic#61902) [Search] Properly add slash preceding path in async search (elastic#62722) [APM] make sure environment query is correct for service maps… (elastic#62764) Add service map icon for rum-js agent type (elastic#62721) [APM] Service map - fixes irrelevant services on data refresh (elastic#62750) [APM] Service map - Fix taxi edge arrow orientation (elastic#62741) [APM] Prevent error rate alert trigger from rendering NaN (elastic#62754) [EPM] Store map visualizations from the package registry and use saved object ID (elastic#62059) [Alerting] for email action, set tls.rejectUnauthorized: false when secure: false (elastic#62380)
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
…d object ID (#62059) (#63146) * Using saved objects id instead of creating one * Adding map to list of types * Fixing typing errors * Reverting id change * Reverting asset id Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
## PR Summary Show [`emsApp` icon from EUI](https://eui.elastic.co/#/display/icons#apps) if integration includes map assets. <img width="229" alt="Screen Shot 2021-01-12 at 3 14 14 PM" src="https://user-images.githubusercontent.com/57655/104367878-65628280-54e9-11eb-8d9c-fa838e2c15ae.png"> Looking at #62059 (comment), I believe it landed with the incorrect key at a time when that part of the page wasn't visible. When we enabled that section, we likely didn't notice the missing key since most integrations don't have Maps assets ## Bug: `master` doesn't have an icon for Map assets 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16 2. Observe missing icon for Map in right column summary & HTTP request for `/app/mapApp` <img width="1013" alt="Screen Shot 2021-01-12 at 3 10 44 PM" src="https://user-images.githubusercontent.com/57655/104367875-64c9ec00-54e9-11eb-81d8-982bec862f5f.png"> ## This PR adds one 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16 2. Observe EMS icon is present in right column summary <img width="1087" alt="Screen Shot 2021-01-12 at 3 11 39 PM" src="https://user-images.githubusercontent.com/57655/104367877-65628280-54e9-11eb-91da-578fec6ff769.png">
## PR Summary Show [`emsApp` icon from EUI](https://eui.elastic.co/#/display/icons#apps) if integration includes map assets. <img width="229" alt="Screen Shot 2021-01-12 at 3 14 14 PM" src="https://user-images.githubusercontent.com/57655/104367878-65628280-54e9-11eb-8d9c-fa838e2c15ae.png"> Looking at #62059 (comment), I believe it landed with the incorrect key at a time when that part of the page wasn't visible. When we enabled that section, we likely didn't notice the missing key since most integrations don't have Maps assets ## Bug: `master` doesn't have an icon for Map assets 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16 2. Observe missing icon for Map in right column summary & HTTP request for `/app/mapApp` <img width="1013" alt="Screen Shot 2021-01-12 at 3 10 44 PM" src="https://user-images.githubusercontent.com/57655/104367875-64c9ec00-54e9-11eb-81d8-982bec862f5f.png"> ## This PR adds one 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16 2. Observe EMS icon is present in right column summary <img width="1087" alt="Screen Shot 2021-01-12 at 3 11 39 PM" src="https://user-images.githubusercontent.com/57655/104367877-65628280-54e9-11eb-91da-578fec6ff769.png">
## PR Summary Show [`emsApp` icon from EUI](https://eui.elastic.co/#/display/icons#apps) if integration includes map assets. <img width="229" alt="Screen Shot 2021-01-12 at 3 14 14 PM" src="https://user-images.githubusercontent.com/57655/104367878-65628280-54e9-11eb-8d9c-fa838e2c15ae.png"> Looking at #62059 (comment), I believe it landed with the incorrect key at a time when that part of the page wasn't visible. When we enabled that section, we likely didn't notice the missing key since most integrations don't have Maps assets ## Bug: `master` doesn't have an icon for Map assets 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16 2. Observe missing icon for Map in right column summary & HTTP request for `/app/mapApp` <img width="1013" alt="Screen Shot 2021-01-12 at 3 10 44 PM" src="https://user-images.githubusercontent.com/57655/104367875-64c9ec00-54e9-11eb-81d8-982bec862f5f.png"> ## This PR adds one 1. Visit an integration with map assets, like AWS http://localhost:5601/app/fleet#/integrations/detail/aws-0.3.16 2. Observe EMS icon is present in right column summary <img width="1087" alt="Screen Shot 2021-01-12 at 3 11 39 PM" src="https://user-images.githubusercontent.com/57655/104367877-65628280-54e9-11eb-91da-578fec6ff769.png">
This PR adds maps to the types of kibana assets that can be created from a package.
Example map working
Testing
To test this change:
Kibana may crash because of the ingest pipeline within the okta package (this is happing on master without my change as well), this is what was happening to me
The dashboard and map should still be installed even though kibana crashed.
3. Restart Kibana but not ES
4. Go to the dashboard page
5. Open the
[Filebeat Okta] Overviewdashboard6. See that the map is now in the dashboard
With the change
Without this change