You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hi there! I'm looking for an architectural diagram or detailed documentation that explains the roles of each service within OneUptime. For instance, how ClickHouse is used for telemetry and logging data, PostgreSQL for database management, and so forth. Having this kind of documentation would really help people understand the system better, leading to more effective pull requests, testing, and overall development.
Describe the solution you'd like
It would be fantastic to have a detailed deployment diagram or a System Architecture Document (SAD) that clearly outlines the structure and function of each component within OneUptime.
Describe alternatives you've considered
I tried to get a grasp of the system's structure by going through the code, but it would be much easier and more efficient to have a straightforward, high-level overview.
Thank you for considering this request and for all the hard work that goes into making OneUptime great. I believe that having this documentation will be a valuable resource for the community. Thanks again!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hi there! I'm looking for an architectural diagram or detailed documentation that explains the roles of each service within OneUptime. For instance, how ClickHouse is used for telemetry and logging data, PostgreSQL for database management, and so forth. Having this kind of documentation would really help people understand the system better, leading to more effective pull requests, testing, and overall development.
Describe the solution you'd like
It would be fantastic to have a detailed deployment diagram or a System Architecture Document (SAD) that clearly outlines the structure and function of each component within OneUptime.
Describe alternatives you've considered
I tried to get a grasp of the system's structure by going through the code, but it would be much easier and more efficient to have a straightforward, high-level overview.
Thank you for considering this request and for all the hard work that goes into making OneUptime great. I believe that having this documentation will be a valuable resource for the community. Thanks again!
The text was updated successfully, but these errors were encountered: