Skip to content
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

Convert question to step-by-step fix instruction #34

Open
SergeyKanzhelev opened this issue Jan 23, 2017 · 2 comments
Open

Convert question to step-by-step fix instruction #34

SergeyKanzhelev opened this issue Jan 23, 2017 · 2 comments

Comments

@SergeyKanzhelev
Copy link
Collaborator

Let's not use

Try to understand and fix the issue. Hint: open web.config for frontend application and review the URL specified as HeaderUrl.

Instead just do step-by-step instruction how to fix it

@AlexBulankou
Copy link
Owner

Why? Step by step instruction would just tell them to open web.config and replace the HeaderUrl, but this gives them a chance to actually feel for yourself the benefit of AppInsights.

@SergeyKanzhelev
Copy link
Collaborator Author

It is nearly impossible for me to understand the issue looking at the map. Maybe instead "you see that response code is 404. It means that address is incorrect." Fairly speaking I'm lost in application map and what it shows myself

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants