When a Rust server starts stuttering or behaving unpredictably after changes, how do you normally narrow down whether the problem is a plugin, plugin interaction, server resources, database/storage activity, or something else?
I’m interested in the order people use when troubleshooting, especially on servers with a larger plugin stack.
For example, do you normally start with:
- Recent plugin updates or configuration changes
- Server console errors
- Plugin unload/reload testing
- Resource usage during the issue
- Database or file I/O
- Reproducing it on a test environment
- Temporarily disabling plugins in groups

I know there is no one-size-fits-all answer, but I’d be interested in the practical workflow people trust before they start changing infrastructure or rolling back everything.

Use a profiler and profile the server, Server console errors, Resource usage during the issue, Temporarily disabling plugins in groups

That makes sense, thank you.

When you are disabling plugins in groups, do you normally begin with the most recently changed plugins, or split the full list into larger groups and narrow it down from there?

I also like the idea of keeping a profiler baseline from a healthy period. Resource usage during an incident is useful, but it seems much easier to interpret if there is already a known-good reference point for the same server, player count, and plugin stack.

start with plugins updated right befor it started then if not then do them in groups.