Hello, we would love to start backporting our SIgNoz alerts to our IaC using Terraform. Following your documentation in https://signoz.io/newsroom/launch-week-1-day-5/#introducing-access-token-management-in-signoz we would need to generate an access token to connect Terraform with our SigNoz instance.
We are using self-hosted SigNoz and are not able to generate an access token, is this behavior intended?
s
Srikanth Chekuri
11/01/2024, 4:51 AM
Hi @Matti, The token management is part of EE plan as of now.
Srikanth Chekuri
11/01/2024, 4:51 AM
You can use basic auth as well to manage the Terraform?
m
Matti
11/03/2024, 4:22 PM
I don't think the provider supports basic auth š
Copy code
Planning failed. Terraform encountered an error while generating this plan.
ā·
ā Error: Missing SigNoz access_token
ā
ā with provider["<http://registry.terraform.io/signoz/signoz|registry.terraform.io/signoz/signoz>"],
ā on <http://main.tf|main.tf> line 10, in provider "signoz":
ā 10: provider "signoz" {
ā
ā The provider cannot create the SigNoz API client as there is a missing or empty value for the SigNoz API access_token. Set the access_token value in the configuration or use the SIGNOZ_ACCESS_TOKEN environment variable. If either is
ā already set, ensure the value is not empty.
SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.