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

Traffic manager monitoring should support expected http status codes #431

Open
Nothing4You opened this issue Feb 19, 2021 · 2 comments · May be fixed by #1800
Open

Traffic manager monitoring should support expected http status codes #431

Nothing4You opened this issue Feb 19, 2021 · 2 comments · May be fixed by #1800
Labels
has_pr PR fixes have been made medium_priority Medium priority new_feature New feature requirments

Comments

@Nothing4You
Copy link

SUMMARY

Currently the following settings are not available on azure_rm_trafficmanager:

  • Custom header settings
  • Expected status code ranges
ISSUE TYPE
  • Feature Idea
COMPONENT NAME

azure_rm_trafficmanager

ADDITIONAL INFORMATION

https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-monitoring

Expected status code ranges. This setting allows you to specify multiple success code ranges in the format 200-299, 301-301. If these status codes are received as response from an endpoint when a health check is done, Traffic Manager marks those endpoints as healthy. You can specify a maximum of eight status code ranges. This setting is applicable only to HTTP and HTTPS protocol and to all endpoints. This setting is at the Traffic Manager profile level and by default the value 200 is defined as the success status code.

Probing interval. This value specifies how often an endpoint is checked for its health from a Traffic Manager probing agent. You can specify two values here: 30 seconds (normal probing) and 10 seconds (fast probing). If no values are provided, the profile sets to a default value of 30 seconds.

@rafaelarcanjo
Copy link

Please. I need it!

@Fred-sun Fred-sun added has_pr PR fixes have been made medium_priority Medium priority new_feature New feature requirments labels Jan 9, 2025
@Fred-sun
Copy link
Collaborator

Fred-sun commented Jan 9, 2025

Added in #1800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has_pr PR fixes have been made medium_priority Medium priority new_feature New feature requirments
Projects
None yet
3 participants