cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Set custom log sources globally but not have them shown

A1
Observer

Hello,

   Is there a way that when i set a custom log source path at the environment level to not have it show under log sources that it does not exist on the hosts that do not have that path.  In some cases I would like to set this at the environment and not at the host group but don't want that message to show on hosts that don't have the path.  For example, if i set at the environment level a custom sql log path it will get picked up by all that have it but for the ones that don't I do not want that message to show because as I would add more rules that list will just keep growing and I would like to avoid that.

Thanks

1 REPLY 1

PedroSantos
Helper

I don't think there is a built-in way to ignore environment set log paths on specific machines directly.

What you can do instead is make use of Host Groups. Dynatrace allows you to set up custom log sources at Host, Host Group and Environment level.

You could evaluate whether it makes sense to have a custom sql path set up for all machines at environment level, or if you should instead make use of a Host Group for those machines and define the custom log source at Host Group level.

Alternatively, you could try to make use of the Include/Exclude functionality in Log Ingestion Rules to filter out paths that do not match your needs (like log paths that don't exist on specific hosts). These can help you manage what gets ingested and doesn't. However, as your system grows in complexity, they could become a real problem to manage if set up like this for this purpose. I would only do this after ensuring the Custom Log Sources rules defined at Host, Host Group and Environment levels are bullet proof. Because if they are this should mitigate a large part of the problem (at least) by itself.

To make an error is human. To spread the error across all servers in an automated way is DevOps.

Featured Posts