How do I report a Tares bug or ask for a connector it does not have yet?

Tares gives you three routes: email help@glassflow.ai, book a call, or open an issue on the GitHub repository. Use the GitHub issue for bugs and feature requests, including a connector you want added. The same routes cover questions about Tares Cloud, and they are all listed on the Help page.

How it works

Tares is built against real use cases, so reports and requests from people running it shape what ships next. The Help page lists three ways to reach the team, and each fits a different kind of message.

• Email: send a message to help@glassflow.ai. This works for anything: being stuck, a bug, a missing connector or feature, or a question about Tares Cloud.
• Book a call: pick a time at https://cal.com/ashishbagri/glassflow. This suits a conversation about your setup, a connector you need, or Tares Cloud.
• GitHub: open an issue at https://github.com/glassflow/tares/issues. This is the route for bugs and feature requests, and it keeps the report public so others can find it.

The team replies quickly on all three. If you are working through the AI SRE guides and hit something that does not behave as described, any of these routes gets it in front of the people who build Tares.

Set it up

Pick the route that matches what you need, then send enough detail for the team to act on it.

1. Decide the route. Use a GitHub issue for a bug or a feature request, such as a connector Tares does not have yet. Use email if you are stuck or want to ask something privately. Book a call if you would rather talk it through.
2. For a bug, note the Tares version you run. This command prints it:

tares --version

3. Describe what you did, what you expected and what happened instead. Add the connector or source involved if there is one.
4. For a connector request, name the system you want to connect, what data you want from it (alerts, logs, metrics, tickets) and how you would reach it today, for example a webhook or a polled API.
5. Send it. Open the issue at https://github.com/glassflow/tares/issues, email help@glassflow.ai, or book a slot at https://cal.com/ashishbagri/glassflow.
6. For a question about Tares Cloud, use email or a call. The Help page covers Tares Cloud questions alongside bugs and requests.

What you get

• A direct line to the team that builds Tares, with quick replies.
• A public record of your bug or feature request when you use a GitHub issue.
• A live conversation about your use case when you book a call.
• One place, the Help page, that lists every route for bugs, missing connectors, missing features and Tares Cloud questions.

When something else fits

• If the system you want has no connector, you may not need to wait. The webhook connector accepts arbitrary JSON posted to a Tares ingest URL, and the http_poll connector polls any JSON endpoint on a schedule. Still send the request so the team knows the demand.
• If you want to compare options or plan a rollout rather than report something, a call is a better fit than an issue.
• If your message contains details you do not want public, such as account or infrastructure information, use email instead of a GitHub issue.

Related