About all

Apdex pain. Appendicitis: Causes, Symptoms, and Treatment – A Comprehensive Guide

What are the main causes of appendicitis. How can you recognize the symptoms of appendicitis. What treatment options are available for appendicitis. Why is prompt diagnosis crucial for appendicitis. How does chronic appendicitis differ from acute appendicitis. Who is at higher risk of developing appendicitis. What complications can arise from untreated appendicitis.

Содержание

Understanding Appendicitis: An Overview

Appendicitis is a common medical condition characterized by inflammation of the vermiform appendix, a small, finger-shaped pouch connected to the colon. This condition can be classified as either acute or chronic, with acute cases requiring immediate medical attention due to the risk of severe complications.

The appendix, although often considered vestigial, plays a role in maintaining gut health and supporting the immune system. When it becomes inflamed, it can lead to a range of symptoms that vary in severity and onset depending on whether the condition is acute or chronic.

Acute vs. Chronic Appendicitis

Acute appendicitis is characterized by rapid onset of symptoms, typically developing over 12 to 24 hours. The pain is often severe and requires urgent medical intervention. Chronic appendicitis, on the other hand, features milder symptoms that wax and wane over weeks, months, or even years.

  • Acute appendicitis: Rapid onset, severe symptoms, requires immediate treatment
  • Chronic appendicitis: Milder symptoms, fluctuating over time, may eventually become acute

The Root Causes of Appendicitis

Appendicitis develops when the lumen, or hollow inner region of the appendix, becomes obstructed. This blockage can occur due to various factors:

  • Fecal matter lodged in the appendix
  • Tumors obstructing the appendix or nearby gastrointestinal tract
  • Swollen lymphoid follicles
  • Foreign bodies
  • Parasites

Once blocked, the appendix becomes a breeding ground for bacteria, viruses, or parasites, leading to inflammation. As the appendix swells, it can compress nearby blood vessels, potentially cutting off its own blood supply. This ischemia weakens the appendix wall, increasing the risk of perforation or rupture in acute cases.

The Inflammatory Process

The inflammatory process in appendicitis follows a predictable pattern:

  1. Obstruction of the appendix lumen
  2. Bacterial overgrowth within the blocked appendix
  3. Inflammation and swelling of the appendix wall
  4. Reduced blood flow due to compression of blood vessels
  5. Potential weakening and perforation of the appendix wall

Recognizing the Symptoms of Appendicitis

Identifying the symptoms of appendicitis is crucial for timely diagnosis and treatment. While the presentation can vary, several key symptoms are commonly associated with this condition:

  • Abdominal pain, often starting around the navel and migrating to the lower right quadrant
  • Nausea and vomiting
  • Loss of appetite
  • Low-grade fever
  • Constipation or diarrhea
  • Abdominal bloating
  • Painful urination

Is abdominal pain always present in appendicitis? While abdominal pain is the most common symptom, its location and intensity can vary. In most cases, the pain begins as a dull sensation around the navel and gradually intensifies as it shifts to the lower right abdomen, a location known as McBurney’s point. However, it’s important to note that pain patterns can differ, especially in pregnant women or individuals with anatomical variations.

The Progression of Symptoms in Acute Appendicitis

Acute appendicitis typically follows a characteristic progression of symptoms:

  1. Initial vague discomfort around the navel
  2. Migration of pain to the lower right quadrant
  3. Intensification of pain over 12-24 hours
  4. Development of associated symptoms such as nausea, fever, and loss of appetite

Risk Factors and Epidemiology of Appendicitis

Appendicitis affects a significant portion of the population, with slightly higher prevalence in males compared to females. Understanding the risk factors can help in early identification and prevention of complications.

Age Distribution

Appendicitis exhibits a bimodal age distribution, meaning it has two peak incidence periods:

  • Primary peak: Ages 10-20
  • Secondary peak: Early 40s to mid-60s

While these age ranges show higher incidence, it’s crucial to remember that appendicitis can occur at any age.

Gender and Genetic Factors

Does gender influence the risk of appendicitis? Studies have shown that males have a slightly higher overall risk of developing appendicitis compared to females. The lifetime risk is approximately 8.6% for males and 6.7% for females.

Family history may play a role in predisposing individuals to appendicitis, particularly in male patients. However, more research is needed to fully understand the genetic components of this condition.

Diagnosing Appendicitis: Challenges and Approaches

Accurate diagnosis of appendicitis can be challenging due to the variability of symptoms and the potential for overlap with other conditions. Physicians employ a combination of clinical examination, laboratory tests, and imaging studies to reach a diagnosis.

Clinical Examination

The initial evaluation typically includes:

  • Detailed medical history
  • Physical examination, including abdominal palpation
  • Assessment of pain response to specific maneuvers (e.g., Rovsing’s sign, psoas sign)

Laboratory Tests

Blood tests can provide valuable information:

  • Complete blood count (CBC) to check for elevated white blood cell count
  • C-reactive protein (CRP) levels to assess inflammation
  • Urinalysis to rule out urinary tract infections

Imaging Studies

Various imaging techniques may be employed to visualize the appendix and surrounding structures:

  • Ultrasound: Often the first-line imaging choice, especially in children and pregnant women
  • CT scan: Provides detailed images and is highly accurate in diagnosing appendicitis
  • MRI: Used in cases where radiation exposure is a concern, such as in pregnant patients

How accurate are imaging studies in diagnosing appendicitis? While imaging studies significantly improve diagnostic accuracy, no single test is 100% conclusive. CT scans have the highest sensitivity and specificity, with accuracy rates above 90%. However, the choice of imaging modality often depends on factors such as age, pregnancy status, and availability of resources.

Treatment Options for Appendicitis

The treatment approach for appendicitis depends on the severity of the condition and whether it is acute or chronic. Prompt intervention is crucial to prevent complications, especially in acute cases.

Surgical Intervention

Appendectomy, the surgical removal of the appendix, remains the gold standard treatment for acute appendicitis. Two main surgical approaches are used:

  • Open appendectomy: Traditional method involving a larger incision
  • Laparoscopic appendectomy: Minimally invasive technique using small incisions and a camera

Laparoscopic surgery is generally preferred due to its advantages:

  • Shorter hospital stay
  • Faster recovery time
  • Reduced postoperative pain
  • Lower risk of wound infections

Conservative Management

In some cases of uncomplicated appendicitis, particularly in chronic cases, a non-surgical approach may be considered:

  • Antibiotic therapy
  • Close monitoring
  • Dietary modifications

Is conservative management effective for all cases of appendicitis? While antibiotics alone can successfully treat some cases of uncomplicated appendicitis, this approach carries a risk of recurrence and is not suitable for all patients. The decision between surgical and conservative management should be made on a case-by-case basis, considering factors such as the severity of symptoms, patient preferences, and overall health status.

Potential Complications of Untreated Appendicitis

Untreated appendicitis can lead to severe complications, underscoring the importance of prompt diagnosis and treatment. Some potential complications include:

  • Perforation: The appendix wall weakens and develops holes
  • Peritonitis: Infection spreads to the abdominal cavity
  • Abscess formation: Pockets of pus develop around the appendix
  • Sepsis: Widespread infection throughout the body
  • Gangrene: Death of appendix tissue due to lack of blood supply

How quickly can complications develop in untreated appendicitis? The risk of perforation increases significantly after 36-48 hours from the onset of symptoms. Once perforation occurs, the risk of life-threatening complications such as peritonitis and sepsis rises dramatically. This emphasizes the critical nature of early diagnosis and treatment.

Long-term Consequences

Even after successful treatment, appendicitis can have long-term implications:

  • Increased risk of adhesions and bowel obstruction
  • Potential for chronic abdominal pain
  • Fertility issues in women due to pelvic scarring

These potential long-term consequences further highlight the importance of timely and appropriate management of appendicitis.

Prevention and Future Directions in Appendicitis Management

While appendicitis cannot always be prevented, certain measures may help reduce the risk or improve outcomes:

  • Maintaining a healthy diet rich in fiber
  • Staying hydrated
  • Practicing good hygiene to prevent gastrointestinal infections
  • Seeking prompt medical attention for persistent abdominal pain

Emerging Research and Treatment Approaches

Ongoing research in the field of appendicitis is exploring new avenues for diagnosis and treatment:

  • Development of more accurate diagnostic biomarkers
  • Refinement of imaging techniques for improved accuracy
  • Investigation of novel antibiotic regimens for conservative management
  • Exploration of minimally invasive surgical techniques

What does the future hold for appendicitis treatment? As our understanding of appendicitis evolves, we may see a shift towards more personalized treatment approaches. This could include tailored antibiotic therapies based on individual patient characteristics and the use of advanced imaging technologies for more precise diagnosis. Additionally, ongoing research into the function of the appendix may lead to new strategies for preserving this organ when possible, potentially altering the current standard of care.

In conclusion, appendicitis remains a significant health concern that requires prompt recognition and appropriate management. By understanding its causes, recognizing its symptoms, and being aware of available treatment options, individuals can seek timely medical care and potentially avoid serious complications. As research progresses, we can expect to see continued improvements in the diagnosis and treatment of this common yet potentially serious condition.

Appendicitis: Causes, symptoms and treatment

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

The vermiform appendix extends off of the colon, also known as the large intestine.
(Image credit: SEBASTIAN KAULITZKI/SCIENCE PHOTO LIBRARY via Getty Images)

Appendicitis is inflammation of the vermiform appendix (or just the appendix, for short), a little structure within the lower gastrointestinal tract.

In appendicitis, the appendix swells, causing a condition that is classified as either acute or chronic. Both acute and chronic appendicitis are characterized by some of the same symptoms, especially abdominal pain. However, while chronic appendicitis features pain that waxes and wanes over periods of weeks, months or years, and that tends to be milder, acute appendicitis has symptoms that are more severe and emerge rapidly, typically over 12 to 24 hours

Acute appendicitis requires immediate treatment to avoid life-threatening complications.

What causes appendicitis?

Appendicitis develops when the lumen (the hollow, inner region of the vermiform appendix) becomes blocked or parts of the gastrointestinal tract to which the appendix is attached become blocked. Such blockages can result from material, such as a piece of fecal matter blocking the hollow interior of the appendix, or they may stem from the presence of a tumor.

This leads to an inflammatory reaction to infectious agents that become trapped inside the appendix, since the blockage prevents these agents from being cleared away by normal secretions and movements of bodily fluids. Usually, such an infection is caused by bacteria, but it also can be driven by a virus or parasite. 

The appendix then swells, causing pain, which is exacerbated when the swelling pushes on nearby blood vessels in a way that cuts off the blood supply to the appendix. Obstructed blood supply leads to ischemia, meaning a lack of blood flow to the tissue. This weakens the tissue, and in cases of acute appendicitis, this weakening can be drastic enough to put the appendix at risk of perforating (developing small holes) or even rupturing.  

Chronic appendicitis also features episodes of inflammation that can decrease blood supply to the appendix. However, any episode that reaches a level of severity bad enough to cause perforation is then called acute appendicitis and treated as such.

Risk factors for appendicitis

Appendicitis is fairly common: 8.6% of the male population and 6.7% of the female population will have the condition at some point in their lives. 

While a family history of appendicitis may be a risk factor for male patients, who have a slightly higher overall risk of the condition than female patients do, the only reliable predictor of risk for everyone is age. Appendicitis is most common between the ages of 10 and 20, and then there is another, smaller peak in older people that arises in the early 40s, peaks around age 65 and then gradually decreases again. This is called a bimodal age distribution. 

Although appendicitis most commonly occurs in the aforementioned age ranges, it’s important to keep in mind that the condition can occur at any age.  

Also, since chronic appendicitis is characterized by waxing and waning episodes, and since any such episode can potentially become acute, people who suffer from chronic appendicitis are also at risk for acute appendicitis.

What are the symptoms of appendicitis?

One of the main symptoms of appendicitis is abdominal pain. (Image credit: urbazon via Getty Images)

According to Johns Hopkins Medicine, the symptoms of appendicitis include the following:

  • abdominal pain
  • nausea
  • lack of appetite
  • vomiting
  • painful urination
  • fever

Pain is the dominant symptom of both chronic and acute appendicitis. As noted above, the pain waxes and wanes over weeks, months or years in cases of chronic appendicitis, whereas symptoms of acute appendicitis develop abruptly. 

Typically, the pain of acute appendicitis begins gradually as a dull sensation around the navel that develops over 12 to 24 hours. Then, the pain shifts to the right side of the lower abdomen, classically to a location that surgeons call the “McBurney’s point. ” It’s important to keep in mind, however, that many people experience variations of this classic pattern of pain progression, or patterns that are very different. Pregnancy notoriously makes the development of appendicitis confusing, because the growing womb shifts organs to different locations, making the McBurney’s point less likely to be the focus of the pain. 

It should be noted that a very small number of people carry their appendix on the left side of the body, instead of the right side, so it’s technically possible for pain in the lower left abdomen to be the result of appendicitis.

How is appendicitis diagnosed?

In evaluating patients for possible appendicitis, physicians and surgeons order blood tests to determine if the number of white blood cells, a type of immune cell, is elevated. Doctors also perform a physical examination in which the abdomen and legs are manipulated in certain ways to elicit classic signs of appendicitis, such as McBurney’s sign. But generally, they do not diagnose appendicitis based on the physical examination alone. 

To add to the information obtained from physical examination and blood tests, doctors order or perform imaging of the abdomen. Usually, the first imaging is ultrasound scanning to reveal if the appendix is swollen. If the ultrasound imaging does not give a clear result, doctors will order either computed tomography (CT) scanning or magnetic resonance imaging (MRI) of the abdomen to get a better look. Currently, CT is the most accurate method for confirming appendicitis.

Complications of appendicitis

In cases of acute appendicitis, the imaging and laboratory workup will be used not only to confirm that appendicitis is present but also to detect or rule out the following complications. The presence or absence of these complications determines whether nonsurgical treatment can be considered.

  • Perforation or rupture: One or more holes opens in the appendix, making it possible for the infection to spread through the abdomen and pelvis. This can lead to an abscess (the infection leaks out of the appendix but becomes enclosed in a ball of pus), peritonitis (the abdominopelvic cavity becomes infected) or sepsis (the infection spreads throughout the bloodstream).
  • An abscess on or near the appendix or elsewhere in the abdomen: As noted above, this is basically a swollen accumulation of pus.
  • Evidence of a possible tumor near the appendix, or within it.
  • An appendicolith: This term refers to a calcified deposit within the appendix. CT scanning is particularly good at revealing this.

Generally, the aforementioned complications are issues related to acute appendicitis, although it is sometimes possible for a small abscess to form in connection with chronic appendicitis.

How is appendicitis treated?

Appendicitis may require surgery. (Image credit: Science Photo Library via Getty Images)

If you have appendicitis with any of the above complications, surgery is mandatory, but there is no need to worry. Appendectomy is a safe, routine operation. In nearly all cases, such complications emerge in the setting of acute appendicitis, rather than chronic. If they do emerge in someone whose appendicitis has been chronic, the case is then considered to be acute, as explained previously.

Usually, the procedure is performed laparoscopically, meaning that surgeons make just a few very tiny incisions in the patient’s abdomen and the appendix is pulled from the body through a tube. Recovery from laparoscopic appendectomy (sometimes called “lap-appy”) is fairly rapid. In fact, because recovery is easy, a patient may decide, in consultation with their doctor, to have their appendix removed even if they have an uncomplicated case, for reasons that will be discussed below.

The idea that an inflamed appendix must always be removed dates back to the late 19th century, when antibiotics weren’t available and surgeons began performing appendectomies (removal of the appendix) routinely as a way to prevent death that would result if a swollen appendix perforated. Perforation is a feared complication because it can lead to abscess, peritonitis or sepsis, which can be fatal.  

Nowadays, however, many people with appendicitis don’t need surgery and can recover with just antibiotics.

Related stories

Nonsurgical treatment is appropriate for a certain fraction of appendicitis cases. Evidence shows that people with acute appendicitis who have not developed complications can receive only antibiotics, with a success rate of about 70%. This means that in about 70% of people who receive the right kind of antibiotics on the correct schedule to treat uncomplicated appendicitis, the appendicitis will clear and then not recur. Of course, this also means that about 30% of uncomplicated appendicitis cases treated nonsurgically will recur, so many people opt for surgical treatment even when they do not experience complications.

When it comes to chronic appendicitis, patients may experience episodes for years without developing complications. But even so, it’s not uncommon for doctors to offer antibiotics for flare-ups and to offer surgery to treat the condition, since removing the appendix ends the problem for good.

Scientists are evaluating the influence of age and other factors on the success rate of nonsurgical treatments for appendicitis. Treating the condition with antibiotics, alone, used to require that patients stay in the hospital and receive the drugs intravenously for 14 to 21 days. Today, however, doctors can successfully treat appendicitis by giving patients intravenous antibiotics for as few as four days and then antibiotic pills for seven to 10 days. These pills can be taken at home, so patients can be discharged from the hospital at that time.

This article is for informational purposes only and is not meant to offer medical advice.

Stay up to date on the latest science news by signing up for our Essentials newsletter.

Contact me with news and offers from other Future brandsReceive email from us on behalf of our trusted partners or sponsors

David Warmflash is a medical researcher, astrobiologist, science communicator, and author, located in Portland, Oregon. He holds an MD from Tel Aviv University Sackler School of Medicine and has conducted research in astrobiology, space biology, and space medicine during research fellowships at NASA’s Johnson Space Center, the University of Pennsylvania, and Brandeis University, and in collaboration with The Planetary Society and the Israeli Aerospace Medicine Institute.

  1. 1

    $500,000 chunk of ‘floating gold’ found in dead whale

  2. 2

    Scientists discover huge, heat-emitting blob on the far side of the moon

  3. 3

    Elite Bronze Age tombs laden with gold and precious stones are ‘among the richest ever found in the Mediterranean’

  4. 4

    The ‘man in the moon’ may be hundreds of millions of years older than we thought

  5. 5

    Kentucky man finds over 700 Civil War-era coins buried in his cornfield

  1. 1

    Zapotec ‘entrance to underworld’ discovered under Catholic church in Mexico

  2. 2

    Humans were in South America at least 25,000 years ago, giant sloth bone pendants reveal

  3. 3

    Nuclear bombs set off new geological epoch in the 1950s, scientists say

  4. 4

    Stone tools and camel tooth suggest people were in the Pacific Northwest more than 18,000 years ago

  5. 5

    $500,000 chunk of ‘floating gold’ found in dead whale

Appendicitis: Causes, symptoms and treatment

When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

The vermiform appendix extends off of the colon, also known as the large intestine.
(Image credit: SEBASTIAN KAULITZKI/SCIENCE PHOTO LIBRARY via Getty Images)

Appendicitis is inflammation of the vermiform appendix (or just the appendix, for short), a little structure within the lower gastrointestinal tract.

