A thread, in the context of Java, is the path followed when executing a program. All Java programs have at least one thread, known as the main thread, which is created by the Java Virtual Machine (JVM) at the program’s start, when the main() method is invoked with the main thread. In Java, creating a thread is accomplished by implementing an interface and extending a class. Every Java thread is created and controlled by the java.lang.Thread class.
On one of the EUC slack forums, a question was recently posted asking what are the key lessons learned in the last year and what changes organizations should investigate in the next year. The answers were revealing. Several folks pointed out that prior to the pandemic, we were operating within the comfort zone of carefully planned deployments with managed devices and managed networks.
In this blog, I’ll cover a real-world example of application performance troubleshooting a Java web app, hosted on JBoss Wildfly using Microsoft SQL as the backend database, including details of the analysis and diagnosis we had to perform in order to identify the root-cause of, and resolve, the performance issue.
A recent eG Innovations & DevOps Institute APM survey of more than 900 IT professionals indicated that AWS is the dominant cloud service provider. Organizations are deploying a wide variety of workloads on AWS cloud environments to ensure agility, scalability, and high availability of their application services.
In an earlier blog post, we had discussed how server performance monitoring is not just about monitoring CPU, memory, and disk resources anymore. There is more to server performance monitoring than just three resources or metrics. That blog post covered several key performance indicators (KPIs) that IT teams must track to ensure that their servers are performing well. In this blog post, we focus on another KPI – server uptime.
The Azure Active Directory (Azure AD) is Microsoft’s cloud-based identity and access management (IAM) service and an identity provider (IdP). Azure AD is the backbone for authentication in Microsoft 365 and for thousands of cloud-based SaaS applications. Azure AD provides several features for your organization and one of the features is the Microsoft Identity Platform.
This blog post is part 2 of our Monitoring Microsoft Azure Active Directory series. Managing Identity is a big challenge in a cloud environment, especially when users can potentially log in from anywhere. Additionally, users can often use different types of devices to log in and access cloud-hosted resources. Without a central Authentication and Authorization source, it is very difficult to manage who can login to what and who can do what with a cloud resource.
eG Innovations works with Managed Service Providers (MSPs) across the world, who use eG Enterprise to deliver value-added services to improve their customers’ resilience and business outcomes. Many of these service providers choose eG Enterprise for its secure and granular role-based multi-tenancy support. The service provider does not have to configure and maintain one instance of eG Enterprise for each customer.
In the second half of 2021, eG Innovations partnered with the DevOps Institute to conduct an online survey of more than 900+ individuals from Sys Admin, DevOps, SREs, and other IT backgrounds. We asked questions about: Some of the results included: You can download the full survey results here: Cloud Technology Adoption Trends | eG Innovations If surveys and statistics on technology adoption are of interest, we have some other recent ones available, conducted in the last 12 months,.
Thomas Stringer has a couple of great blog posts on how to understand your Azure monitoring costs and also on how to reduce your costs, see Azure Monitor Log Analytics too Expensive? Part 2 – Save Some Money | Thomas Stringer (trstringer.com). In the past I’ve blogged on How to calculate the Azure Monitor and Log Analytics costs associated with AVD (not an easy task!).
