Add saved object tags to integrations with Kibana saved objects

[alexfrancoeur]

The Kibana team (well, @pgayvallet 😉) has a PR for saved object tagging targeted for 7.11 that is currently under review (elastic/kibana#79096). This is the MVP and we plan to iterate. That being said, I think there is an opportunity to update any packages with Kibana saved object tags in the same release. I realize the registry is not release based, but it'd be a nice announcement to go along with user generated tags 😄

Next up that's related to this effort, I plan to start up discussions with the team on elastic/kibana#70461

cc: @ruflin @mostlyjason @tbragin @kobelb @joshdover

[ruflin]

Mentioning @andresrc as he will drive the updates of integrations. I assume it means, any visualization / dashboard etc. where we will start using tags, will be only compatible with KB 7.11, means the package itself is probably only compatible with 7.11. No problem with that, just wanted to make sure compatibility is clear.

[tbragin]

@alexfrancoeur this is great news! +1 on automatically applying tags for the dashboards we ship with integrations. Thank you for starting this conversation ❤️

cc @sorantis @mukeshelastic from observability integrations
cc @jamiehynds @hmnichols from security integrations

[alexfrancoeur]

As a quick update to this group, @pgayvallet has officially merged tags with out of the box support for dashboards and visualizations. We'll be discussing what additional improvements we can make for 7.11 (elastic/kibana#81980), but the functionality is now available.

[ruflin]

@andresrc We should start to create a guideline on how we use the tags inside the packages

[bradenlpreston]

@jamiehynds and @epixa in the event we want to update any packages related to security.

[nreese]

Tags added to maps with elastic/kibana#83197

[alexfrancoeur]

Hey all, I wanted to provide a quick update around tags for 7.11.

There has been some significant (and amazing) progress from @pgayvallet, @ryankeairns and team to support a global experience for tag usage.

We now have search syntax to filter down results by type and tag elastic/kibana#83422
Tags are now a suggested filter from our navigational search elastic/kibana#85144
To support this even more, we'll soon surface tags in search results with saved objects that have them elastic/kibana#85084
Users can now manage tags in bulk across supported saved objects elastic/kibana#84177

This significantly increases discoverability and streamlines navigation of Kibana assets packaged with integrations.

Have we come to a consensus on guidelines for integrations? If so, do we think that integrations will add support for tags in 7.11? I also believe that integrations are not bound by release, so maybe it's possible to iterate here.

[tbragin]

@mukeshelastic @sorantis @andresrc @mostlyjason @jamiehynds @ruflin @ph I'd love your perspective here.

As you may recall, we asked the Kibana team to prioritize tags, so we have a mechanism to organize assets we are installing with modules and integrations. Do we already have a plan in place to leverage them? I know it's been discussed, but not sure where we ended up.

[ruflin]

My suggestion is we start simple with 2 tags:

• integrations name tag on all assets from an integration
• managed tag on all the assets to indicated that they are managed by us. Alternative we could add a fleet tag to indicate that they are managed by fleet.

[sorantis]

We discussed the possibility to use tags as a mechanism to automatically expose integrations' assets in the UI. For example we could automatically add a link to a dashboard based on a tag matching service/integration name on a host's or container's details page. This actually aligns with @ruflin's first suggestion.

[ph]

@ruflin what you are proposing is to thave theses tags hardcoded at install time? The second steps would be to allow dev author to define more tags?