Civil Rights
Movements, leaders, victories and the continuing fight for equality.
q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
Explore the people, places, events, achievements, struggles and stories that shaped our journey.
Movements, leaders, victories and the continuing fight for equality.
Innovation, patents, science, technology and world-changing contributions.
Pioneers, champions, Negro Leagues, records, activism and excellence.
Meet the people whose lives, choices and achievements shaped the journey.
Black towns, communities, institutions and places where history happened.
Moments that changed communities, movements, institutions and the nation.
In August 1908, a white mob attacked Springfield, Illinois’s Black community, destroying homes and businesses and lynching two Black men. National outrage over the violence helped spur the movement that created the NAACP the following year.
MORE →Reflects the personal views, recollections, and perspective of the author, Mike Davis.
This is a personal recollection on the Move fire on May 13, 1985
 | This article is written like a personal reflection, personal essay, or argumentative essay that states a Wikipedia editor's personal feelings or presents an original argument about a topic. (July 2017) |
| This article may be too technical for most readers to understand. (October 2021) |
In software design, web design, and electronic product design, synthetic monitoring (also known as active monitoring or proactive monitoring) is a monitoring technique that is done by using a simulation or scripted recordings of transactions. Behavioral scripts (or paths) are created to simulate an action or path that a customer or end user would take on a site, application, or other software (or even hardware). Those paths are then continuously monitored at specified intervals for performance, such as functionality, availability, and response time measures.
Synthetic monitoring enables a webmaster or an IT/Operations professional to identify problems and determine if a website or application is slow or experiencing downtime before that problem affects actual end users or customers. This type of monitoring does not require actual traffic, thus the name synthetic, as it enables companies to test applications 24x7, or test new applications prior to a live customer-facing launch.[1][2]
Because synthetic monitoring is a simulation of typical user behavior or navigation through a website, it is often best used to monitor commonly trafficked paths and critical business processes. Synthetic tests must be scripted in advance, so it is not feasible to measure performance for every permutation of a navigational path an end user might take. These scripts are then injected into the code of the application or website, which is then tested under artificial loads. This, of course, can be a contrast to actual load/traffic when the design goes live. In this case, real user monitoring is performed, where the performance metrics are tested against real loads. This is more suited for passive monitoring.
Synthetic testing is useful for measuring uptime, availability, and response time of critical pages and transactions (how a site performs from all geographies) but doesn't monitor or capture actual end user interactions, see Website monitoring.[3]
Synthetic monitoring will report myriad metrics, and it's up to the a webmaster or an IT/Operations professional to identify which ones are most important. Common metrics from synthetic website monitoring includes Time to First Byte, Speed Index, Time to Interactive, and Page Complete.[4]
Demand for synthetic monitoring has grown exponentially corresponding to the underlying growth in websites/applications. IT/Operations staff need mechanisms to identify health and performance issues in advance of their customers identifying and reporting them to avoid customer satisfaction issues. To accomplish this they can write custom simulation scripts, or leverage the growing number of commercial synthetic monitoring solutions. Example include:
By implementing Synthetic Monitoring IT/Operations staffs are able to identify application issues in advance of them becoming critical, and take remedial action. Identifying such issues can be difficult because of:
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
In software design, web design, and electronic product design, synthetic monitoring (also known as active monitoring or proactive monitoring) is a monitoring technique that is done by using a simulation or scripted recordings of transactions. Behavioral scripts (or paths) are created to simulate an action or path that a customer or end user would take on a site, application, or other software (or even hardware). Those paths are then continuously monitored at specified intervals for performance, such as functionality, availability, and response time measures. Synthetic monitoring enables a webmaster or an IT/Operations professional to identify problems and determine if a website or application is slow or experiencing downtime before that problem affects actual end users or customers. This type of monitoring does not require actual traffic, thus the name synthetic, as it enables companies to test applications 24x7, or test new applications prior to a live customer-facing launch. Because synthetic monitoring is a simulation of typical user behavior or navigation through a website, it is often best used to monitor commonly trafficked paths and critical business processes. Synthetic tests must be scripted in advance, so it is not feasible to measure performance for every permutation of a navigational path an end user might take. These scripts are then injected into the code of the application or website, which is then tested under artificial loads. This, of course, can be a contrast to actual load/traffic when the design goes live. In this case, real user monitoring is performed, where the performance metrics are tested against real loads. This is more suited for passive monitoring. Synthetic testing is useful for measuring uptime, availability, and response time of critical pages and transactions (how a site performs from all geographies) but doesn't monitor or capture actual end user interactions, see Website monitoring. Synthetic monitoring will report myriad metrics, and it's up to the a webmaster or an IT/Operations professional to identify which ones are most important. Common metrics from synthetic website monitoring includes Time to First Byte, Speed Index, Time to Interactive, and Page Complete. Demand for synthetic monitoring has grown exponentially corresponding to the underlying growth in websites/applications. IT/Operations staff need mechanisms to identify health and performance issues in advance of their customers identifying and reporting them to avoid customer satisfaction issues. To accomplish this they can write custom simulation scripts, or leverage the growing number of commercial synthetic monitoring solutions. Example include: Datadog's Synthetic Monitoring ManageEngine Applications Manager's synthetic monitoring via Real Browser Monitor(RBM) F5's Distributed Cloud Synthetic Monitoring Powerhouse Nudge Synthetic Monitoring by Atakama Technologies By implementing Synthetic Monitoring IT/Operations staffs are able to identify application issues in advance of them becoming critical, and take remedial action. Identifying such issues can be difficult because of: The number of applications monitored by an average sized organization can be several hundred Issues may vary by geography; for example performance issues may be evident to users in Asia, but may not appear to users in Europe IT/Operations staff need not only to identify the fact that an issue exists, but also need diagnostic information on what is causing the identified issue IT/Operations staff often lack the historical perspective on application performance which can be helpful in diagnosing an evolving issue
Passive monitoring is a technique used to capture traffic from a network by copying traffic, often from a span port or mirror port or via a network tap. It can be used in application performance management for performance trending and predictive analysis. Passive monitoring is also used in web performance optimization in the form of real user monitoring. E-commerce and media industries use real user monitoring to correlate site performance to conversions and engagement. It can be analyzed in a sniffer such as Wireshark. It can be examined for flows of traffic, providing information on "top talkers" in a network as well as TCP round-trip time. It can be reassembled according to an application's state machine into end-user activity (for example, into database queries, e-mail messages, and so on.) This kind of technology is common in real user monitoring. In some cases, HTTP reassembly is further analyzed for web analytics. Passive monitoring can be very helpful in troubleshooting performance problems once they have occurred. Passive monitoring differs from synthetic monitoring in that it relies on actual inbound web traffic to take measurements, so problems can only be discovered after they have occurred. Synthetic monitoring is also referred to as active monitoring, which helps report on system availability and predefined business transactions using synthetic probes and web robots. While initially viewed as competitive with synthetic monitoring approaches, most networking professionals now recognize that passive and synthetic monitoring are complementary.
Real user monitoring (RUM) is a passive monitoring technology that records all user interaction with a website or client interacting with a server or cloud-based application. Monitoring actual user interaction with a website or an application is important to operators to determine if users are being served quickly and without errors and, if not, which part of a business process is failing. Software as a service (SaaS) and application service providers (ASP) use RUM to monitor and manage service quality delivered to their clients. Real user monitoring data is used to determine the actual service-level quality delivered to end-users and to detect errors or slowdowns on websites. The data may also be used to determine if changes that are propagated to sites have the intended effect or cause errors. Organizations typically use RUM to test changes within the production environment or to anticipate behavioral changes in a website or application by using A/B testing or other techniques. As technology shifts more and more to hybrid environments like cloud, fat clients, widgets, and apps, it becomes more and more important to monitor the usage of applications from within the client itself. Real user monitoring is typically "passive monitoring" i.e., the RUM device collects web traffic without having any effect on the operation of the site. In most cases, a form of JavaScript is injected into the page or native code within the application to provide feedback from the browser or client. This data is collected from various individuals and consolidated. RUM can be very helpful in identifying and troubleshooting last-mile issues. RUM differs from synthetic monitoring in that it relies on actual people clicking on the page to take measurements rather than automated tests simply going over a given set of test steps. RUM feature is available in various observability products such as Dynatrace, New Relic. For example, New Relic provides RUM as a part of its Browser monitoring feature in which it captures, processes and visualizes the data in RUM dashboards.
SiteScope is agentless monitoring software focused on monitoring the availability and performance of distributed IT infrastructures, including Servers, Network devices and services, Applications and application components, operating systems and various IT enterprise components. SiteScope was originally written by Freshwater Software in 1996, a company acquired by Mercury Interactive in 2001. Mercury Interactive was subsequently acquired by Hewlett-Packard (HP) in 2006. Version 10.10 was released in July 2009. The current version is 2018.08 (11.51). SiteScope is now marketed by OpenText after its acquisition of Micro Focus. SiteScope tests a web page or a series of web pages using synthetic monitoring. However, it is not limited to web applications and can be used to monitor database servers (Oracle Database, Microsoft SQL Server, etc.), Unix servers, Microsoft Windows servers and many other types of hardware and software. It can export the collected data in real time to OpenText LoadRunner or it can be used in standalone mode.
Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.
MORE →Joe Louis.