<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Debug School: Rajesh Kumar Samal</title>
    <description>The latest articles on Debug School by Rajesh Kumar Samal (@rksamal29).</description>
    <link>https://www.debug.school/rksamal29</link>
    <image>
      <url>https://www.debug.school/images/qzBfUm3Ah6vJt3F-iOD5wRHF4QKXwqdzAA2jzN-ezz8/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly93d3cu/ZGVidWcuc2Nob29s/L3VwbG9hZHMvdXNl/ci9wcm9maWxlX2lt/YWdlLzY2My9jYTA3/MmRiZC0zYzIwLTQx/NTUtOTBhYS00NzBj/MjlkYzQ0YWUuanBn</url>
      <title>Debug School: Rajesh Kumar Samal</title>
      <link>https://www.debug.school/rksamal29</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/rksamal29"/>
    <language>en</language>
    <item>
      <title>Datadog –Day-4- 14-Sept–23- Assignment 1</title>
      <dc:creator>Rajesh Kumar Samal</dc:creator>
      <pubDate>Thu, 14 Sep 2023 04:56:14 +0000</pubDate>
      <link>https://www.debug.school/rksamal29/datadog-day-4-14-sept-23-assignment-1-j4j</link>
      <guid>https://www.debug.school/rksamal29/datadog-day-4-14-sept-23-assignment-1-j4j</guid>
      <description>&lt;h2&gt;
  
  
  1 Top 10 metrics/indicators for APM  ?
&lt;/h2&gt;

&lt;p&gt;Response Time: Measure the time it takes for your application to respond to user requests. This is crucial for user experience.&lt;br&gt;
Latency: Measure the delay between a request and its corresponding response to identify network and application performance issues.&lt;br&gt;
Transaction Tracing: Trace the path of transactions across various components of your application to pinpoint bottlenecks and slowdowns.&lt;br&gt;
Error Rate: Monitor the frequency of errors occurring in your application. High error rates can indicate problems that need immediate attention.&lt;br&gt;
Resource Utilization: Monitor CPU, memory, disk, and network usage to identify resource bottlenecks and optimize resource allocation.&lt;br&gt;
Throughput: Track the number of transactions or requests your application can handle per unit of time. It helps gauge your system's capacity.&lt;br&gt;
Apdex Score: Calculate the Application Performance Index (Apdex) score to assess user satisfaction with application response times.&lt;br&gt;
Dependency Analysis: Analyze dependencies between different components and services to identify potential issues and optimize performance.&lt;br&gt;
Error Details: Dig deeper into error data to understand the root causes of issues and prioritize debugging efforts.&lt;br&gt;
Real User Monitoring (RUM): Collect real user data, such as page load times and interactions, to gain insights into how actual users experience your application.&lt;/p&gt;

&lt;h2&gt;
  
  
  2 Top 10 metrics/indicators for Synthetic monitoring ?
&lt;/h2&gt;

&lt;p&gt;Error Rate: Keep an eye on the rate at which synthetic transactions encounter errors or failures.&lt;br&gt;
Response Time: Measure the time it takes for synthetic transactions to complete and assess whether they meet predefined thresholds.&lt;br&gt;
synthetics.test_run_steps (count): The number of Synthetic test steps.&lt;br&gt;
Availability/Uptime: Monitor the percentage of time an application or website is accessible and available to users.&lt;br&gt;
Transaction Success Rate: Track the percentage of synthetic transactions that complete successfully without errors.&lt;br&gt;
Transaction Paths: Monitor the sequence of steps within synthetic transactions to identify bottlenecks or issues in critical user flows.&lt;br&gt;
Transaction Completion Time: Monitor the time it takes for specific synthetic transactions (e.g., login, checkout) to finish successfully.&lt;br&gt;
Page Load Time: Measure how long it takes for web pages to fully load, including all resources such as images, scripts, and stylesheets.&lt;br&gt;
Geographic Performance: Assess how response times vary across different geographical locations to identify regional performance issues.&lt;br&gt;
Content Validation: Verify the content displayed during synthetic transactions to ensure it matches expected results, helping to detect unexpected changes or defacements.&lt;br&gt;
Third-Party Service Performance: Evaluate the performance of third-party services and APIs integrated with your application, as they can impact overall performance.&lt;/p&gt;

&lt;h2&gt;
  
  
  3 Top 10 metrics/indicators for RUM  ?
&lt;/h2&gt;

&lt;p&gt;Page Load Time: Measure the time it takes for web pages to fully load in a user's browser, including all resources (images, scripts, stylesheets).&lt;br&gt;
Page Views: Track the number of pages viewed by users to understand engagement and navigation patterns.&lt;br&gt;
First Contentful Paint (FCP): Monitor the time it takes for the first piece of content to be rendered on a web page, providing a user with visual feedback.&lt;br&gt;
Bounce Rate: Monitor the percentage of users who leave the website after viewing only one page, which can indicate user dissatisfaction.&lt;br&gt;
Time to Interactive (TTI): Measure how long it takes for a web page to become fully interactive, where users can interact with elements and content.&lt;br&gt;
Conversion Rate: Measure the percentage of users who complete a desired action or conversion, such as signing up or making a purchase.&lt;br&gt;
Error Rate: Keep an eye on the rate at which users encounter errors or experience issues while interacting with your application.&lt;br&gt;
Geographic Performance: Assess how performance varies across different geographic locations to identify regional performance disparities.&lt;br&gt;
Device and Browser Performance: Analyze how performance varies on different devices (e.g., desktop, mobile) and browsers (e.g., Chrome, Firefox).&lt;br&gt;
User Segmentation: Segment users based on various attributes (e.g., location, device, browser) to identify performance differences among different user groups.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Datadog-Day-2-12-09-23 : Assignment-1</title>
      <dc:creator>Rajesh Kumar Samal</dc:creator>
      <pubDate>Tue, 12 Sep 2023 11:32:15 +0000</pubDate>
      <link>https://www.debug.school/rksamal29/datadog-day-2-12-09-23-assignment-1-h1m</link>
      <guid>https://www.debug.school/rksamal29/datadog-day-2-12-09-23-assignment-1-h1m</guid>
      <description>&lt;h2&gt;
  
  
  Write it down a step to collect apache metrices to datadog ?
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Write it down a step to collect tomcat metrices to datadog ?
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Write it down a step to collect docker metrices to datadog ?
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Write it down a step to collect mysql metrices to datadog ?
&lt;/h2&gt;