In appendicitis, the appendix swells, causing a condition that is classified as either acute or chronic. Both acute and chronic appendicitis are characterized by some of the same symptoms, especially abdominal pain. However, while chronic appendicitis features pain that waxes and wanes over periods of weeks, months or years, and that tends to be milder, acute appendicitis has symptoms that are more severe and emerge rapidly, typically over 12 to 24 hours

Acute appendicitis requires immediate treatment to avoid life-threatening complications.

What causes appendicitis?

Appendicitis develops when the lumen (the hollow, inner region of the vermiform appendix) becomes blocked or parts of the gastrointestinal tract to which the appendix is attached become blocked. Such blockages can result from material, such as a piece of fecal matter blocking the hollow interior of the appendix, or they may stem from the presence of a tumor.

This leads to an inflammatory reaction to infectious agents that become trapped inside the appendix, since the blockage prevents these agents from being cleared away by normal secretions and movements of bodily fluids. Usually, such an infection is caused by bacteria, but it also can be driven by a virus or parasite. 

The appendix then swells, causing pain, which is exacerbated when the swelling pushes on nearby blood vessels in a way that cuts off the blood supply to the appendix. Obstructed blood supply leads to ischemia, meaning a lack of blood flow to the tissue. This weakens the tissue, and in cases of acute appendicitis, this weakening can be drastic enough to put the appendix at risk of perforating (developing small holes) or even rupturing. 

Chronic appendicitis also features episodes of inflammation that can decrease blood supply to the appendix. However, any episode that reaches a level of severity bad enough to cause perforation is then called acute appendicitis and treated as such.

Risk factors for appendicitis

Appendicitis is fairly common: 8.6% of the male population and 6.7% of the female population will have the condition at some point in their lives. 

While a family history of appendicitis may be a risk factor for male patients, who have a slightly higher overall risk of the condition than female patients do, the only reliable predictor of risk for everyone is age. Appendicitis is most common between the ages of 10 and 20, and then there is another, smaller peak in older people that arises in the early 40s, peaks around age 65 and then gradually decreases again. This is called a bimodal age distribution. 

Although appendicitis most commonly occurs in the aforementioned age ranges, it’s important to keep in mind that the condition can occur at any age. 

Also, since chronic appendicitis is characterized by waxing and waning episodes, and since any such episode can potentially become acute, people who suffer from chronic appendicitis are also at risk for acute appendicitis.

What are the symptoms of appendicitis?

One of the main symptoms of appendicitis is abdominal pain. (Image credit: urbazon via Getty Images)

According to Johns Hopkins Medicine, the symptoms of appendicitis include the following:

  • abdominal pain
  • nausea
  • lack of appetite
  • vomiting
  • painful urination
  • fever

Pain is the dominant symptom of both chronic and acute appendicitis. As noted above, the pain waxes and wanes over weeks, months or years in cases of chronic appendicitis, whereas symptoms of acute appendicitis develop abruptly. 

Typically, the pain of acute appendicitis begins gradually as a dull sensation around the navel that develops over 12 to 24 hours. Then, the pain shifts to the right side of the lower abdomen, classically to a location that surgeons call the “McBurney’s point.” It’s important to keep in mind, however, that many people experience variations of this classic pattern of pain progression, or patterns that are very different. Pregnancy notoriously makes the development of appendicitis confusing, because the growing womb shifts organs to different locations, making the McBurney’s point less likely to be the focus of the pain. 

It should be noted that a very small number of people carry their appendix on the left side of the body, instead of the right side, so it’s technically possible for pain in the lower left abdomen to be the result of appendicitis.

How is appendicitis diagnosed?

In evaluating patients for possible appendicitis, physicians and surgeons order blood tests to determine if the number of white blood cells, a type of immune cell, is elevated. Doctors also perform a physical examination in which the abdomen and legs are manipulated in certain ways to elicit classic signs of appendicitis, such as McBurney’s sign. But generally, they do not diagnose appendicitis based on the physical examination alone. 

To add to the information obtained from physical examination and blood tests, doctors order or perform imaging of the abdomen. Usually, the first imaging is ultrasound scanning to reveal if the appendix is swollen. If the ultrasound imaging does not give a clear result, doctors will order either computed tomography (CT) scanning or magnetic resonance imaging (MRI) of the abdomen to get a better look. Currently, CT is the most accurate method for confirming appendicitis.

Complications of appendicitis

In cases of acute appendicitis, the imaging and laboratory workup will be used not only to confirm that appendicitis is present but also to detect or rule out the following complications. The presence or absence of these complications determines whether nonsurgical treatment can be considered.

  • Perforation or rupture: One or more holes opens in the appendix, making it possible for the infection to spread through the abdomen and pelvis. This can lead to an abscess (the infection leaks out of the appendix but becomes enclosed in a ball of pus), peritonitis (the abdominopelvic cavity becomes infected) or sepsis (the infection spreads throughout the bloodstream).
  • An abscess on or near the appendix or elsewhere in the abdomen: As noted above, this is basically a swollen accumulation of pus.
  • Evidence of a possible tumor near the appendix, or within it.
  • An appendicolith: This term refers to a calcified deposit within the appendix. CT scanning is particularly good at revealing this.

Generally, the aforementioned complications are issues related to acute appendicitis, although it is sometimes possible for a small abscess to form in connection with chronic appendicitis.

How is appendicitis treated?

Appendicitis may require surgery. (Image credit: Science Photo Library via Getty Images)

If you have appendicitis with any of the above complications, surgery is mandatory, but there is no need to worry. Appendectomy is a safe, routine operation. In nearly all cases, such complications emerge in the setting of acute appendicitis, rather than chronic. If they do emerge in someone whose appendicitis has been chronic, the case is then considered to be acute, as explained previously.

Usually, the procedure is performed laparoscopically, meaning that surgeons make just a few very tiny incisions in the patient’s abdomen and the appendix is pulled from the body through a tube. Recovery from laparoscopic appendectomy (sometimes called “lap-appy”) is fairly rapid. In fact, because recovery is easy, a patient may decide, in consultation with their doctor, to have their appendix removed even if they have an uncomplicated case, for reasons that will be discussed below.

The idea that an inflamed appendix must always be removed dates back to the late 19th century, when antibiotics weren’t available and surgeons began performing appendectomies (removal of the appendix) routinely as a way to prevent death that would result if a swollen appendix perforated. Perforation is a feared complication because it can lead to abscess, peritonitis or sepsis, which can be fatal.  

