-
Notifications
You must be signed in to change notification settings - Fork 21.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The agent name is wrong and the agent address is really 'foo' #75260
Comments
Thanks for the feedback! I have assigned the issue to the content author to investigate this and update the document as appropriate. |
@DrEight could you please show us the logs that you're looking at that is showing the "foo" part that you're referring to. I reached out to our devs and was told no where in our code for the health probe does that name appears. Thank you. |
I don't have logs, I discovered the 'foo' agent attaching the debugger to the AppService behind the azure front door.
|
#reassign: jessie-jyy |
@DrEight I have forwarded your information to our Dev team and they were not able to find any related information in the health probe code named "foo". If you need further assistance on this matter, please open a service request with our support to further investigate this with you. Thank you for your contribution, for now I will be archiving this issue. #please-close |
[Enter feedback here]
In the documentation is specified the agent name as 'Edge Health Probes'. This is wrong the agent name is 'Edge Health Probe' without the S.
I also would say that the agent address is 'foo.mydomain.com' where foo is not a random name, but is really 'foo'.
This drove me crazy, because I thought it was in my code somewhere 'foo'. I wasted literally days.
It is a very bad idea to call an agent 'foo'.
So, please specify in the documentation that you have had a really bad idea, and the agent address is 'foo'
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: