How much do devops engineers usually own observability tools and topics?

Аналитика рынка

Стек

Откликнуться

Загрузите резюме — мы свяжем вас с работодателем напрямую через нашу базу.

Описание

How much do devops engineers usually own observability tools and topics? Hi I am an Architect in a small team and we're trying to implement observability solutions for our infra. We have had Zabbix for infra monitoring for years - owned and managed by our infra team. But we have been lacking at application monitoring and logging and we are implementing ELK platform and we decided to take Prometheus + Grafana for application monitoring. For the logging platform, we have an external partner who helps manage our on-prem instance. For the monitoring platform, our infra team just set up some local VMs with the tech stack and now handed it over to our dev team's devops. And I am struggling to figure out how to proceed. Our devops engineers have previously said that they want a working platform and not own the platform itself. We have kind of achieved this now, although we don't get the platform owner support as well as we would want (about best practices etc) But now adding our apps and configuring them etc - as an architect i would want them to take ownership and know what and how to set up and what to monitor, at least offer what to do there. But they also word it in a way that they want me as an architect or business product owners to tell them what data/metrics to monitor or what dashboards to create etc. And on one hand, i get it.. but on the other hand, i am swamped with so many other areas and I want them to take more ownership. So I just wonder - it seems they are deflecting responsibility on different levels but i find it hard to define where do the boundaries of devops' responsibilities run then. I just want to get something done eventually (but i do get that this "something" has to be defined) - just that by now it has been dragging on for too long and i feel it just falls on me like everything else. [link] [handle]

Контакты работодателя (email/phone/telegram) скрыты из публичного превью — отправьте резюме, чтобы мы связали вас напрямую.