Nowadays, however, many people with appendicitis don’t need surgery and can recover with just antibiotics.

Related stories

Nonsurgical treatment is appropriate for a certain fraction of appendicitis cases. Evidence shows that people with acute appendicitis who have not developed complications can receive only antibiotics, with a success rate of about 70%. This means that in about 70% of people who receive the right kind of antibiotics on the correct schedule to treat uncomplicated appendicitis, the appendicitis will clear and then not recur. Of course, this also means that about 30% of uncomplicated appendicitis cases treated nonsurgically will recur, so many people opt for surgical treatment even when they do not experience complications.

When it comes to chronic appendicitis, patients may experience episodes for years without developing complications. But even so, it’s not uncommon for doctors to offer antibiotics for flare-ups and to offer surgery to treat the condition, since removing the appendix ends the problem for good.

Scientists are evaluating the influence of age and other factors on the success rate of nonsurgical treatments for appendicitis. Treating the condition with antibiotics, alone, used to require that patients stay in the hospital and receive the drugs intravenously for 14 to 21 days. Today, however, doctors can successfully treat appendicitis by giving patients intravenous antibiotics for as few as four days and then antibiotic pills for seven to 10 days. These pills can be taken at home, so patients can be discharged from the hospital at that time.

This article is for informational purposes only and is not meant to offer medical advice.

Stay up to date on the latest science news by signing up for our Essentials newsletter.

Contact me with news and offers from other Future brandsReceive email from us on behalf of our trusted partners or sponsors

David Warmflash is a medical researcher, astrobiologist, science communicator, and author, located in Portland, Oregon. He holds an MD from Tel Aviv University Sackler School of Medicine and has conducted research in astrobiology, space biology, and space medicine during research fellowships at NASA’s Johnson Space Center, the University of Pennsylvania, and Brandeis University, and in collaboration with The Planetary Society and the Israeli Aerospace Medicine Institute.

  1. 1

    $500,000 chunk of ‘floating gold’ found in dead whale

  2. 2

    Scientists discover huge, heat-emitting blob on the far side of the moon

  3. 3

    Elite Bronze Age tombs laden with gold and precious stones are ‘among the richest ever found in the Mediterranean’

  4. 4

    The ‘man in the moon’ may be hundreds of millions of years older than we thought

  5. 5

    Kentucky man finds over 700 Civil War-era coins buried in his cornfield

  1. 1

    Zapotec ‘entrance to underworld’ discovered under Catholic church in Mexico

  2. 2

    Humans were in South America at least 25,000 years ago, giant sloth bone pendants reveal

  3. 3

    Nuclear bombs set off new geological epoch in the 1950s, scientists say

  4. 4

    Stone tools and camel tooth suggest people were in the Pacific Northwest more than 18,000 years ago

  5. 5

    $500,000 chunk of ‘floating gold’ found in dead whale

How to reduce the dimension of metrics in Prometheus if you are not DevOps

Publications

July 1, 2021

Sometimes the development team is faced with a task in which they have little expert experience, and through trial and error they find a non-obvious solution. This happened to us when we needed to transfer the collection of metrics from Infux to Prometheus. Their final dimension turned out to be 1.5 million, and we decided to reduce it. The infrastructure for collecting metrics (Prometheus, k8s, deploy via Helm) was created by DevOps engineers from another team who did not have the resources for our task. Therefore, we enlisted their advice, studied the documentation, and decided to reduce the dimension of metrics by development forces.

This article is not suitable for experienced DevOps engineers, but it will be useful for developers who want to reduce the metrics dimension and do not want to dive into the documentation. Or those who deliberately refuse hierarchical federation and are looking for a workaround, but do not want to step on our rake. Let’s tell:

  • how to reduce the dimension of metrics in two steps using two ServiceMonitors,
  • what is the reference way to reduce the dimension of metrics without “crutches”,
  • why you shouldn’t spend time reducing metrics with Pushgateway.

Why it was necessary to reduce the dimension of metrics

Our team is responsible for one of the Mindbox products — product recommendations on the website and in mailing lists. We collected real-time recommendation processing time in Influx, and in order to help the business evaluate the performance of the product, we also needed to calculate the Apdex (Application Performance Index). The company is gradually transferring metrics from Influx to Prometheus, so we decided to collect both metrics at once in Prometheus using histograms.

A bar chart with metrics that we wanted to create to evaluate the performance of products

Our services are deployed in Kubernetes. We collect metrics in Prometheus using ServiceMonitor. We use Prometheus.NET in the application. In the default configuration, each metric exported by a pod is appended with a pod label with the corresponding value.

Collecting metrics in Prometheus using ServiceMonitor

To display the average processing time, percentiles (p50, p95, p99) and Apdex planned to use a histogram with 20 buckets. Taking into account the fact that we wanted to receive information regarding each of the 2.5 thousand recommendation mechanics, the total dimension of the metrics was 50 thousand. Pod names change on every show and a pod label is assigned to every metric, so with a 30-day retention and a daily show, the dimension grows to 1.5 million. A metric with this dimension took up much more space in Prometheus than we wanted.

2500 * 20 * 30 = 1 500 000
(number of mechanics) * (number of histogram buckets) * (retention) = (final dimension)

We decided to get rid of the pod and instance label so that the dimension does not increase on the calculations. At the same time, we tried to find a simple and cheap solution that can be implemented and maintained without the involvement of a DevOps engineer.

An important assumption: the metric for which we wanted to reduce the dimension is collected from only one pod at a time. The pod can change only when the application is restarted, for example, when laying out.

What solutions were considered

Let’s make a reservation right away that hierarchical federation is most suitable for solving problems with dimension; the documentation for it describes in detail examples of use. We could deploy Prometheus with a low metrics retention and collect the original metrics there. Then, through the recording rules, calculate the aggregates and collect them into another Prometheus with a high data retention.

We didn’t consider federation because we wanted to find a simpler, cheaper, and faster solution. In addition, developers, not DevOps, had to work on the task, so I wanted to use familiar tools and techniques. Although practice has shown that we spent time looking for such a solution, during which it was possible to make a federation, and our implementation turned out to be a “crutch”.

We formulated two equivalent solutions:

1. Raise Pushgateway and push metrics there without labels. The company already had a helm chart for stack monitoring, including for Pushgateway.

