<?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: Vasim Akram Shaik</title>
    <description>The latest articles on Debug School by Vasim Akram Shaik (@shaikvasim221_165).</description>
    <link>https://www.debug.school/shaikvasim221_165</link>
    <image>
      <url>https://www.debug.school/images/BsaE8fbRKmAsaaIiGTNBnBNb9SiYU_eUqOprjxSg9LM/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly93d3cu/ZGVidWcuc2Nob29s/L3VwbG9hZHMvdXNl/ci9wcm9maWxlX2lt/YWdlLzc4LzkyYzA2/ZDMyLWE3NTAtNDJm/OC04MDc2LTgwY2Jm/M2IyMTViYi5wbmc</url>
      <title>Debug School: Vasim Akram Shaik</title>
      <link>https://www.debug.school/shaikvasim221_165</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/shaikvasim221_165"/>
    <language>en</language>
    <item>
      <title>Log Analysis</title>
      <dc:creator>Vasim Akram Shaik</dc:creator>
      <pubDate>Thu, 15 Sep 2022 05:48:00 +0000</pubDate>
      <link>https://www.debug.school/shaikvasim221_165/log-analysis-ci9</link>
      <guid>https://www.debug.school/shaikvasim221_165/log-analysis-ci9</guid>
      <description>&lt;p&gt;1.&lt;strong&gt;Write down top 10 events in Windows and identify their event ID ?&lt;/strong&gt;&lt;br&gt;
4624 Successful account log on&lt;br&gt;
4625 Failed account log on&lt;br&gt;
4634 An account logged off&lt;br&gt;
4648 A logon attempt was made with explicit credentials&lt;br&gt;
4719 System audit policy was changed.&lt;br&gt;
4964 A special group has been assigned to a new log on&lt;br&gt;
1102 Audit log was cleared. This can relate to a potential attack&lt;br&gt;
4720 A user account was created&lt;br&gt;
4722 A user account was enabled&lt;br&gt;
4723 An attempt was made to change the password of an account&lt;/p&gt;

&lt;p&gt;2.&lt;strong&gt;Write down top 10 events in Linux and identify their pattern and log linux&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;/var/log/messages&lt;br&gt;
/var/log/auth.log&lt;br&gt;
/var/log/secure&lt;br&gt;
/var/log/boot.log&lt;br&gt;
/var/log/dmesg&lt;br&gt;
/var/log/kern.log&lt;br&gt;
/var/log/faillog&lt;br&gt;
/var/log/yum.log&lt;br&gt;
var/log/httpd/&lt;br&gt;
/var/log/mysql.log&lt;/p&gt;

&lt;p&gt;3.&lt;strong&gt;Identify the log file in linux which log service start|stop|enable|disable&lt;/strong&gt;&lt;br&gt;
systemctl start service&lt;br&gt;
systemctl stop service&lt;br&gt;
systemctl enable service&lt;br&gt;
systemctl disable service&lt;/p&gt;

&lt;p&gt;4.&lt;strong&gt;Identify the log file in linux which log process running or killed.&lt;/strong&gt;&lt;br&gt;
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;p&gt;5.&lt;strong&gt;Identify the log file of apache and find out list of VERB and count of each using linux command&lt;/strong&gt;&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;

</description>
    </item>
    <item>
      <title>Understanding Datadog Agent</title>
      <dc:creator>Vasim Akram Shaik</dc:creator>
      <pubDate>Tue, 13 Sep 2022 09:54:00 +0000</pubDate>
      <link>https://www.debug.school/shaikvasim221_165/understanding-datadog-agent-2593</link>
      <guid>https://www.debug.school/shaikvasim221_165/understanding-datadog-agent-2593</guid>
      <description>&lt;p&gt;&lt;strong&gt;What is Datadog Agent ?&lt;/strong&gt;&lt;br&gt;
Datadog agent is a combination of collector, Forwarder and DogstaasD. Which collects the metrices, events etc and forwards to the datadog through https.&lt;br&gt;
&lt;strong&gt;Type of Datadog Agent ?&lt;/strong&gt;&lt;br&gt;
StaasD&lt;br&gt;
DogstaasD&lt;br&gt;
&lt;strong&gt;Ports used in Datadog agent?&lt;/strong&gt;&lt;br&gt;
5000--&amp;gt;Exposes runtime metrics about the Agent.&lt;br&gt;
5001--&amp;gt;Used by the Agent CLI and GUI to send commands and pull &lt;br&gt;
        information from the running Agent.&lt;br&gt;
5002--&amp;gt;Serves the GUI server on Windows and OSX.&lt;br&gt;
8125--&amp;gt;Used for the DogStatsD server to receive external metrics.&lt;br&gt;
443/tcp--&amp;gt; port for most Agent data. &lt;br&gt;
&lt;strong&gt;Top 5 commands with simple explanation troubleshooting Datadog agent?&lt;/strong&gt;&lt;br&gt;
$ datadog-agent status - To check the status whether it is active or not &lt;br&gt;
$ datadog-agent config - Whether it is configured or not&lt;br&gt;
$ datadog-agent diagnose - To diagnosis the server&lt;br&gt;
$ datadog-agent health - To check the health of server&lt;br&gt;
$ datadog-agent integration - To check whether container integrated or not&lt;br&gt;
&lt;strong&gt;5 techniques for troubleshooting Datadog?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Verify API token  (datadog.yaml)&lt;/li&gt;
&lt;li&gt;Verify site/region    (datadog.yaml)&lt;/li&gt;
&lt;li&gt;Agent is running or not&lt;/li&gt;
&lt;li&gt;Restart the services&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Locate how to enable Logs monitoring in datadog.yaml&lt;/strong&gt;&lt;br&gt;
we need to fetch the YML file and then Locate the logs: section and set enabled: false to enabled: true.&lt;/p&gt;

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