Why not the Appliance for production and what are the partition recommendations?

[IT_Architect]

Why not the Appliance for production and what are the partition recommendations?
- I see they have an appliance but do not recommend using it for production. Why is that?
- What are the partition recommendations for Linux? /usr? Where are the areas of expansion? /var? or /home? so I know how to set up for Zabbix. I haven't used Zabbix in 10 years and while I still have the VMs I could fire up, I want to start over fresh with the newest.
- If I install the beta of 6, can it be upgraded to release?

Thanks!

[cyber]

Appliance is for getting to know the product etc. They are all-in-one installs. Not optimized for large environment, where you should separate your components to different hosts (DB, webserver, server itself) For prod env you should probably tweak your VM settings etc..
Your main expansion points are DB and logs. But is is up to you, where you put those...
Yes you beta install can be upgraded.

[cyber]

Appliance is for getting to know the product etc. They are all-in-one installs. Not optimized for large environment, where you should separate your components to different hosts (DB, webserver, server itself) For prod env you should probably tweak your VM settings etc..
Your main expansion points are DB and logs. But is is up to you, where you put those...
Yes you beta install can be upgraded.

[IT_Architect]

That's everything I needed to know. I will only be fielding two Zabbix VMs, each monitoring 4 hosts on an opposing server, so probably anything would work. I might start out with the appliance and see what the partition requirements are and then spin up an AlmaLinux install with Zabbix and make a copy on the other server. Since I'm not stuck where the db and logs are, I'll put them on an end partition where I can start small and expand as necessary.

I used Zabbix up until about 10 years ago installed on a couple FreeBSD hosts and wrote my own checks which I still have but not active. However, it doesn't make sense not to start new since I'm relearning anyway and I'm sure a lot has changed. I'll go for the agent2. When I heard it was written on GO I was thinking, what's GO? (Thinking another much ado about nothing like like python.) GO's mascot didn't help and I just got done looking at Rust, which is unmaintainable code with nutty installs. After watching a overview of GO on YouTube, I was impressed, and will be using it for a lot more than Zabbix. GO is like a real language in that reads, and thus maintainable, plus it can be compiled into an executable that doesn't depend on other services. Excellent choice for agent2.