We have released Dynatrace Managed version 1.340. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.340 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.338. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.338 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.336. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.336 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.334. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.334 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.332. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.332 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.330. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.330 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.326. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.326 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.320. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.320 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.318. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.318 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.316. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.316 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.314. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.314 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.312. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.312 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.310. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.310 appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.308. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.308 appeared first on Dynatrace news.

Expectations for network monitoring

In today’s digital landscape, businesses rely heavily on their IT infrastructure to deliver seamless services to customers. However, network issues can lead to significant downtime, affecting user experience and business operations. Traditional monitoring tools often fall short of providing deep insights into network layers, leaving gaps in understanding the root causes of performance issues. The market demands a robust solution that can monitor applications and the underlying network infrastructure to ensure end-to-end availability and performance.

The Dynatrace approach

Dynatrace addresses these challenges by extending its synthetic monitoring capabilities to include Network Availability Monitoring. NAM allows you to monitor the availability of remote hosts, network devices, and services over the network, even when HTTP/HTTPS endpoints are unavailable. You can utilize the same private synthetic locations you’ve been using to execute HTTP and Browser monitors and run ICMP, TCP, and DNS monitors. By integrating NAM with powerful Dynatrace Davis® AI, you gain 24/7 insights into the health of your network, enabling proactive identification and resolution of issues before they impact your business.

Key features of Network Availability Monitoring in Dynatrace Managed

• Three types of monitors are available: ICMP (to check the reachability of network devices and hosts), TCP (to verify the availability of specific services running on your network), and DNS (to ensure your DNS services are resolving correctly)
• All monitors are executed from the same private locations you’re already using to monitor your internal applications with HTTP and browser monitors.
• NAM integrates seamlessly with the Dynatrace Problems page in the web UI. These synthetic tests are integrated into Dynatrace Managed, allowing you to configure and manage them easily through the Dynatrace web UI or API. The results are combined with other monitoring data to provide a comprehensive view of your IT environment.

In Dynatrace Managed, you can easily create a new Network Availability Monitor by navigating to your list of available network monitors at Digital Experience > Synthetic > List of available Network Monitors and selecting Create a Network Availability Monitor. Configure your Network Availability Monitor according to your use case and save your changes. For more details, please refer to Dynatrace Documentation.

Next steps

Dynatrace Managed NAM allows the monitoring of remote hosts, network devices, and services through synthetic tests, allowing around-the-clock insights into network health. Future updates may include advanced analytics, extended support for additional network protocols, or integration with other Dynatrace features.

For further information, please also consult our newly established Network Availability Monitoring FAQ community post.

The post Get the most from Network Availability Monitoring on Dynatrace Managed appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.306. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.306 appeared first on Dynatrace news.

We’re excited to announce that Dynatrace has successfully achieved CSA Star 2 certification with a Gold Maturity Score. This significant milestone underscores our ongoing commitment to maintaining the highest standards of security and compliance in the cloud and making it easier for our customers to use Dynatrace SaaS.

What is CSA Star 2?

The Cloud Security Alliance (CSA) Security, Trust & Assurance Registry (STAR) is a comprehensive framework for cloud security assurance. The Level 2 certification involves a rigorous third-party assessment based on the CSA’s Cloud Controls Matrix (CCM). This certification is specifically designed for Cloud Service Providers (CSPs) and builds upon the more generic approaches of ISO 27001 and SOC 2 Type II.

CSA Star 2 strengthens Dynatrace cloud security posture

CSA Star 2 certification provides a trusted benchmark for cloud security and thus strengthens the overall Dynatrace security posture. It signifies that a cloud provider has undergone a thorough evaluation by an independent auditor, confirming that their security measures meet or exceed industry standards.

Benefits to Dynatrace customers

The Dynatrace® platform for observability and security with Davis® hypermodal AI provides answers and intelligent automation from data at an enormous scale. This enables innovators to modernize and automate cloud operations, deliver software faster and more securely, and ensure flawless digital experiences. That’s why the world’s largest organizations trust Dynatrace to accelerate digital transformation.

Achieving CSA Star 2 certification is not just a badge of honor for Dynatrace; it’s a testament to our dedication to safeguarding your data. This certification means:

• Enhanced trust: Customers can be assured that Dynatrace adheres to the highest security standards, as validated by CSA Star 2 certification through a third-party audit.
• Risk reduction: The certification process ensures that we have strong controls in place to mitigate security risks significantly, reducing the likelihood of breaches.
• Regulatory compliance: Our certification helps customers meet their own regulatory requirements, simplifying their compliance processes because our certification aligns with international standards and ensures data is handled in compliance with relevant laws and regulations.
• Streamlined audits: Customers can leverage our certification during their own audits, making the process more efficient and providing evidence of our commitment to security.

Our commitment

As shown by our broad range of certifications and accreditations, security is a core value at Dynatrace. Adding CSA Star 2 certification highlights our dedication to excellence. We’re focused on ongoing improvements to maintain the highest security standards and deliver exceptional service, providing a safe and governed environment for our customers.

What’s next

To learn more about Dynatrace data security and privacy, visit our Trust Center.

If you’re an existing Dynatrace Managed customer looking to upgrade to Dynatrace SaaS, see How to start your journey to Dynatrace SaaS.

The post Dynatrace achieves CSA Star 2 certification appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.304. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.304 appeared first on Dynatrace news.

What is SOC 1 Type II?

SOC 1 (Service Organization Control 1) is a widely recognized auditing standard developed by the American Institute of Certified Public Accountants (AICPA). It focuses on controls related to financial reporting. The “Type II” designation means that an independent auditor evaluated our controls over a period of time (typically six months) and confirmed the controls’ effectiveness.

Strengthening the Dynatrace security posture

Having SOC 1 Type II certification demonstrates Dynatrace’s robust security practices. Our internal controls have been rigorously assessed, ensuring we meet or exceed industry standards. This certification provides peace of mind to our customers, partners, and stakeholders, who can be confident that their data is safe.

Benefits to Dynatrace customers

Our customers directly benefit from our SOC 1 Type II certification:

1. Increased trust: With this certification, you can trust that Dynatrace adheres to stringent security protocols. We prioritize the confidentiality, integrity, and availability of all customer data.
2. Risk mitigation: By adhering to SOC 1 Type II standards, we minimize the risk of financial misstatements or security breaches. You can confidently rely on Dynatrace for critical operations.
3. Streamlined audits: You can leverage Dynatrace certification during your own internal audits; it simplifies the audit process and provides evidence of our commitment to security.

Our commitment

At Dynatrace, security is at the core of everything we do. Achieving SOC 1 Type II certification reinforces our dedication to excellence. We remain focused on continuous improvement, maintaining the highest security standards while ensuring you receive exceptional service.

What’s next

• To learn more about Dynatrace data security and privacy, visit our Trust Center.
• If you’re an existing Dynatrace Managed customer looking to upgrade to Dynatrace SaaS, see How to start your journey to Dynatrace SaaS.

The post Dynatrace achieves SOC 1 Type II certification appeared first on Dynatrace news.

In this blog, we previously announced and went through a demo on how the new distributed tracing app provides effortless trace insights. Today, we’ll walk through a hands-on demo that showcases how the Distributed Tracing app transforms raw OpenTelemetry data into actionable insights.

Set up the Demo

To run this demo yourself, you’ll need the following:

• A Dynatrace tenant. If you don’t have one, you can use a trial account.
• A Dynatrace API token with the following permissions:
  • Ingest OpenTelemetry traces (openTelemetryTrace.ingest)
  • Ingest metrics (metrics.ingest)
  • Ingest logs (logs.ingest)

To set up the token, see Dynatrace API – Tokens and authentication in Dynatrace documentation.

• A Kubernetes cluster (we recommend using this kind)
• Helm, to install the demo on your Kubernetes cluster.

Once your Kubernetes cluster is up and running, the first step is to create a secret containing the Dynatrace API token. This will be used by the OpenTelemetry collector to send data to your Dynatrace tenant. The secret can be created using the following command:

API_TOKEN="<your API token>"
DT_ENDPOINT=https://<your-tenant-id>.dynatrace.com/api/v2/otlp

kubectl create secret generic dynatrace --from-literal=API_TOKEN=${API_TOKEN} --from-literal=DT_ENDPOINT=${DT_ENDPOINT}

After successfully creating the secret, the OpenTelemetry demo application can be installed using Helm. First, download the helm values file from the Dynatrace snippets repo on GitHub.

This file configures the collector to send data to Dynatrace using the API token in the secret you created earlier. Then, use the following commands to install the Demo application on your cluster:

helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts

helm install my-otel-demo open-telemetry/opentelemetry-demo --values otel-demo-helm-values.yaml

After invoking the helm install command, the application will eventually be up and running, and the OpenTelemetry collector will send data to your Dynatrace tenant.

Inspect traces using the Distributed Tracing app

