-
Notifications
You must be signed in to change notification settings - Fork 512
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
Updated diagrams on the architecture page #1459
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The arrows to/from "cache" should arguably go both ways, else LGTM.
Thank for you addressing my feedback from the other PR.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love it! The diagrams look good to me.
[not a blocker, can be done in a follow up PR] The diagrams in the deployment modes page still have the gray background. Can we remove the background from there too?
Same happen to me when I look at the raw file from github, but if I compile the website |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forgot to send my comment.
docs/sources/architecture/_index.md
Outdated
@@ -11,13 +11,9 @@ The system has multiple horizontally scalable microservices that can run separat | |||
Grafana Mimir microservices are called components. | |||
|
|||
Grafana Mimir's design compiles the code for all components into a single binary. | |||
The `-target` parameter controls which component that single binary will behave as. For those looking for a simple way to get started, Grafana Mimir can also be run as a monolith, with all components running simultaneously in one process. | |||
The `-target` parameter controls which component that single binary will behave as. For those looking for a simple way to get started, Grafana Mimir can also be run in monolithic mode, with all components running simultaneously in one process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is configured using -target=all
, should it be mentioned?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that is mentioned in the deployment-modes.md file so I'm going to leave it off. I add a link to that section of the docs under "monolithic mode"
docs/sources/architecture/_index.md
Outdated
@@ -11,13 +11,9 @@ The system has multiple horizontally scalable microservices that can run separat | |||
Grafana Mimir microservices are called components. | |||
|
|||
Grafana Mimir's design compiles the code for all components into a single binary. | |||
The `-target` parameter controls which component that single binary will behave as. For those looking for a simple way to get started, Grafana Mimir can also be run as a monolith, with all components running simultaneously in one process. | |||
The `-target` parameter controls which component that single binary will behave as. For those looking for a simple way to get started, Grafana Mimir can also be run in monolithic mode, with all components running simultaneously in one process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
-target
parameter controls which componentS ...
I'd use plural, as it is possible to use -target=compactor,ingester
for example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I will updated to component(s)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just left some minor feedback. Looks good!
docs/sources/architecture/_index.md
Outdated
@@ -11,13 +11,9 @@ The system has multiple horizontally scalable microservices that can run separat | |||
Grafana Mimir microservices are called components. | |||
|
|||
Grafana Mimir's design compiles the code for all components into a single binary. | |||
The `-target` parameter controls which component that single binary will behave as. For those looking for a simple way to get started, Grafana Mimir can also be run as a monolith, with all components running simultaneously in one process. | |||
The `-target` parameter controls which component that single binary will behave as. For those looking for a simple way to get started, Grafana Mimir can also be run in monolithic mode, with all components running simultaneously in one process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The `-target` parameter controls which component that single binary will behave as. For those looking for a simple way to get started, Grafana Mimir can also be run in monolithic mode, with all components running simultaneously in one process. | |
The `-target` parameter controls which components that single binary will behave as. For those looking for a simple way to get started in a development environment, Grafana Mimir can also be run in monolithic mode by setting `-target=all`. This will run the minimally required components in one process. |
Just clarified that monolithic mode is for development only and it technically doesn't run everything, just the minimally necessary components.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just clarified that monolithic mode is for development only and it technically doesn't run everything, just the minimally necessary components.
I don't think that's true. It's not for development only, and it actually runs most of the components. Notably missing is alertmanager, but it's easy to enable it as well. (-target=all,alertmanager).
While it's not recommended for production, because it's easier to control resources of individual components, it's absolutely possible to use Mimir that way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough, I was thinking of this from a support perspective at Grafana Labs, but you're right that it can work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pstibrany @Logiraptor we already have some of this information in deployment-modes.md file so I'm going to leave it off.
@pstibrany changed all the arrows to be black and updated the cache to be the same color as the object store to help improve readability. Lemme know if you think its good to go. |
@pracucci - I think this might be related to your relref observation/proposal for how to rework things but I see that the diagram on the ruler.md page renders correctly when I run |
Right now, due to how URLs are built in grafana.com website, either we make it work for GitHub or grafana.com. We obviously need images working in grafana.com so we start prioritizing them. At the moment, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
66c9062
to
a3f56a5
Compare
…iagram. Adding ruler diagram.
Signed-off-by: Marco Pracucci <marco@pracucci.com>
a3f56a5
to
e0dc3ee
Compare
I rebased and fixed conflicts. |
* Refreshing read and write diagrams and removing parent architecture diagram. Adding ruler diagram. * Moved images Signed-off-by: Marco Pracucci <marco@pracucci.com> Co-authored-by: Marco Pracucci <marco@pracucci.com>
Removed the diagram at the top of the architecture page, since we have almost the same diagram on the deployment-modes.md page under the 'microservices' header.
Replaced the read and write diagrams with svg files (formerly png) for higher resolution. Changed the background to white since @pstibrany pointed out it improves the contrast.
For the read diagram, I added a bubble to represent the caches, with the caches labeled as optional.
Since we have no overall architecture diagram which shows the ruler (the one on deployment-modes.md excludes the optional components), I added a ruler specific diagram to the ruler.md page.
All diagrams come from here:
https://docs.google.com/presentation/d/1LemaTVqa4Lf_tpql060vVoDGXrthp-Pie_SQL7qwHjc/edit
Fixes #1192 and replaces #1360