Hello,
We plan to use your Terraform provider (registry.terraform.io/providers/site24x7/site24x7/latest) to deploy a large number of monitors, however there are some limitations with the provider currently which prevent us from doing so.
Could you please add functionality for the following:
- Configuring 'Should contain HTTP Response Header(s)' in website_monitor and rest_api_monitor resources
- Configuring tags in any resource configurable through the provider
- Configuring 'Third-party Integrations' in any monitor resources
- Specifying threshold/notification/user alert configuration by friendly name rather than uid, or a data provider to pull these in. Currently, these need to be retrieved from the UI or through the API.
- Configuring 'Rest API Transaction' monitors, and configuring the transaction steps within this monitor.
Thanks
Dear Brendan,
Thank you for raising it here. We are working on some of the features you've requested already (tags and 3rd party).
Since the provider is open source and in GitHub, we encourage you to contribute to some of the enhancements you've mentioned if you can (Others too can start contributing). The provider itself is being enhanced constantly by our team; however, we would be happy to accept your pull requests (Additional help is always welcome).
You can also raise these requests as issues in GitHub for more visibility and community contribution (We already have some requests and are working on them).
-Jasper
Site24x7, PM
Dear Brendan,
Please use the latest version(0.0.1-beta.6) of our terraform provider to configure third party services to resources.
Example:
// (Optional) List of Third Party Service IDs to be associated to the monitor.
third_party_service_ids = [
"4567"
]
Thanks & Regards,
Jim
Hi, do you have option to configure schedule maintenance of monitors.
I wonder why you want to do this with Terraform and not using the site24x7 API.
You "build" with terraform. But don't "operate".
This isn't my question but this might be an example...
There's a scheduled pipeline that uses a terraform template to generate a new Letsencrypt certificate and then install it on an endpoint. You may want to have that same terraform first schedule a maintenance window before it does it's thing. :shrug: Obviously many ways to skin a cat but seems like a valid feature request.