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

Offer multiple modes of Tobs installation #473

Open
VineethReddy02 opened this issue Jul 7, 2022 · 3 comments
Open

Offer multiple modes of Tobs installation #473

VineethReddy02 opened this issue Jul 7, 2022 · 3 comments
Labels
documentation Improvements or additions to documentation epic/tobs-production-readiness

Comments

@VineethReddy02
Copy link
Contributor

VineethReddy02 commented Jul 7, 2022

We see users coming from different contexts based on their existing state of Observability. This is a feature request to easily integrate tobs with their existing setup. Listing down the possible scenarios that users might be interested in onboarding with Tobs:

  • Getting started with the entire Observability stack i.e. evaluating, and testing the stack. (with production best practices i.e without HA.)
  • Production grade installation for the entire stack. (This is the default that already exists in Tobs)
  • Integrating to existing Prometheus stack.
  • Integrating to existing OpenTelemetry or Jaeger stack.
  • Integrating Observability stack with Timescale cloud for offloading the storage to cloud.
  • Hub-and-spoke architecture, to run the instrumentation layer of tobs in spoke clusters and run Promscale layer in hub cluster. (added in edit 1)

What is missing?
Easy way of integrating tobs with the existing setup and running tobs for testing and evaluating.

Why do we need it?
To offer an easy getting started modes of installation with Tobs.

Anything else we need to know?:
This will definitely help users to easily get started and integrate as per their requirements.

@VineethReddy02 VineethReddy02 added the feature New features label Jul 7, 2022
@paulfantom
Copy link
Contributor

with production best practices i.e without HA.

Lack of HA is violating production best practices. Instead we can offer "developer" version which is not having HA and can be used for testing, but it won't have "production best practices".

@VineethReddy02
Copy link
Contributor Author

yup, that's the requirement for testing and evaluating the stack.

@VineethReddy02
Copy link
Contributor Author

#498 feels like a duplicate of this issue. Supporting all modes of installation covers hub-and-spoke deployments, as mentioned in the issue description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation epic/tobs-production-readiness
Projects
None yet
Development

No branches or pull requests

2 participants