When is event-driven architecture overkill for internal app integrations?

I've noticed a lot of teams just going with event-driven patterns for pretty much all their internal app stuff, even when it seems simple. There's a big push for it, I guess with microservices or just what's popular right now. But sometimes, it makes things way more complicated to manage and harder to understand, and you don't really see a clear upside. For basic request-response things, especially when services are kinda linked in concept or speed isn't a huge deal for that one integration, is it always the right move? What are some good rules of thumb or actual cases where you'd say, 'Nah, don't go totally event-driven for this internal communication'?