</description>
    </item>
    <item>
      <title>Datadog-Day-1-11-09-23 : Assignment-2</title>
      <dc:creator>Rajesh Kumar Samal</dc:creator>
      <pubDate>Mon, 11 Sep 2023 11:39:56 +0000</pubDate>
      <link>https://www.debug.school/rksamal29/datadog-day-1-11-09-23-assignment-2-5g78</link>
      <guid>https://www.debug.school/rksamal29/datadog-day-1-11-09-23-assignment-2-5g78</guid>
      <description>&lt;h2&gt;
  
  
  Top 10 commands of Datadog Agent  ?
&lt;/h2&gt;

&lt;p&gt;$ datadog-agent status&lt;br&gt;
$ datadog-agent check apache&lt;br&gt;
$ sudo -u dd-agent datadog-agent check apache&lt;br&gt;
$ datadog-agent config&lt;br&gt;
$ datadog-agent diagnose&lt;br&gt;
$ datadog-agent health&lt;br&gt;
$ datadog-agent integration&lt;br&gt;
$ datadog-agent integration show datadog-apache&lt;br&gt;
$ systemctl start datadog-agent&lt;br&gt;
$ systemctl stop datadog-agent&lt;br&gt;
$ systemctl restart datadog-agent&lt;br&gt;
$ systemctl status datadog-agent&lt;/p&gt;

&lt;h2&gt;
  
  
  Locate how to enable Process monitoring in datadog.yaml ?
&lt;/h2&gt;

&lt;p&gt;process_collection:&lt;br&gt;
    enabled: true&lt;br&gt;
Process Agent&lt;br&gt;
process_agent_enabled: true&lt;/p&gt;

&lt;h2&gt;
  
  
  Top 5 Techniques for troubleshooting Datadog Agent  ?
&lt;/h2&gt;

&lt;p&gt;$ systemctl start datadog-agent&lt;br&gt;
$ systemctl stop datadog-agent&lt;br&gt;
$ systemctl restart datadog-agent&lt;br&gt;
$ systemctl status datadog-agent&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Difference between Obserbability and Monitoring ?</title>
      <dc:creator>Rajesh Kumar Samal</dc:creator>
      <pubDate>Mon, 11 Sep 2023 07:27:08 +0000</pubDate>
      <link>https://www.debug.school/rksamal29/difference-between-obserbability-and-monitoring--37ja</link>
      <guid>https://www.debug.school/rksamal29/difference-between-obserbability-and-monitoring--37ja</guid>
      <description>&lt;p&gt;Monitoring is tooling solution that allows teams to understand the state of their systems. Monitoring is based on gathering predefined sets of metrics or logs. &lt;br&gt;
Observability is tooling or a technical solution that allows teams to actively debug their system .Observability is based on exploring properties and patterns not defined in advance.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Datadog –Day -1- 11-09–23 : Assignment -1</title>
      <dc:creator>Rajesh Kumar Samal</dc:creator>
      <pubDate>Mon, 11 Sep 2023 07:15:09 +0000</pubDate>
      <link>https://www.debug.school/rksamal29/what-is-obserbability-and-its-advantage--3j86</link>
      <guid>https://www.debug.school/rksamal29/what-is-obserbability-and-its-advantage--3j86</guid>
      <description>&lt;h2&gt;
  
  
  What is Obserbability and its advantage ?
&lt;/h2&gt;

&lt;p&gt;Observability is to identify the cause of issue , not only to observe if there is a issue . Observability uses metrics ,logs and traces which is main component of troubleshooting the issue and provide better solution to the customer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Difference between Obserbability and Monitoring ?
&lt;/h2&gt;

&lt;p&gt;Monitoring is tooling solution that allows teams to understand the state of their systems. Monitoring is based on gathering predefined sets of metrics or logs.&lt;br&gt;
Observability is tooling or a technical solution that allows teams to actively debug their system .Observability is based on exploring properties and patterns not defined in advance.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is Datadog?
&lt;/h2&gt;

&lt;p&gt;Datadog is a monitoring and analytics tool for information technology (IT) and DevOps teams that can be used to determine performance metrics as well as event monitoring for infrastructure and cloud services. The software can monitor services such as servers, databases and tools .&lt;/p&gt;

&lt;h2&gt;
  
  
  What is Datadog Agent and How it works?
&lt;/h2&gt;

&lt;p&gt;The Datadog Agent is software that runs on your hosts. It collects events and metrics from hosts and sends them to Datadog, where you can analyze your monitoring and performance data. The Datadog Agent is open source and its source code is available on GitHub at DataDog/datadog-agent .&lt;/p&gt;

&lt;h2&gt;
  
  
  Component of Datadog Agent and short intro for each ?
&lt;/h2&gt;

&lt;p&gt;Agent,Metrics, tracing libraries, and Observability.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