To gain insight into requests executed within the application, we can use the new Distributed Tracing app. This app provides an overview of all ingested traces within the application, including a list of the most recent traces and a time series chart representing metrics such as the response time percentiles and the number of successful and failed requests. The filtering fields on the left side make it easy to search for particular traces of interest, for example, if you want to inspect all the traces sent by a particular service.

Troubleshooting problems

Now let’s see how Distributed Tracing can help us spot problems and find their root cause. For this purpose, we’re going to make use of the built-in failure scenarios that are included in the OpenTelemetry demo. To enable a failure scenario, we need to update the my-otel-demo-flagd-config ConfigMap containing the feature flags of the application. The feature flags defined here contain a flag named productCatalogFailure, for which we will change the defaultVariant from off to on.

After a couple of minutes, the effects of this change will be noticeable due to an increase in failed spans within Distributed Tracing.

To investigate what’s happening here, we’ll open the details of one of the failed traces by selecting an entry in the span list. This leads to a detailed view of the complete trace, including all involved services in the executed request and the spans that are generated by these services.

Here we notice that the error seems to be caused by the product service, particularly instances of the GetProduct call. Select the failed span to access a detailed overview of the failed GetProduct request, including all attributes attached to the span, as well as a status description:

Here, we see that the status message indicates that the failures are related to the feature flag we changed earlier. However, not all of the GetProduct spans seem to be failing—only some.

Therefore, let’s investigate further by analyzing how certain attributes might impact the error rate. One interesting attribute to investigate is the product ID. In the example trace above, only some of the GetProduct requests failed.

To analyze whether there is a correlation between this attribute and the failure rate, we first select the attribute and add a filter to only show traces where this attribute is available:

After applying this filter, the trace list above should only display the requests to the GetProduct endpoint of the productcatalogservice:

Next, we’ll add the product ID attribute to the columns of the trace list.

To do this, select the column settings at the top right of the table. Here, we’re presented with the option to add additional attributes to the column. Using the search field, let’s look for the product ID attribute and select it.

Once we’ve added the product ID attribute to the columns of the trace list, we can group the traces by that attribute. This shows us how many traces for a particular product ID were successful and how many failed.

To perform the grouping, select the header of the App product id column, and select Group By in the menu.

The result of this operation confirms our suspicion that there might be something wrong with a particular product, as all the errors seem to be caused by requests for a particular product ID:

Of course, this example was somewhat easy to troubleshoot as we’re using a built-in failure scenario. This should, though, give you an impression of how Distributed Tracing enables you to investigate problems by first finding the failure point and then analyzing how certain attributes attached to spans might have an effect on the outcome of requests sent to a faulty service.

Conclusion

In this blog post, we explored how the Distributed Tracing app can be harnessed to visualize data ingested from the OpenTelemetry collector to get an overview of application health. This end-to-end tracing solution empowers you to swiftly and efficiently identify the root causes of issues. Enjoy unprecedented freedom in data exploration, ask questions, and receive tailored answers that precisely meet your needs.

This powerful synergy between OpenTelemetry and the Dynatrace platform creates a comprehensive ecosystem that enhances monitoring and troubleshooting capabilities for complex distributed systems, offering a robust solution for modern observability needs.

Get started

If you’re new to Dynatrace and want to try out the Distributed Tracing app, check out our free trial.

We’re rolling out this new functionality to all existing Dynatrace Platform Subscription (DPS) customers. As soon as the new Distributed Tracing Experience is available for your environment, you’ll see a teaser banner in your classic Distributed Traces app.

If you’re not yet a DPS customer, you can try out this functionality in the Dynatrace playground instead. You can even walk through the same example above.

If you’re interested in learning more about the Dynatrace OTel Collector and its use cases, see the documentation.

This is just the beginning. So, stay tuned for more enhancements and features.

Make your voice heard after you’ve tried out this new experience. Provide feedback for Distributed Tracing in the Distributed Tracing feedback channel (Dynatrace Community)

The post Demo: Transform OpenTelemetry data into actionable insights with the Dynatrace Distributed Tracing app appeared first on Dynatrace news.

We’re excited to announce the first version of our new Distributed Tracing app, a part of the new Dynatrace user experience that leverages the full power of the Dynatrace platform. With the Distributed Tracing app, you can flexibly slice and dice raw trace data to understand what went wrong and why. Find what you’re looking for faster with:

