mDNS results in esp_netif_lwip log spam (IDFGH-12320)

[malachib]

Answers checklist.

• [X] I have read the documentation for esp-protocols components and the issue is not addressed there.
• [X] I have updated my esp-protocols branch (master or release) to the latest version and checked that the issue is present there.
• [X] I have searched the issue tracker for a similar issue and not found a similar issue.

What component are you using? If you choose Other, provide details in More Information.

mDNS

component version

1.2.5

IDF version.

v5.1.3

More Information.

mDNS works as well as ever, but I get a nonstop spam in my logs now:

D (11011) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbf558
D (11221) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbf558
D (11321) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbf558
D (11421) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbf558
D (12041) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbf558
D (12241) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbf558
D (12341) esp_netif_lwip: esp_netif_get_ip_info esp_netif:0x3ffbf558

Not exactly a bug, but perhaps indicative of an issue? It certainly interferes with my log evaluations

[david-cermak]

Hi @malachib

The log says that the mDNS library check IPs addresses of related network interfaces, but I agree that the debug level is probably too verbose for logging an API entry -- will change to verbose.

It certainly interferes with my log evaluations

You can update logging levels of certain components/TAGs using esp_log_level_set()

For example this:

    esp_log_level_set("esp_netif_lwip", ESP_LOG_INFO);

would move the abovementioned logs to the info level.