Thank you for the suggestion.
Not sure that useful there. And it might be pretty noisy if you add tags from host and templates here.
Probably I agree that filter should work by tags, which isn't now.
So it seems there is some context, Tags of items and tags of templates and host, latest more general and hardly will be contain some CPU related tags. It more about location or some application or cluster .

Actually, I was thinking about the noise and I agree with you. If we use a lot of tags, it's going to create a lot of noise and actually disturb usability. On the other hand, if these tags exsist why don't we see them? It might be confusing.

Perhaps a selector with "Show inherited tags" here could help with that. Depending on the environment, it might be a useful adition.

Just putting it out there for community consideration

I vote the Nathan idea of "Show inherited tags" but we need to see all the Tag if needed.

I think ZBXNEXT-7665 is related ?

Personally I think template inherited tags should always be visible and selectable for filtering in Latest data, so one can easily filter on the inherited template tag "target". I don't think that would produce that much noise if one follows the Zabbix templating guides? And as templates mostly cover only a single application/service this would in some sense replace the old "Application" (I initially thought that was the intention with the 'target'-tag introduced in the new templating guidelines. So not finding these inherited tags on Latest Data already was confusing for me.)

When latest data of several hosts is displayed instead of for a single host, host inherited tags should (possibly optional) also be displayed and selectable for filtering.