• Enhanced charting and data visualization: Easily filter, group, search, and visualize trace data to gain deeper insights into your system’s behavior.
• Automatic data capture and display: More data, including span attributes, is available for out-of-the-box analysis, with no additional configuration necessary.
• Seamless OpenTelemetry integration: Make the most of your trace data with native support of OpenTelemetry traces. For more details, see our recent blog post explaining how new Dynatrace capabilities help modern app teams analyze OpenTelemetry traces and log data at scale.

Whether you’re troubleshooting a specific issue or looking to improve overall system performance, Distributed tracing equips you with the tools you need to make informed decisions and maintain a high standard of application performance.

To understand the benefits of the Distributed Tracing app, let’s take a look at a typical scenario.

Use Distributed Tracing to improve application performance and troubleshoot faster

In this scenario, an e-commerce business uses Dynatrace to monitor the performance of its online store. They use Kubernetes to power their marketplace. The team decides to dig into the “prod” namespace to perform exploratory analysis of their critical production workloads.

By opening the time series view filtered by the “prod” cluster, the team immediately notices spikes in the 90% decile of request response times. These performance outliers in production are impacting customer experience, so the team needs to investigate further.

By analyzing the response time distribution in the histogram, the team notices that the outliers occur when the response time is around 5 seconds.

Next, the team leverages the interactive chart, hovering over the outlier requests to see real-time details. In the image below, they select the range of slow requests (3.7 s – 7.24 s) to investigate further.

Now filtered, the image below shows only requests in the time bucket selected (3.7 s -7.24 s).

The filter bar displays all the filters applied during the analysis. To better understand where slow response times are occurring, the e-commerce team decides to group requests by service and endpoint.

To focus on an essential endpoint for the e-commerce website, they use a wildcard (*) to filter on endpoints that start with "/cart".

This investigation reveals that requests in the “/cart/checkout” endpoint are failing. The team filters further by the “/cart/checkout endpoint” attribute value.

To pinpoint the exact requests that are failing, the e-commerce team filters by excluding successful HTTP 200 status codes. This refinement reveals that only a few requests are failing. The team can now dive deeper to find out why.

To understand what happened in detail, the team clicks on an impacted trace and opens the waterfall view of the full trace.

In the waterfall view, the team can quickly and easily switch among multiple traces and their attributes when analyzing issues. A span can have many different attributes, and the search function helps the team quickly find interesting insights. They search for “failure” and explore the exception tab. Here we’ve found some exceptions that happen rarely.

In this view, the root cause of the issue is clear: an exception is generated when a user tries to purchase an item with a card that is not a Visa or Mastercard. Instead of returning a 500 error, the application should provide the user with a failed payment message letting them know their card is the reason why the transaction was not completed. With these details, the issue is found, and they have the information needed to escalate the situation to their development teams and prioritize the creation and deployment of the needed fix.

With logs now integrated directly into the waterfall view, the team can see detailed log messages tied to each span without switching tools. This seamless access to both trace flow and detailed log context accelerates the investigation from symptom identification to root cause analysis

Explore service telemetry data

With the Services app you can view traces in an aggregated format, easily sift through problems, and ensure general services are functioning properly. A comprehensive view of trace data organized by services provides additional context.

When a problem arises, the Services app is an excellent tool for analysis. Davis^® AI automatic root cause analysis highlights abnormal behaviors, such as increased failure rates at the /cart/checkout endpoint, in real time to accelerate the analysis process

Get started with the Distributed Tracing and Services apps

If you’re new to Dynatrace and want to try out the Distributed Tracing app, check out our free trial.

We’re rolling out this new functionality for our existing Dynatrace Platform Subscription (DPS) customers. As soon as the new Distributed Tracing Experience is available for your environment, you’ll see a teaser banner in your classic Distributed Traces app.

If you’re not yet a DPS customer, you can use the Dynatrace playground instead. You can even walk through the same example above. The new Services app is already available to all DPS and non-DPS customers.

This is just the beginning. stay tuned for more enhancements and features.

Make your voice heard after you’ve tried out this new experience. Provide feedback for Distributed Tracing in the Distributed Tracing feedback channel (Dynatrace Community). To share your feedback regarding the Services app, go to the Services feedback channel (Dynatrace Community).

The post New Distributed Tracing app provides effortless trace insights appeared first on Dynatrace news.

We have released Dynatrace Managed version 1.302. To learn what’s new, have a look at the release notes.

The post Dynatrace Managed release notes version 1.302 appeared first on Dynatrace news.

