<?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: Devendra A Aphale</title>
    <description>The latest articles on Debug School by Devendra A Aphale (@devendraaphale_976).</description>
    <link>https://www.debug.school/devendraaphale_976</link>
    <image>
      <url>https://www.debug.school/images/RGqBfGLBRb3LZMdPNDnCW7oLd3FS6y1YQ6QOFU-_xp8/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly93d3cu/ZGVidWcuc2Nob29s/L3VwbG9hZHMvdXNl/ci9wcm9maWxlX2lt/YWdlLzY1Ni9kMTIx/NDRmMC01ODQwLTQ4/ZGYtYmJlZC1jNTc4/YjM4NDFiOGYucG5n</url>
      <title>Debug School: Devendra A Aphale</title>
      <link>https://www.debug.school/devendraaphale_976</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/devendraaphale_976"/>
    <language>en</language>
    <item>
      <title>Synthetic and RUM Monitoring</title>
      <dc:creator>Devendra A Aphale</dc:creator>
      <pubDate>Thu, 14 Sep 2023 04:58:41 +0000</pubDate>
      <link>https://www.debug.school/devendraaphale_976/synthetic-and-rum-monitoring-pg1</link>
      <guid>https://www.debug.school/devendraaphale_976/synthetic-and-rum-monitoring-pg1</guid>
      <description>&lt;p&gt;Synthetic Monitoring &lt;br&gt;
Application is up and running 24*7&lt;br&gt;
Test New market or Geography &lt;br&gt;
Monitor 3rd Party APIs&lt;br&gt;
Resolve Support Issues &lt;br&gt;
SLAs&lt;/p&gt;

&lt;p&gt;RUM&lt;br&gt;
Determine Impact of Slowness &lt;br&gt;
Monitor Real Users&lt;br&gt;
SLAs&lt;br&gt;
Transaction performance &lt;br&gt;
Root Cause determination &lt;/p&gt;

</description>
    </item>
    <item>
      <title>DataDog Questions-2</title>
      <dc:creator>Devendra A Aphale</dc:creator>
      <pubDate>Mon, 11 Sep 2023 11:49:32 +0000</pubDate>
      <link>https://www.debug.school/devendraaphale_976/datadog-questions-2-13p0</link>
      <guid>https://www.debug.school/devendraaphale_976/datadog-questions-2-13p0</guid>
      <description>&lt;h1&gt;
  
  
  1 Top 10 commands of Datadog Agent
&lt;/h1&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;br&gt;
$ ls /var/log/datadog/&lt;br&gt;
$ more /etc/datadog-agent/datadog.yaml&lt;br&gt;
$ more /var/log/datadog/agent.log&lt;br&gt;
$ more /var/log/datadog/process-agent.log&lt;br&gt;
$ more /var/log/datadog/trace-agent.log&lt;br&gt;
$ datadog-agent configcheck&lt;br&gt;
$ datadog-agent config&lt;br&gt;
$ datadog-agent health&lt;br&gt;
$ datadog-agent hostname&lt;br&gt;
$ datadog-agent version&lt;br&gt;
$ datadog-agent status&lt;/p&gt;

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

&lt;p&gt;process_config:&lt;br&gt;
  process_collection:&lt;br&gt;
    enabled: "true"&lt;/p&gt;

&lt;h1&gt;
  
  
  3 Top 5 Techniques for troubleshooting Datadog Agent
&lt;/h1&gt;

&lt;p&gt;Check the Agent Status: Check if the Datadog Agent is running on the machine by running the command “sudo service datadog-agent status” or “sudo systemctl status datadog-agent”. If the agent is not running, try restarting the agent by running the command “sudo service datadog-agent restart” or “sudo systemctl restart datadog-agent”.&lt;br&gt;
Check the Agent Logs: Check the logs for any error messages that may indicate issues with the agent. The agent logs can be found in the /var/log/datadog directory. Check for any error messages or stack traces and try to resolve the issue based on the error message.&lt;br&gt;
Check the Configuration: Verify the agent configuration to ensure that it is properly configured. The agent configuration file is located in /etc/datadog-agent/datadog.yaml. Check for any errors in the configuration file and ensure that it is properly configured to collect the metrics and logs that you need.&lt;br&gt;
Check the Connectivity: Check if the agent is able to connect to the Datadog backend. To do this, run the command “sudo datadog-agent info” and check the “Status” field. If the status is “ok”, then the agent is connected to the backend. If the status is “not running”, then there may be an issue with the agent configuration or connectivity.&lt;br&gt;
Check for Firewalls: If you are running a firewall on the machine, ensure that the agent is allowed to communicate with the Datadog&lt;/p&gt;

</description>
    </item>
    <item>
      <title>DataDog Training 11 Sept</title>
      <dc:creator>Devendra A Aphale</dc:creator>
      <pubDate>Mon, 11 Sep 2023 07:35:49 +0000</pubDate>
      <link>https://www.debug.school/devendraaphale_976/datadog-training-11-sept-4mm2</link>
      <guid>https://www.debug.school/devendraaphale_976/datadog-training-11-sept-4mm2</guid>
      <description>&lt;h2&gt;
  
  
  What is Obserbability and its advantage?
&lt;/h2&gt;

&lt;p&gt;Observability contains collection of below details &lt;br&gt;
1.Metrics (Related to Infra)&lt;br&gt;
2.Traces (Application Performance Monitoring)&lt;br&gt;
3.Log  (Log Analytics)&lt;br&gt;
4.Uptime (Through Synthetic Monitoring) &lt;br&gt;
5.UX  (Real User Monitoring)&lt;br&gt;
6.Security &lt;/p&gt;

&lt;h2&gt;
  
  
  Difference betweenb Obserbability Monitoring?
&lt;/h2&gt;

&lt;p&gt;Monitoring tells you when something is wrong where observability gives why something is wrong with detailed system view. &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.&lt;/p&gt;

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

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