DB Monitoring Using Full Stack

[bagusputro]

Hi!

Could anyone advise whether it is suitable to have DB monitoring using full stack or it is better to have it under infra monitoring?

Thanks!

[MaximilianoML]

Hello @bagusputro,

In general, for dedicated database servers, it’s usually better to use Infrastructure Monitoring rather than Full-Stack.

A common setup is:

• Full-Stack on the application hosts, so you can see database calls from the app perspective
• Infrastructure Monitoring on the database hosts, for DB server health and performance

So if the host is mainly running the database, infra monitoring is normally the better fit. If it also runs application components and you need deep code-level visibility there, then Full-Stack can make sense.

[bagusputro]

Hi Max!

Much appreciated for your prompt feedback!
Will infra monitoring give us less visibility against full stack monitoring for database?
And what setup is required to have deep monitoring for the database level e.g query cost, query running time, etc? Do we need some extension for this one?

Thanks a lot!

[MaximilianoML · Accepted solution]

Hello @bagusputro ,

Yes, Infra Monitoring gives less visibility than Full-Stack on the DB host itself, mainly because you won’t get the same deep process/code-level tracing there.

That said, for a dedicated database server, Infra Monitoring is usually the right choice. A common setup for the Modes are:

• Full-Stack on the application hosts
• Infra Monitoring on the database host
• Database extension + Databases app for deeper DB insights

So if you want things like query execution time, expensive queries, and DB-level performance details, then yes you typically need the relevant DB extension for that.

Kudos are appreciated if helped you 😃

[bagusputro]

Hi Max!

Thanks for your explanation!
As for DB extension, is there any separated cost for that one? or is it already included in one monitoring package?

Thank you!