Modern observability and security require comprehensive access to your hosts, processes, services, and applications to monitor system performance, conduct live debugging, and ensure application security protection. This level of access enables advanced capabilities such as runtime instrumentation and detailed diagnostics. While these techniques are powerful, they can pose risks to production environment resilience if not managed properly, as demonstrated by the widespread software outages in July.

At Dynatrace, we’ve implemented a thorough and industry-proven approach to developing OneAgent^® that minimizes such risks. Our approach encompasses all stages of the software development lifecycle, focusing on safeguarding OneAgent integration with your systems. Through rigorous testing, dependency management, continuous monitoring, and phased rollouts, we’ve prioritized the development of OneAgent with the highest possible reliability and security standards.

By adhering to these stringent processes, OneAgent is designed to operate smoothly and securely, minimizing the likelihood of disruptions and providing you with greater confidence in your system’s security.

Dynatrace OneAgent: Quick overview

Dynatrace OneAgent is a unified monitoring solution deployed across customers’ IT environments. It automatically discovers and monitors each host’s applications, services, processes, and infrastructure components. Injecting monitoring code into your applications without manual configuration ensures continuous and comprehensive monitoring and security. OneAgent provides end-to-end visibility, capturing real-time performance data and detailed metrics on CPU, memory, disk, network, and processes.

Safety measures across the entire software lifecycle

From development to rollout and production, we’ve developed safeguards to ensure production environment resilience at each phase of the software development lifecycle, preventing problems in your systems during updates. Let’s dive into the details.

End-to-end safety measures in the software development process

• Separation of concerns: Each OneAgent component is designed to perform only one specific function. Critical and impactful components are minimized and undergo regular detailed reviews. Changes are introduced on a controlled schedule, typically once a week, to reduce the risk of affecting customer systems.
• Dependency reduction: OneAgent development teams minimize the use of third-party or open source dependencies. Any required dependencies are thoroughly tested and fixed to specific versions, minimizing the risk of introducing untested code.
• Rigorous testing: Engineers conduct extensive unit and integration tests on all code changes, covering individual functions and OneAgent performance with real-world applications. These tests are run on all supported operating systems and versions to enhance reliability.
• Hardening phase: Before release, OneAgent undergoes a month-long hardening phase, during which repeated tests are conducted to uncover hidden issues. Our developers double-check these tests daily. The software is also deployed to internal test applications for real-world validation.
• Artifact signing: OneAgent binaries are signed to prevent unauthorized changes. The deployment steps guide you through verifying the signature during installation, and from this point on, any OneAgent updates are verified automatically to ensure the integrity of the OneAgent.

Reduced likelihood of failures in the OneAgent rollout process

• Pre-rollout check: After the hardening phase, we thoroughly review each new OneAgent version with all teams to identify any known issues or concerns. We only proceed with a phased rollout when confident in a release.
• Phased and controlled rollout: Each rollout is carefully staged, starting with internal environments, then moving to proofs-of-concept (POCs), trials, new customer environments, and finally to the broader customer base. We monitor correct OneAgent behavior and functionality at each stage to ensure it behaves as expected.
• Customer control: You can manually update OneAgent versions, prioritizing updates for critical applications or host groups while enabling auto-updates for less critical areas. You can also schedule updates during maintenance windows to minimize disruption.

Stay ahead of potential failures with production self-monitoring

• 24/7 fully automated monitoring: We continuously monitor critical statistics, such as the number of connected OneAgents per technology, to swiftly address any significant issues. We also collect and analyze warning and severe log events to proactively address potential problems before they escalate into incidents.
• Real-time health insights: Dynatrace provides immediate insights into your environment, helping you quickly identify the root cause of any issues. This enables you to clearly understand the health of your OneAgent deployment across your entire environment.

• Automated issue collection: Details of potential issues are automatically collected and can be sent to Dynatrace for further analysis. Additionally, manual diagnostics can be performed to gather more specific information if needed.

• Proactive analysis and auto-remediation: When a problem is reported, regardless of its severity, we assess its potential impact on our customers’ environments and take appropriate action as needed. This might include adding safety checks or rolling out an updated version to address the issue.

Ensure system stability with our zero-impact policy

Dynatrace OneAgent is built with a focus on reliability and security, aiming to keep your systems stable and protected. We proactively approach potential risks, implementing rigorous standards across the entire software development lifecycle and maintaining continuous, real-time monitoring. This comprehensive strategy is designed to reduce the likelihood of disruptions, offering you greater confidence in the safety and resilience of your IT environment.

While no system is entirely free from potential risks, our approach minimizes such risks and provides robust protection for your systems, helping to ensure smoother and more reliable operation.

