What Your Peers Are Saying About
VP of IT
How are you approaching Observability in the Cloud across both non-prod and prod environments? Are you paying for a tool (e.g. Dynatrace) across all environments or only production? If only production, are your devops teams able to use the tool effectively in production after not having used it in development? If across all environments, how is the cost not prohibitive? Or, did you manage to accept it as a cost of doing business?Vice President of Enterprise Solutions
See Full DiscussionI’ve found that a 'tool-first' approach can sometimes lead to unnecessary costs. Instead, consider a 'problem-first' mindset: pinpoint specific observability needs in both non-prod and prod environments before selecting tools. If using tools like Dynatrace across all environments, ensure they’re utilized effectively by your DevOps teams. For those managing costs, evaluate if a tool’s expense is justified by its value and how it contributes to overall efficiency. Balancing cost with effectiveness is key to a sustainable observability strategy.
Director of Corporate Development
Curious to hear how organizations are leveraging observability tools in relation to their ITSM platforms. Where is the source of truth for SLAs/SLOs? How is application dependency mapping handled? Is there integration between the two technologies? We are using Dynatrace (observability) and ServiceNow (ITSM), for reference.Sr Software Principal engineer (Gen AI and ML Security)
See Full DiscussionServicenow + Dynatrace is a decent combination. Although, it would be better to maintain the product/app dependencies in a separate system, infra dependency in Servicenow, observability in dynatrace/splunk/grafana