Pros: code and charts can be reused, metrics can be transferred to the raised Pushgateway from other team servers that are outside Kubernetes and have not yet moved from Influx to Prometheus.

Cons: more expensive support.

Collecting metrics in Prometheus using Pushgateway

2. Raise the second ServiceMonitor and configure routing of metrics between them. In one, remove pod/instance labels through relaying, and in the other, leave them as they are.

Pros: is cheaper – you just need to deploy ServiceMonitor, easier to maintain.

Cons: ops implementation that the developers were not familiar with.

Collecting metrics in Prometheus using the second ServiceMonitor

How the Pushgateway solution failed

First solution. To begin with, we chose the obvious implementation through Pushgateway. We raised Pushgateway, pushed metrics there and used the instance constant as a label. The request looked something like this:

We quickly coped with the task and at first the result was pleasing – the metrics were collected, but the dimension did not grow. But soon we began to notice large gaps in the metrics of some mechanics. At the same time, a strange pattern was observed – when for some mechanics the metric was transmitted correctly and continuously, for others, failures began. Because of this, it seemed that only one group of mechanics was reporting at a single moment in time. There were several such groups, and they changed randomly.

Why didn’t it work. Those who are familiar with the Pushgateway device probably immediately realized that our solution was not working. In Pushgateway, labels are passed in two ways: through the request path or in the request body. At the same time, the set of labels and their values ​​that are passed through the path act as a key for the dictionary where the metrics are stored. Everything passed through the request body gets into the value by this key. That is, in our case, each request from the pod overwrote all the metrics that were pushed from other pods. Since Prometheus collects metrics at intervals, it only got metrics from the pod that was last pushed.

To correctly send metrics to Pushgateway, you would have to write custom C# code. But such a solution was neither simple nor cheap, so it was abandoned.

Second solution. We decided to cling to Pushgateway again: collect initial metrics and push with all labels, and then remove the pod label using ServiceMonitor, which collects metrics from Pushgateway. But already at the start they realized that the idea would not work.

Why didn’t they implement it. Pushgateway has several features that make this solution impossible. Main – data is not cleared automatically, by retention. This means that you need to track the size of the disk and write cleanup code manually. Another problem is that after relaying, metrics with the same set of labels, but with a different pod label, will conflict. As a result, only the last metric in the Pushgateway order will remain. At the same time, the metrics are sorted not by the date of the last change, but in alphabetical order. So, when uploading values ​​from new pods, they may not get into Prometheus.

How the solution worked with the second ServiceMonitor

We returned to the second original version and made two ServiceMonitors. Additionally, a special label was affixed in the code (in our case, business) for those metrics whose dimension we are reducing:

  • on one ServiceMonitor, all metrics with a special label were discarded, and the rest were left as they are;
  • on the other, only metrics with a special label were left and the pod and instance labels were removed from them.

We did everything through relaying, the code was added to the configuration of the first ServiceMonitor:

The code was added to the configuration of the second ServiceMonitor:

What we learned from the story of finding solutions

  1. Neither Pushgateway directly nor its relabeling are suitable for metric reduction.
  2. If relaying is used, then metrics with the same set of labels should not be simultaneously reported from different pods.
  3. The second ServiceMonitor is a “crutch” that is easy and quick to implement if you don’t want to waste resources on federation.
  4. The best solution for reducing the dimensionality of metrics is federation:
    • Prometheus low retention,
    • assemble aggregates (recording rules),
    • is sent to Prometheus with high retention.
  • Development

  • Developer

    Yuri Sokolov

  • Editor

    Anastasia Sikorskaya

General system performance | qaload.

github.io

General system performance

Books
  • Systems Performance: Enterprise and the Cloud – Brendan Gregg (En)
  • The Art of Application Performance Testing – Ian Molyneaux (En)
Talks
  • Load testing of a typical Internet service – Andrey Pokhilko (Rus)
  • From load testing service to competence center – Ural Nurgalin (Rus)
  • Complexity of performance testing – Andrey Akinshin (Rus)
  • Fair performance testing – Dmitry Pivovarov (Rus)
  • Bottleneck – Mikhail Epihin (Rus)
  • Learning to analyze the results of load testing – Alexey Lavrenyuk (Rus)
  • Speeding up Apache JMeter – Vyacheslav Smirnov (Rus)
  • Cloud Performance Root Cause Analysis at Netflix – Brendan Gregg (En)
  • Linux Performance – Brendan Gregg (En)
  • Pitfalls in load testing – Vladimir Sitnikov (Rus)
  • Atlassian Jira load testing – Alexey Matveev (Rus)
Articles
  • Methodology and practice of load testing. Miro experience – Dmitry Vinokurov (Rus)
Analyzing performance methods
  • The USE Method
  • The TSA Method

Java application performance

Books
  • Optimizing Java: Practical Techniques for Improving JVM Application Performance (En)
Talks
  • Java Benchmarking: how to read two timestamps! – Alexey Shipilev (Rus)
  • Performance: What’s In Your Name? – Alexey Shipilev (Rus)

Data analysis

Books
  • Statistics and cats – Vladimir Saveliev (Rus)

Load Testing Knowledge Base

Material in the process of filling and editing

What is load testing?
  • Glossary
  • Introduction to NT Theory
  • Types of tests
  • Load profile
  • Related papers
    Develop test scripts and stubs
  • Apache JMeter script examples
  • Gatling script examples
  • Apache JMeter plugins
    Documentation
    Running tests
    Collection and analysis of metrics/logs
    Test data generation
    Study of system operation
    Stand setup
    Stress Testing Tools
    Monitoring
    Workplace preparation
    Automation
  • Reports

What is load testing?

Glossary
  • ISTQB – English Glossary of Iternation Software Testing Qualifications Board terms. Unfortunately, there are a number of controversial terms and definitions that either do not reveal the essence or contradict other sources.
  • RSTQB – similar to the previous Russian glossary Russian Software Testing Qualifications Board
Introduction to NT Theory

Load Testing (LT) – a type of testing in which we check whether our system meets the delivered
non-functional requirements when working under high load.

Compared to functional testing, HT is more complex than just success/fail testing.
It is much more complex and the results are a lot of metrics and graphs that need to be analyzed in order to be able to
was to conclude how well the system works in different situations.

What you need for HT
Requirements

Requirements should be as specific as possible and cover many situations.

An example of a bad requirement is “pages should load quickly”.

