Log (classic) ingest rule , host tag matcher attribute

[Yosi_Neuman]

Hi guys,

Struggle here with Log classic ingest rule Add condition and Matcher attribute of Host tag

We have tag on host 

But once adding the condition

logs are not collected any more 

What are we missing here ?

Yos 

[PedroSantos]

Hey Yos, did you manage to figure this out?
We're having a very similar problem where Dynatrace doesn't seem to be able to recognize the tags on a host properly and collect logs from there.

This is the rule I have for the environment and it does not work. The host absolutely has the tag:

But no logs are collected.


However, if I add the following rule to the host itself, the logs are collected:

I have no clue what's going on, since it should be working and had been working in the past. A "workaround" would be to add rules to each and every host individually, but that's a nightmare.

Am I using the wrong syntax or something?

[Yosi_Neuman]

Hi @PedroSantos 

Nope 🙃 still don't have solution for that 

Will open a support ticket for that later on and will update with the answer

Yos 

[PedroSantos · Accepted solution]

Hi @Yosi_Neuman 

I think we might have figured out something on our end. It seems that this might be the issue:

---

---

---

Matching is based on the host tag. The attribute only supports the tags set with the OneAgent command line tool or with the Remote configuration in a key=value pair format. They can be distinguished by the [Environment] prefix on the UI, but you should use the value without the prefix. Multiple tags can be specified in a single matcher, but each tag needs to have the same key, such as logscope=frontend, logscope=backend.

---

So, essentially, none of the tags we were using had the [Environment] prefix on the UI. Can you confirm this is the case on your end as well?

For this purpose, we can only use tags defined through the OneAgent command line tool or applied through the Remote Configuration. What this means is that we'll probably need to reapply tags to several hosts using these tools, and then it should work. From what I've gathered, it seems that tags not applied through these tools are not visible to the OneAgent (and are instead known by the SaaS), and that's why the OneAgents has no idea that the tags we're using are applied to their hosts.

[Yosi_Neuman]

Bravo @PedroSantos 

I read the documentation and saw the Remote configuration but did not understood that it means we need to go the deployment status page and set the tag from there 😱

Now, after setting the tag its work like a charm!  🤗

Thanks for your help ! 

All the best and stay safe

Yos