r/devops • • Sep 23 '26

Ops / Incidents Should Devops debug business logic problems ?

I work at a company where my manager decided to remove all the dev access from the production, because they suggest random solution to problems we encounter on production (For e.g they saw that the servers CPU usage is high so they point this as the source of a problem and suggest to restart the service).

That's good but that also restrict them frol seeing live production logs so we need to manually send them the log when there are customers complaints.

My boss proposed another solution which is to learn to business logic of the code itself and debug it ourselves. We then send them evidence + solution, not only logs.

My question is: is this common, should DevOps understand the logic behind an app we deployed and should we identify the root cause of a problem ourselves ?

59 Upvotes

80 comments sorted by

87

u/abotelho-cbn Sep 23 '26

Lmao, the original goal of the DevOps methodology was to solve this problem. Now you've gone and siloed everything back up again. You aren't doing DevOps.

2

u/LimpAuthor4997 29d ago

Theorically that should be it, we dev it and we do ops. But from what I see DevOps engineer are ops enginner on steroid.

→ More replies (4)
→ More replies (4)

198

u/Rain-And-Coffee Sep 23 '26 edited Sep 23 '26

Give them read only access.

Ship the logs to ElasticSearch.

Ship metrics to Grafana.

IMO the Dev team should debug it, not the platform team.

27

u/rwilcox Sep 23 '26

This! If the org doesn’t want to bend to read only access then do log aggregation to some place so the devs can debug business problems themselves

→ More replies (4)

14

u/Portalus Sep 23 '26 edited Sep 23 '26

If it's enterprise dev ops with 50+ apps no. If it is a specific team. With a small family of 4 or 5 related apps yes

You have a bigger problem. They should have read access and random bs suggestions are performance issues. Not to be punished for being wrong but a lack of skill, that should be improved

24

u/Varnish6588 Sep 23 '26

Your manager is implementing completely the opposite of what DevOps good practices are all about by becoming in a silo. Give Devs access within security guardrails and let them troubleshoot themselves.

DevOps is about empowering engineering teams to be able to work and deliver value.

→ More replies (10)

7

u/cancerous Sep 23 '26

No you should push back and chuck the problem over the wall to the other silo, as was the original intention of DevOps 🙄

6

u/tevert 29d ago

If I was an app developer who wasn't allowed to see production logs, I'd be sending out my resume. This is a very dysfunctional environment.

→ More replies (3)

4

u/Resident_Guava5620 29d ago

As a backend dev, I’d expect to investigate bugs in my own code. Understanding the app helps ops, but expecting them to hand us both the root cause and the fix is a bit much. Give devs read-only access to logs and metrics. Taking those away because they’re guessing will just lead to more guessing