Add blogpost on "monitoring FerretDB performance using Coroot" #4279
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Marketing blog posts should be reviewed by @ptrfarkas and @AlekSi. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4279 +/- ##
==========================================
- Coverage 75.26% 74.76% -0.50%
==========================================
Files 326 326
Lines 22471 22471
==========================================
- Hits 16913 16801 -112
- Misses 4337 4436 +99
- Partials 1221 1234 +13 see 22 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
AlekSi
requested changes
May 14, 2024
Comment on lines
13
to
19
| Effective real-time monitoring is a critical aspect of any infrastructure. | ||
| [Coroot](https://coroot.com/) is an open source observability platform that can provide real-time monitoring and visibility into a [FerretDB](https://www.ferretdb.com/) setup. | ||
|
|
||
| <!--truncate--> | ||
|
|
||
| Effective real-time monitoring is a critical aspect of any infrastructure. | ||
| [Coroot](https://coroot.com/) is an open source observability platform that can provide real-time monitoring and visibility into a [FerretDB](https://www.ferretdb.com/) setup. |
| ## Setting up Coroot for FerretDB monitoring | ||
|
|
||
| Since Coroot uses eBPF, you need the right environment before setting it up. | ||
| The most recent versions of the Linux kernel (v 4.16 and above) should be compatible since they offer at least minimal eBPF support. |
There was a problem hiding this comment.
Suggested change
| The most recent versions of the Linux kernel (v 4.16 and above) should be compatible since they offer at least minimal eBPF support. | |
| The most recent versions of the Linux kernel (v4.16 and above) should be compatible since they offer at least minimal eBPF support. |
Comment on lines
137
to
140
| The Coroot dashboard provides the full details on all components. | ||
|
|
||
| At first glance, we can see a memory leak on the `ferretdb` and `postgres` databases. | ||
| That suggests that allocated memory is not being efficiently reused or deallocated, causing the total memory usage to grow progressively as the services operate. |
There was a problem hiding this comment.
… so we want to publish a blog post that casually mentions that FerretDB and PostgreSQL have memory leaks just like that?
Comment on lines
165
to
167
| Using distributed tracing, Coroot provides a heat map showing operation requests, their status, durations, and details. | ||
|
|
||
|  |
There was a problem hiding this comment.
Why do we write something that has nothing to do with FerretDB?
Comment on lines
169
to
171
| The above image shows how response time for the `ferretdb` increased progressively over time. | ||
| It shows that the system takes a long time to handle queries. | ||
| That should prompt us to take additional measures to improve performance. |
Fashander
had a problem deploying
to
cloudflare-dev-blog
GitHub Actions
Failure
AlekSi
had a problem deploying
to
cloudflare-dev-blog
GitHub Actions
Failure
AlekSi
requested changes
Jun 3, 2024
| You also get CPU, memory, storage, network, and log management metrics. | ||
|
|
||
| To get started with FerretDB, [see our documentation](https://docs.ferretdb.io/). | ||
| And if you want to contact the team for help or have any questions, [contact us on Slack](https://join.slack.com/t/ferretdb/shared_invite/zt-zqe9hj8g-ZcMG3~5Cs5u9uuOPnZB8~A). |
There was a problem hiding this comment.
As we talked about many times before, we should not use that link because it may change. We should link to the community section in our docs or in README
There was a problem hiding this comment.
Alex, it is your responsibility to enforce that guide. And you are not even following it yourself.
AlekSi
added
not ready
noisersup
reviewed
Jun 4, 2024
|
|
||
| Setting up effective monitoring for your entire system can be resource-intensive, time-consuming, and expensive. | ||
| Imagine a scenario where your FerretDB instance is deployed as a Docker container along with other components and services. | ||
| Observability into all critical areas of the system in as little time is vital. |
There was a problem hiding this comment.
I believe the whole intro needs some short self-explanation. Why typical monitoring can be resource-intensive, time-consuming, and expensive?
We could potentially expand the "Imagine a scenario..." section to show the potential issues "in the practice", and then jump to the part how relying on eBPF solves that :)
If I can help in any way we could sync on this one
website/blog/2024-06-03-monitor-ferretdb-performance-using-coroot.md
Outdated
Show resolved
Hide resolved
…oot.md Co-authored-by: Patryk Kwiatek <patryk@kwiatek.xyz>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Closes FerretDB/engineering#168.
Readiness checklist
task all, and it passed.@FerretDB/core), Milestone (Next), Labels, Project and project's Sprint fields.