An example of a good requirement is “ such and such a page must open faster than 100ms for 75% of cases, faster than 500ms
for 95% of cases and faster than 1s for 99% of cases
“.

Specialists

The larger the scale, the stronger the division into narrower specializations, but in general, it was necessary for NT engineers
have the following roles:

  1. QA – be able to find problem areas and build a quality assurance process.
  2. Analyst – be able to identify cause and effect relationships, explore user behavior patterns and understand
    complex systems.
  3. Developer – be able to design and program automation tools and test scripts.
  4. DevOps – be able to navigate the architecture of the test environment and modify it.
Tools
  1. Load Generator: JMeter, Gatling, k6, Locust….
  2. Cluster management tools (AWS API and similar, native tools, etc.).
  3. Monitoring tools and tools for storing and visualizing metrics and logs (Prometheus / InfluxDB + Grafana, ELK etc).
  4. A tool for compiling and storing reports.
  5. Command line tools, spreadsheets, etc.
Test environment

Test environment includes:

  1. Target system – should be as close as possible to the product, namely, match its hardware resources (CPU, RAM
    etc), databases (at least in terms of etc)
  2. Load Cluster – with hosted load generators and monitoring tools
Stages
  1. Statement of requirements (what is required from the system?).
  2. Preparing a scenario (how will we reproduce the tested user behavior and what application metrics will we collect?).
  3. Preparing a test environment (what will we test on and what system metrics will we collect?).
  4. Conducting a test and measurement (what are the values ​​of the collected metrics?).
  5. Analysis (does the system meet the requirements, what are the problems and what causes them?).
  6. Report (what knowledge did we get?).
  7. System improvement plan * (how to fix problems?) – not always in the competence of NT, it is better to ask the functional teams
    or DevOps/SRE team.
Automation steps
  1. “Manual” start (target system, test script and load feeding cluster start manually, results
    assembled by hand)
  2. Tests run with minimal automation (one script/set of scripts and target system with feed cluster
    loads are lifted and the script is run and the results are collected).
  3. Tests are manually launched via the web interface for a certain software version + a beautiful report is created.
  4. CI/CD integration.
  5. Degradation tests.
  6. Robots do all the routine, humans only focus on really difficult situations more exploratory
    nature: profiling, chaos testing, etc.
Main metrics and their analysis

As mentioned in the introduction, we need to collect scenario-specific and system-wide metrics. Engineers from
Google shared their experience and described the “4 golden signals”
which are groups of metrics that cover almost everything we need to analyze:

  1. Latency.
  2. Traffic.
  3. Errors.
  4. Saturation.

These types of metrics are described below with additional explanations for some of them.

Latency

This is the request processing time, from the moment the client sends the request to the moment the client receives a response. Low latency –
the user is happy. The latency of successful requests must be separated from the latency of failed requests. Mistakes can
return very quickly (simply due to loss of connection to the database for example) and this can significantly affect
statistics. Slow failed requests are even worse.

This metric is what the user notices first (if the system is accessed at all, huh), so we’ll break it down
it in a little more detail.

Mean and deviations

The system is required to respond quickly and correctly to user requests. And if the correctness of the answers is rather
to functional testing, speed is just our concern. But “the system must respond quickly” is a weak
requirement. Let’s see why. If we look at this response time graph below, we won’t be able to tell if
how fast the system responds under a given load:

We can check the average response time, but if we look only at this average, we can draw wrong conclusions.
For example, in the graph below, the average response time may be quite satisfactory for us (284 ms), but this does not say
nothing to us about the jumps that exist and can be critical for us:

Standard deviation (or variance == squared standard deviation) can help us. In the next chart, we
we see the mean (red line) plus (yellow line) or minus (green line) standard deviation. Actually
In fact, the mean minus the standard deviation is negative in our case, but this does not make sense, so this
value is taken as zero.

Now we see some score telling us about some volatility. But just like the average value is not very
revealingly, the standard deviation, being “mean variability” is not very suitable for all distributions
random variables. It’s good for a normal distribution, but our response times are not necessarily normal.
distributed.

Percentiles

Percentiles fit much better. But to use them, you need to formulate several requirements. For example,
50% of queries should be completed in less than 100ms, 95% in less than 400ms and 99% in less than 1s. Below is an example
a graph that displays these percentiles and you can see how the response time meets the requirements, simply
comparing the percentile values ​​with the required:

As you can see, the percentiles are higher than in our requirements.

Comparison of several versions of

Now suppose we have made two optimized versions. Compare with original graph:

Looking at the response time graph, we can certainly say that the red line v2 looks better than the blue v1, and the yellow
v3 looks better than red v2. But we need to not just roughly say which is better, but determine it with confidence,
and it is better to calculate how much better. To do this, we can sort the response times and get a graph like this:

This graph makes it easier for us to work with percentiles. Please note that here we have 100 measurements and therefore we can
don’t aggregate data for percentiles, but in the real case you’ll need it.

Now we can clearly say that yellow line v3 is the best option, but how much better? To answer this, we
we can calculate (by integrating the values ​​of the points of the graphs) the areas marked “1” and “2” in the graph below. Area “1”
shows how much v2 is better than v1, area “2” shows how much v3 is better than v2, and the sum of “1” and “2” shows how much v3 is better than v1.

APDEX

APDEX (Application Performance inDEX – application performance index) – open
a standard that defines a method for evaluating and comparing a variety of metrics from application response time to quality
food and more.

APDEX example – automated comparison of results from multiple test runs.

Let’s imagine that we have a graph of the response time of some endpoint. And there is a graph for the second version of the algorithm
same endpoint. Let’s look at them together:

Of course, it seems that the red line is better, but is it visible to a person, but to a machine? You can use percentiles, or you can
APDEX.

Here is the scheme of its calculation:

Let’s take the following gradation:

  1. Satisfied time: <=200 ms
  2. tolerating time: <=300 ms
  3. frustrated time: >300 ms

and applicable to our data.

Get (believe me):

  1. First version (blue line) – 0.525
  2. Second version (red line) – 0.75

APDEX levels:

  1. 0.00..0.50 – not acceptable
  2. 0.50..0.70 – unsatisfactory
  3. 0.70..0.85 – satisfactory
  4. 0.85..0.94 – good
  5. 0.94..1.00 – excellent

Simple, measurable, comparable. Not so easy to interpret as percentiles, but nonetheless.

Traffic

