Monitor Solr?

tblancher

I see in the documentation that one should closely monitor Solr, but it doesn’t give any hints or clues on how to do this. I’ve begun to monitor Pressure Stall Information (PSI), a feature of newer Linux kernels, but I’m not sure if that would be enough.

I’ve looked at the Solr documentation, and they mention monitoring as well without specifying exactly how to monitor Solr. It seems monitoring is supposed to already be understood by the system administrator, and I don’t see clues on how to set this monitoring up.

I’m not having any problems with Solr right now, I’m still planning my initial deployment of mailcow-dockerized. I was rereading the installation and setup guide, and this monitoring aspect of Solr caught my attention.

tblancher

So, no one responded to this topic. I did my own research, and found this blog post discussing some options for container monitoring. Also, in the same search I found an ad for New Relic, which appears to be more turnkey and their free tier seems to be just what I need.

I’m going to give New Relic a try. If I’m ultimately dissatisfied with it, I can explore the other options for open source container monitoring.

TheNomad11

tblancher I was also wondering about this, so thanks for your post. Please keep us updated. Let’s hope this forum will become more active!

tblancher

TheNomad11

New Relic looks pretty slick, but for me it’s not as turnkey¹ for me as advertised, since I’m running Arch Linux on my VPS (a choice I still don’t regret). Basically, I’m having to install everything manually, and I’m not quite there yet. New Relic identified two gaps in my implementation since their manual guide seems a bit incomplete, not everything you need is installed using their manual tarball method and their instructions for doing it manually aren’t all in the same place. I’ve tried both methods, as a docker compose service in my non-mailcow stack, and as a standalone Linux service.

For everything thus far at least for the standalone Linux service, I’ve set up PKGBUILDs (Arch Build System scripts) that just install the pre-compiled binaries available from the New Relic GitHub site (it’s all Apache 2.0 licensed). My next step is to install their packaged version of FluentBit. Not sure why FluentBit isn’t part of their docker image, I haven’t found instructions on how to install it as a separate service using the New Relic flavor (which is a minor release and several patch releases behind the latest stable FluentBit).

1: “Turnkey” means you install it using their Guided Install method, and they bundle everything together (or install it outright) so you don’t have to fiddle with it too much to get started. If you run Ubuntu, Debian, Red Hat/CentOS/etc., or SuSE, it should work out of the box, just run their install script and it will do everything for you. Sadly they don’t have Arch as a supported platform, so I’m doing everything myself.

tblancher

OK, so I have New Relic fully set up, in terms of ingest. I removed my newrelic-infra Docker services, as that can’t monitor logs on the host. But I have the Docker integration, so both my logs and Docker compose services are being monitored.

If you use one of their supported Linux distributions, it is MUCH easier to set up. Also, you get 100GB of ingest for free per month, and it’s $0.30 per GB after that (seems kind of steep to me). If you ingest into a non-US region, it’s an extra $0.05 per GB after the first 100GB. So far I’ve used 9GB since October 1 when I started setting this up, at an average of 0.31GB per day. So I don’t feel I’ll be approaching the 100GB limit before the end of the month.

I think I’ll be ready to turn on mailcow-dockerized at the beginning of November, and see how it goes!