Offensive Security Labs Os 2402 Pdf Download
Katja Gains
Welcome! This lab is available for you to repeat as many times as you want. To start somewhere other than the beginning, use the Table of Contents in the upper right-hand corner of the Lab Manual or click on one of the modules below.
The lab console will indicate when your lab has finished all the startup routines and is ready for you to start. If you see anything other than "Ready", please wait for the status to update. If after 5 minutes your lab has not changed to "Ready", please ask for assistance.
VMware Aria Operations delivers intelligent operations management with application-to-storage visibility across physical, virtual, and cloud infrastructures. Using policy-based automation, operations teams can automate key processes and improve IT efficiency.
Using data collected from system resources (objects), Aria Operations identifies issues in any monitored system component, often before the customer notices a problem. Aria Operations also frequently suggests corrective actions you can take to fix the problem right away. For more challenging problems, Aria Operations offers rich analytical tools that allow you to review and manipulate object data to reveal hidden issues, investigate complex technical problems, identify trends, or drill down to gauge the health of a single object.
The Administration section allows for management and customization of several options for VMware Aria Operations, ranging from access and certificate management, to management of the Aria Operations nodes themselves, to configuration and customization of capacity and cost calculations. We will not be reviewing each of these sections in detail, but some exercises in this lab series do leverage Administration settings.
We have already explored the Aria Operations Launchpad and navigation menu. But what happens if we need to locate an object quickly in the inventory and you do not know where it is? Well just like in VMware vCenter, there is a search feature in VMware Aria Operations.
The object detail page includes detailed information on the object in the Aria Operations inventory (in this case, the windows-0010 VM.) We could have navigated through the Object Browser to find this VM, but the search field allows us to locate it quickly.
You can scroll down through the Summary tab to view additional information, or click any of the other tabs to view more detail for this object. Several of these tabs will be covered in later modules in this lab, as well as later labs in the series.
In this module, we started to explore the VMware Aria Operations interface using the basic navigation functions. We introduced the Search function which gave us the ability to search and quickly locate the objects in the inventory. By reviewing each of the different functions of the VMware Aria Operations interface we can see how comprehensive a toolset it can be for managing our virtual infrastructure.
Managing and estimating available capacity in a dynamic virtualized environment can be a challenge. Aria Operations provides several out-of-the-box dashboards that provide additional insights into available capacity as well as estimates of time remaining based on observed growth in the environment.
Capacity quantifies the resources used, resources remaining, and opportunities to reclaim unused resources. Projections of the demand provide a proactive view of capacity. The Capacity Dashboards display capacity in terms of time remaining before capacity is projected to run out, the amount of capacity remaining, the number of VMs that might fit in the remaining capacity, and reclaimable resources that can increase the available capacity.
Due to the time and resources allotted for this Hands-On Lab, we won't individually review these dashboards, but we will identify where these dashboards are located to provide an opportunity to further research as time allows.
The Capacity Pillar in Aria Operations is designed to assess workload status and how much capacity is remaining in data centers across your environment. To access the Capacity Pillar, do the following:
As we scroll down further on the Datacenter Capacity page, notice the Cluster Utilization widget and how it provides a graphical chart estimating the time remaining of current resources (at current rate of growth). Additionally, the chart shows a history of resources for the past month and a forecast of resources for the next three months. Several options can be explored in this widget by doing the following:
Aria Operations gives administrators in depth reporting and alerting capabilities. With the ability to create customized alerts designed for specific objects, applications or systems, administrators can eliminate the noise of an environment and instead focus on whats important. Let's take a look at the basic alerting capabilities with more advanced topics covered in additional Labs.
Aria Operations Alerts are similar to rules used for years in monitoring critical IT resources. However, previous rule-based systems tended to be static and difficult to build, deploy, and maintain. Aria Operations leverages built-in analytics and predefined content to provide a dynamic, effective, and scalable approach for identifying and resolving issues in your environment.
For this lesson, we will start by exploring a Symptom Definition. Symptom Definitions enable Aria Operations to identify problems with objects in your environment. These Symptom Definitions can be used to build alerts in our environment. Let's get started.
Symptom Definitions are conditions that evaluate the state of your environment that, if met, trigger a symptom which can result in a generated alert. Symptom definitions can be created using attributes such as metrics, super metrics, properties, message events, fault events, or metric events. You can create a symptom definition as you create an alert definition or as an individual item in the appropriate symptom definition list.
Metric and super metric symptoms are based on the operational or performance values that VMware Aria Operations collects from target objects in your environment. You can configure the symptoms to evaluate static thresholds or dynamic thresholds.
Metric symptoms that are based on dynamic thresholds compare the currently collected metric value against the trend identified by VMware Aria Operations , evaluating whether the current value is above, below, or generally outside the trend.
Message event symptoms are based on events received as messages from a component of VMware Aria Operations or from an external monitored system through the system's REST API. You define symptoms based on message events to include in alert definitions that use these symptoms. When the configured symptom condition is true, the symptom is triggered.
The adapters for the external monitored systems and the REST API are inbound channels for collecting events from external sources. Adapters and the REST server both run in the VMware Aria Operations system. The external system sends the messages, and VMware Aria Operations collects them.
System Performance Degradation - This message event type corresponds to the EVENT_CLASS_SYSTEM and EVENT_SUBCLASS_PERFORM_DEGRADATION type and subtype in the VMware Aria Operations API SDK.
Change - The VMware adapter sends a change event when the CPU limit for a virtual machine is changed from unlimited to 2 GHz. You can create a symptom to detect CPU contention issues as a result of this configuration change. This message event type corresponds to the EVENT_CLASS_CHANGE and EVENT_SUBCLASS_CHANGE type and subtype in the VMware Aria Operations API SDK.
Environment Down - The VMware Aria Operations adapter sends an environment down event when the collector component is not communicating with the other components. You can create a symptom that is used for internal health monitoring. This message event type corresponds to the EVENT_CLASS_ENVIRONMENT and EVENT_SUBCLASS_DOWN type and subtype in the VMware Aria Operations API SDK.
Fault symptoms are based on events published by monitored systems. VMware Aria Operations correlates a subset of these events and delivers them as faults. Faults are intended to signify events in the monitored systems that affect the availability of objects in your environment. You define symptoms based on faults to include in alert definitions that use these symptoms. When the configured symptom condition is true, the symptom is triggered.
If the adapter published fault definitions for an object type, you can select one or more fault events for a given fault while you define the symptom. The symptom is triggered if the fault is active because of any of the chosen events. If you do not select a fault event, the symptom is triggered if the fault is active because of a fault event.
Metric event symptoms are based on events communicated from a monitored system where the selected metric violates a threshold in a specified manner. The external system manages the threshold, not VMware Aria Operations .
Metric event symptoms are based on conditions reported for selected metrics by an external monitored system, as compared to metric symptoms, which are based on thresholds that VMware Aria Operations is actively monitoring.
The metric event thresholds, which determine whether the metric is above, below, equal to, or not equal to the threshold set on the monitored system, represent the type and subtype combination that is specified in the incoming metric event.
When defining an Alert Definition we need to select the object type that this Alert will cover. These object types are all the objects that Aria Operations can monitor and collect data for. This includes VMware components as well as non-VMware components which allows Aria Operations to serve as the monitoring hub for your entire datacenter.
When creating an alert definition, we first need to decide what symptoms the alert will trigger from. We spent time going over the different types of symptom and condition definitions earlier in the lab and here is where we consume them.
b1e95dc632