[Fleet] Dashboards and visualizations are not clearly labeled to distinguish from Beats

[mostlyjason]

The dashboards and visualizations created by packages for Elastic Agent are not clearly labeled to distinguish them from Beats. This is confusing when the system package is installed by default even when the user is not using Elastic Agent. The user may accidentally click on one of the Elastic Agent dasbhoards mistakenly thinking they are for Beats, and there will be no data visible. Also, it will appear to using the incorrect index pattern. We have gotten a support request for this and it may be confusing to other users as well.

To address this confusion, we should clearly label the dashboards and visualizations for Elastic Agent. This could be done via a tags on saved objects, if tags are displayed on the dashboard and visualization selector page. Alternatively, they could include "Elastic Agent" in the title of the asset.

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[elasticmachine]

Pinging @elastic/fleet (Feature:Fleet)

[mostlyjason]

@sorantis @masci See the related support issue that describes the confusion.

[mostlyjason]

@masci sorry I accidentally tagged this as ingest management team, but I think its integrations team. Can you check if it synced correctly to your tracking system?

[elasticmachine]

Pinging @elastic/integrations-services (Team:Services)

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[elasticmachine]

Pinging @elastic/integrations (Team:Platforms)

[sorantis]

Moved the issue to beats repo.

[ruflin]

I wonder if we need to a second issue in the integrations repo. In the best case, Beats and Integrations both add labels to distinguish between the two.

[mostlyjason]

@sorantis where is the best place to track/discuss this issue? For integrations, it seems like we could add labels as part of our development guidelines? https://github.com/elastic/obs-dc-team/blob/master/development/generic_guidelines.md. If you agree I'd be happy to open a PR.

[sorantis]

@mostlyjason We can add the to the generic guidelines or preferably to the dashboard guidelines. Thanks!

[mostlyjason]

Moved this discussion to the integrations repo, so closing this one