Skip to content
Should Tracetest invest time in adding scheduling and alerting?
1.
Should Tracetest invest time in adding scheduling and alerting
Yes - this is absolutely needed… yesterday!
No - we have our own tools for scheduling and alerting. We can trigger Tracetests from these.
Not yet - continue to focus on the core trace-based testing capabilities, and consider this later.
2.
What are you currently using for synthetic monitoring of your APIs?
3.
If Tracetest were going to add integrations or examples of working with CI/CD or test runner tools, which one should we focus on?
GitHub Actions
Tekton
Jenkins
Semaphore
Travis CI
GitLab CI
Other (please specify)
4.
What alerting tools do you use currently that you would like to see Tracetest support?
PagerDuty
Slack
Twilio
Zapier
Other (please specify)