For traditional APIs, traffic can be measured by requests per second (RPS).
High RPS (with low response time) – many satisfied customers. It may be useful to distinguish between static and
dynamic resources. For streaming systems, you can monitor the I / O frequency and the number of parallel sessions. For
key-value stores – the number of transactions and requests per second.

Errors

Obviously, few errors are good (with low response times and heavy traffic). But HTTP protocol codes can
be insufficient to express all statuses. For example, an HTTP-200 might be sent for a response with bad content.
And HTTP-500 from the balancer can be both a balancer error and an error on the worker, and it is important to distinguish between these
situations. Although load testing is not functional testing, it can still be important to check
goes deeper than just looking at HTTP codes to make sure the system is not only fast, but
correctly.

Saturation

Shows how “full” your servers and the system as a whole are. Many metrics belong to this type, here are some:

  1. CPU utilization.
  2. Amount of free memory.
  3. Amount of free disk space.
  4. I/O metrics, including network.
  5. Number of descriptors used.
  6. Number of worker servers.
Types of tests
Smoke tests

The simplest tests are just to check that the test works on the desired configuration and we collect all the necessary
metrics. Light load, short working time.

Closed and open test models
  1. Closed – Users wait for previous requests to complete before submitting new ones. This web is similar to the usual
    store with several sellers and a queue of buyers.
  2. Open – Users come and go without waiting for previous requests to complete. This is the real web.
Volume Load Tests

In volume tests, we check our system for response time and other metrics described in
section “Main metrics”, with a certain amount of load, that is, with a certain frequency of requests and
their distribution, which corresponds to the actual use of the system. This volume is determined by the requirements for
system and usually corresponds to some expectations of the future level of load on the system that we must withstand,
providing a comfortable working environment for users.

Limit tests

Let’s say our system is compliant and the servers are responding fast enough for a certain expected number
users. Now we want to go beyond the expected amount of load and see if our system can handle
a significantly larger number of users with the same load profile that we see in the prod. To do this, we gradually
we increase the load on our service and look at the metrics to find the point at which the system stops working
good enough. Here the graph shows 95% percentile of response time for one of the types of requests relative to
simulated number of users:

As we can see here, the response time starts to increase dramatically with a load of more than about 250 users (we have in this
example is a very simple system, yes). Therefore, we decided to slightly improve our system and of course we need to compare two
versions. To do this, we build the results on the same graph as for the first version, only we also add 95%
percentile for the second version. Anything can be, for example we can get improved response time for high
loads, but lose speed at low loads, as shown in the graph below:

But as it was said in the “Main Metrics” section, it is not enough to judge based on only one percentile value,
so it’s better to plot multiple percentiles for each version of the system. Here is an example of three percentiles for
one of the system versions:

Stability tests

If we find that the system meets the expected load volume and works correctly up to certain limits, we
you need to check whether the system is stable enough to withstand the load over a long period of time. For check
this, for example, we can check for memory leaks. In the following graph example, the load is stable, but the consumption
memory grows and grows, which indicates a leak and this will require additional parsing:

Scalability tests

We definitely want to know that in the event of a greatly increased load on our system, we will be able to adapt it to the new
load simply by increasing the number of servers. For this, scalability tests are performed. For example, you can take one
indicator (or better several) and check it on a different number of servers. For such a test, we can get a graph,
similar to this:

In this example graph, we can see that scaling from 1 server to 2 and 4 is good enough, but for 8 servers
score is not much different from 4.

Load Boost Tests

It is not uncommon for a situation where a link to our system was placed on some large site or because of some
another reason, many users immediately switched to us. Our system must be prepared for a very sharp increase in the number
users. This test is related to scalability and limits tests, but we need to check that our system is not
simply scalable, but rapidly scalable, and not only can show good performance with atypical
high load, and quickly adapt to it.

Recovery tests

If there was some kind of major outage, for example if one or more of our servers went down or
disconnected, our system system must be ready for such an event without trouble for users. System
should quickly redirect users to the remaining servers and scale to more servers if
need to. When the failed servers come back online, the system should quickly return to normal operation.

Component Interaction Tests

Most services consist of several components (this is especially critical for microservice architecture) and more
one important test is to check whether the components of our system interact well or badly with each other.

Load Profile
Reports on topic
  • Load testing from scratch – Kirill Yurkov

Development of test scripts and stubs

Apache JMeter 9 Script Examples0156
Gatling script examples
Apache JMeter plugins
  • JMeter Plugins – a large selection of plugins for jmeter

Documentation

Stress Testing Method (MNT)
Execution of the report and instructions

NT requires a very large amount of resources and to ensure that these resources are not wasted and to extract the maximum
benefits from the conducted NT, a good report is needed. So what are the criteria for a good report? Benefits for different people
report depends on the availability of answers to the relevant questions:

  1. For the manager, how the system meets the requirements, whether there is a reserve and what situation can cause problems with
    system?
  2. For DevOps, are there any weaknesses in the system on the infrastructure side.
  3. For developers – are there any weaknesses in the system from the code side.
  4. For the NT engineer, which NT tools were used with what settings, which script was used, on which
    infrastructure configuration was tested. All this knowledge, including in order to be able to reproduce
    script for any code or infrastructure changes for comparison.

No report – NT wasted!

Running tests

Collection and analysis of metrics/logs

System behavior patterns under load
“Saw”

Jumps of the indicator significantly up/down, may indicate the saturation of some resource to the limit and the fall of a number of agents,
raising new ones and repeating the situation.

“Shelf”

It may indicate that we have reached some limit and the system cannot cope further, although it does not fall. Here it is necessary
also look at the state of the load generators, maybe more than this limit and they do not load and this is not an error, but simply
reaching the level of the possible. It can also be just a limit value, above which to rise in principle
impossible, such as CPU usage, such cases require special attention.

Splash

Just a sudden jump, the cause of which may need to be investigated. It can be, for example, just suddenly launched
garbage collection.

Sharp drop

For example, at the beginning of the test, with a gradual increase in load, one of the traffic-generating workers may die. Or
it could be a graph of the total RPS for the whole cluster and one server could fail.

Smooth degradation

92) and the like.

Test data generation

System study

Stand setup

Load testing tools

Monitoring

Workplace preparation

Automation

Reports
  • NT automation is cheap and painful Kirill Yurkov – Jenkins, JMeter and Grafana
  • Ready-made autoreport template in JMeter + large dashboard – Confluence, JMeter and Grafana test trends and transition to the test by link.