Hello Brian
I hope you are doing well.
This behavior could be due to many causes. For example, in my case I have seen it when my expressway has problems communicating with the CSSM, which is normal. But on another occasion someone tried to do a SIP options from the default zone (which in our implementation has nothing to do with it) and that loopback came up. In general, what I want to tell you is that It can be either good or bad or normal (remember that these devices are back-2-back and communicate between interfaces).
Regardless of the type of implementation you have, whether MRA, B2B, registrar, it is always a very good practice to enable and configure Automated Detection and firewall rules (it is in system --> protection) along with call policies (configuration --> call policy), at least do it on the Edge expressway which is the one that faces the Internet.
Now regarding your case, as I mentioned before, it is difficult to know what it is. It would be a good idea to enable debugs for "traffic server": If it were up to me I would enable the following logs as debug:
network.http
network.http.edgeconfigprovisioning
network.http.trafficserver
You can do that in Maintenance--> Diagnostics --> Advanced --> Network log configuration. This is so you can see in more detail what is causing what you mention. What you are seeing right now at the INFO level does not give you much information. That is why you need to see more detail at the DEBUG level.
Then in Maintenance --> Diagnostics --> Diagnostic logging , take your captures.
I understand that your issue is repeated every second (even better if it is not random), so I think it will be easy to collect the logs and in a few seconds. Just don't forget to turn them to the default level (INFO) after you no longer use them.
I hope it helps.
Regards