For complete details about Dynatrace OneAgent, go to Dynatrace Documentation.

Interested in innovating along with us? Explore the OneAgent careers page.

The post Dynatrace commitment to safe OneAgent releases: Protecting production environment resilience appeared first on Dynatrace news.

As we did with IBM Power, we’re delighted to share that IBM and Dynatrace have joined forces to bring the Dynatrace Operator, along with the comprehensive capabilities of the Dynatrace platform, to Red Hat OpenShift on the IBM Z and LinuxONE architecture (s390x). IBM Z and LinuxONE mainframes running the Linux operating system enable you to respond faster to business demands, protect data from core to cloud, and streamline insights and automation. By leveraging Dynatrace observability on Red Hat OpenShift running on Linux, you can accelerate modernization to hybrid cloud and increase operational efficiencies with greater visibility across the full stack from hardware through application processes.

Dynatrace full stack observability for Red Hat OpenShift

Dynatrace enhances software quality and operational efficiency, which drives innovation by unifying application, operation, and platform engineering teams on a single platform. Dynatrace with Red Hat OpenShift monitoring stands out for the following reasons:

1. With infrastructure health monitoring and optimization, you can assess the status of your infrastructure at a glance to understand resource consumption and thus optimize resource allocation for cost efficiency.
2. Full stack observability gives you comprehensive observability across your entire stack, including Kubernetes clusters, logs, and more. Telemetry data, such as traces and metrics, allow you to analyze the end-to-end performance of your deployed applications. You also benefit from enhanced monitoring capabilities with seamless Dynatrace integrations with cloud-native technologies and services like Istio and Prometheus.
3. Dynatrace Smartscape® technology provides all data in context to simplify analytics and problem detection by semantically mapping metrics, traces, logs, and real user data to specific Kubernetes objects, including containers, pods, nodes, and services.
4. You can automatically detect and analyze performance issues across your entire tech stack with Davis® AI. This lets you quickly troubleshoot issues by identifying problematic components or configurations and providing insights into the root cause.
5. Dynatrace is designed to scale easily across the entire Kubernetes stack. Its support of GitOps practices allows for handling large-scale deployments with thousands of nodes and containers, making it the best option for enterprise-grade Red Hat OpenShift monitoring.

The new Dynatrace Kubernetes experience also marks a groundbreaking advancement for platform engineering teams by enabling you to pull critical observability and security information into a centralized Kubernetes management console. In particular, it allows you to explore cluster health, resource utilization, security, and the performance of applications built and deployed on a Kubernetes-centric platform. This is significant when coupled with the  OpenShift platform.

Dynatrace Operator for OneAgent, API monitoring, routing, and more

Dynatrace Operator leverages Kubernetes’ native capabilities to automate the rollout, configuration, and lifecycle management of Dynatrace components within Kubernetes environments. It simplifies setting up and maintaining Dynatrace observability by encapsulating the necessary configuration and operational logic into a single entity.

Dynatrace Operator acts as an intelligent controller that understands the desired state of your Dynatrace monitoring environment and takes actions to achieve it. It automates tasks such as provisioning and scaling Dynatrace monitoring components, updating configurations, and ensuring the health and availability of your monitoring infrastructure.

Dynatrace Operator consumes DynaKubes with cloud-native full-stack configuration and deploys the following resources:

• Dynatrace OneAgent, deployed as a DaemonSet, collects host metrics from Kubernetes nodes.
• Dynatrace code modules, enabled via Dynatrace webhook, provide distributed tracing and code-level visibility for applications deployed on Kubernetes.
• Dynatrace ActiveGate is used for routing and monitoring Kubernetes objects by collecting data (metrics, events, status) from the Kubernetes API.

With this approach:

• Red Hat OpenShift infrastructure (control plane and worker nodes) and workloads are instrumented automatically without manual code change.
• The scope of automatic workload instrumentation is user-configurable, for example, by namespace.
• Lifecycle management of Dynatrace components (for example, ActiveGate and OneAgent) is automatic and secure.

Get started monitoring Red Hat OpenShift on IBM Z and LinuxONE

• New to Dynatrace? Sign up for a fully functional Dynatrace free trial.
• Learn more about the new Kubernetes Experience for Platform Engineering.
• Dynatrace observability is available for Red Hat OpenShift on IBM Power.

The post Dynatrace observability now available for Red Hat OpenShift on IBM Z and LinuxONE mainframes appeared first on Dynatrace news.