<?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: Deepak dhodi</title>
    <description>The latest articles on Debug School by Deepak dhodi (@deepakdhodi_77).</description>
    <link>https://www.debug.school/deepakdhodi_77</link>
    <image>
      <url>https://www.debug.school/images/jdt77fX6AEazJ2dGzlp-mhUZX-VcjrBW8AoBBeVqYAs/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly93d3cu/ZGVidWcuc2Nob29s/L3VwbG9hZHMvdXNl/ci9wcm9maWxlX2lt/YWdlLzg3LzI3NmI5/YmEwLTE0MTItNDk1/NS05YjhhLTcxODQ2/ZTNkOWUxOS5wbmc</url>
      <title>Debug School: Deepak dhodi</title>
      <link>https://www.debug.school/deepakdhodi_77</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/deepakdhodi_77"/>
    <language>en</language>
    <item>
      <title>Log analysis</title>
      <dc:creator>Deepak dhodi</dc:creator>
      <pubDate>Thu, 15 Sep 2022 05:37:40 +0000</pubDate>
      <link>https://www.debug.school/deepakdhodi_77/log-analysis-4h7m</link>
      <guid>https://www.debug.school/deepakdhodi_77/log-analysis-4h7m</guid>
      <description>&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Write down top 10 events in Windows and identify their event ID&lt;br&gt;
event ID - 4624 /25 - successful and failed account log on , 4648 - system logon attempt with explicit credentials, 4719 -system audit policy changed, 1102 - audit logs cleared, 4723 - attempt made to change the password of account, 4740 - user account locked, 4735- priviledge local group modified, 4782 - password has an account was accessed, 4946- rule was added to windows firewall  exception list.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Write down top 10 events in Linux and identify their pattern and log linux&lt;br&gt;
/var/log/messages,/var/log/auth.log, /var/log/secure,/var/log/boot.log, /var/log/dmesg, /var/log/kern.log,/var/log/faillog&lt;br&gt;
/var/log/cron, /var/log/yum.log,/var/log/maillog or /var/log/mail.log&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Identify the log file in linux which log service start|stop|enable|disable&lt;br&gt;
start - sudo systemctl start service.service, stop- sudo systemctl stop service.service, enable - sudo systemctl enable name_service.service,&lt;br&gt;
disable - sudo systemctl disable name_service.service&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Identify the log file in linux which log process running or killed.&lt;br&gt;
If the kernel killed a process (because the system ran out of memory), there will be a kernel log message. Check in /var/log/kern.log (on Debian/Ubuntu, other distributions might send kernel logs to a different file, but usually under /var/log under Linux&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Identify the log file of apache and find out list of VERB and count of each using linux command&lt;br&gt;
Location of the Log Files By default on Debian-based distributions such as Ubuntu, access and error logs are located in the /var/log/apache2 directory. On CentOS the log files are placed in /var/log/httpd directory. Reading and Understanding the Apache Log Files&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Understanding Datadog Agent</title>
      <dc:creator>Deepak dhodi</dc:creator>
      <pubDate>Tue, 13 Sep 2022 09:52:00 +0000</pubDate>
      <link>https://www.debug.school/deepakdhodi_77/understanding-datadog-agent-56ii</link>
      <guid>https://www.debug.school/deepakdhodi_77/understanding-datadog-agent-56ii</guid>
      <description>&lt;p&gt;**- **What is Datadog agent?&lt;br&gt;
Its a software that runs on host that collects events and metrics from hosts and sends these events and metrices to  Datadog, where one  analyze  monitoring and performance data.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Type of Datadog Agent?
Collector and Dogstatsd&lt;/li&gt;
&lt;li&gt;Ports used to in Datadog agent?
UDP , HTTP - 80, TCP, HTTPS - 443&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Top 5 commands with simple explanation troubleshooting Datadog agent?&lt;br&gt;
$ systemctl start datadog-agent - start the agent&lt;br&gt;
$ systemctl stop datadog-agent  - stop the agent &lt;br&gt;
$ systemctl status datadog-agent    - status of the agent&lt;br&gt;
$ datadog-agent config    - print all the runtime configuration&lt;br&gt;
$ more /etc/datadog-agent/datadog.yaml - details of configuartion file&lt;br&gt;
$ ls /var/log/datadog/ - listing&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Locate how to enable Logs monitoring in datadog.yaml&lt;br&gt;
edit the datadog.yaml file. Locate the logs: section and set enabled: false to enabled: true.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;5 techniques for troubleshooting Datadog?&lt;br&gt;
Verify API token      (datadog.yaml)&lt;br&gt;
Verify site/region    (datadog.yaml)&lt;br&gt;
Datadog Agent is running or not under services&lt;br&gt;
check if logs enabled under config file**&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;**&lt;/p&gt;

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