<?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: Ayesha </title>
    <description>The latest articles on Debug School by Ayesha  (@ayeshas).</description>
    <link>https://www.debug.school/ayeshas</link>
    <image>
      <url>https://www.debug.school/images/30Z3UCmDCUkRvNNLwgocq4f7hg7Skqn2dePe0bCK2AQ/rs:fill:90:90/g:sm/mb:500000/ar:1/aHR0cHM6Ly93d3cu/ZGVidWcuc2Nob29s/L3VwbG9hZHMvdXNl/ci9wcm9maWxlX2lt/YWdlLzY2OS82ZmI2/ZjQ5OS1hOTllLTQ1/NjctYjA1Ny0yY2Vm/MDdkMTc4NmQucG5n</url>
      <title>Debug School: Ayesha </title>
      <link>https://www.debug.school/ayeshas</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.debug.school/feed/ayeshas"/>
    <language>en</language>
    <item>
      <title>DataDog assigment -4</title>
      <dc:creator>Ayesha </dc:creator>
      <pubDate>Thu, 14 Sep 2023 04:54:40 +0000</pubDate>
      <link>https://www.debug.school/ayeshas/datadog-assigment-4-1bfk</link>
      <guid>https://www.debug.school/ayeshas/datadog-assigment-4-1bfk</guid>
      <description>&lt;p&gt;&lt;strong&gt;1. Top 10 metrics/indicators for APM&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1 Error rate: This is a measure of how many application requests result in failures&lt;/p&gt;

&lt;p&gt;2 Duration (Response time): This metric tracks how long it takes applications to handle requests for resources.&lt;/p&gt;

&lt;p&gt;3 Uptime: Uptime measures the total amount of time, in the form of a percentage, that your application is available and responding normally.&lt;/p&gt;

&lt;p&gt;4 Memory usage: Tracking how much memory your application uses is crucial for identifying memory leaks that could eventually cause a failure.&lt;/p&gt;

&lt;p&gt;5 CPU usage: Assessing CPU usage is important to evaluate the effect of usage on performance.&lt;/p&gt;

&lt;p&gt;6 Request rates: Measure your application traffic including spikes, inactivity, or number of active users.&lt;/p&gt;

&lt;p&gt;7 Number of instances: Scale your application to meet actual user demand with autoscaling, based on the number of app or server instances running at any one time.&lt;/p&gt;

&lt;p&gt;8 Garbage collection: Improve performance by identifying and eliminating the problems caused by heavy memory use in Java or other languages that use GC.&lt;/p&gt;

&lt;p&gt;9 Customer experience: Understand and improve upon the user experience by using a combination of Apdex scores and SLA thresholds to measure customer tolerance or satisfaction&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Top 10 metrics/indicators for Synthetic monitoring&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1 synthetics.test_runs (count): The number of Synthetic test runs.&lt;/p&gt;

&lt;p&gt;2 synthetics.test_run_steps (count): The number of Synthetic test steps.&lt;/p&gt;

&lt;p&gt;3 datadog.estimated_usage.synthetics.api_test_runs (count): Estimated usage for API tests.&lt;/p&gt;

&lt;p&gt;4 datadog.estimated_usage.synthetics.browser_test_runs (count): Estimated usage for browser tests.&lt;/p&gt;

&lt;p&gt;5 synthetics.api.response (count): The count of API responses we receive.&lt;/p&gt;

&lt;p&gt;6 synthetics.http.response.time (gauge): The overall time the request took to be processed.&lt;/p&gt;

&lt;p&gt;7 synthetics.http.response.size (gauge): The size of the response in bytes.&lt;/p&gt;

&lt;p&gt;8 synthetics.http.redirect.time (gauge): The time spent during redirections.&lt;/p&gt;

&lt;p&gt;9 synthetics.http.dns.time (gauge): The time spent resolving the DNS name of the last request.&lt;/p&gt;

&lt;p&gt;10 synthetics.http.connect.time (gauge): The time to establish the TCP connection to the server&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Top 10 metrics/indicators for RUM&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1 User Experience: RUM gives you an idea of what kind of user experience your site is offering.&lt;/p&gt;

&lt;p&gt;2 Transaction Paths: RUM monitors actual users and captures performance data to shape key metrics, like transaction paths.&lt;/p&gt;

&lt;p&gt;3 Responsiveness: This metric measures how quickly your application responds to user interactions.&lt;/p&gt;

&lt;p&gt;4 Page Load Times: This is a measure of how long it takes for a page to load from the perspective of a real user.&lt;/p&gt;

&lt;p&gt;5 Performance Analysis: RUM provides performance analysis in real time, including all user actions taken and how the various actions impact performance.&lt;/p&gt;

&lt;p&gt;6 User Actions: A basic concept of RUM revolves around user actions. A user action is any interaction a user has with your application.&lt;/p&gt;

&lt;p&gt;7 User Sessions: A user session is essentially a “user visit” performed in your application.&lt;/p&gt;

&lt;p&gt;8 Error Detection: RUM can easily identify problems or errors that occurred during a user’s interaction with your application.&lt;/p&gt;

&lt;p&gt;9 Geolocation Breakdowns: This metric provides insights into the geographic locations of your users.&lt;/p&gt;

&lt;p&gt;10 User Behavior Insights: With RUM, you can gain insight into the behavior of your users, including the number of customers who return to your site&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Datadog assigment-3</title>
      <dc:creator>Ayesha </dc:creator>
      <pubDate>Tue, 12 Sep 2023 11:47:10 +0000</pubDate>
      <link>https://www.debug.school/ayeshas/datadog-assigment-3-d15</link>
      <guid>https://www.debug.school/ayeshas/datadog-assigment-3-d15</guid>
      <description>&lt;p&gt;&lt;strong&gt;1. Write it down a step to collect apache metrices to datadog&lt;/strong&gt;****&lt;/p&gt;

&lt;p&gt;1 Install the Datadog Agent: The Apache check is packaged with the Datadog Agent. Install the Agent on your Apache server&lt;/p&gt;

&lt;p&gt;2 Enable mod_status on Apache: Apache web server exposes metrics through its status module, mod_status. If your server is running and mod_status is enabled, your server’s status page should be available at &lt;a href="http://your-server-ip/server-status"&gt;http://your-server-ip/server-status&lt;/a&gt;. If that link does not work, it means you need to enable mod_status in your configuration file&lt;/p&gt;

&lt;p&gt;3 Configure Datadog Agent for Apache: You need to edit the Datadog Agent’s configuration file for the Apache integration (conf.d/apache.d/conf.yaml). This will allow the Agent to collect logs and metrics from Apache&lt;/p&gt;

&lt;p&gt;4 Restart the Datadog Agent: After making these changes, restart the Datadog Agent to start collecting metrics&lt;/p&gt;

&lt;p&gt;5 Verify Metrics in Datadog: Log into your Datadog account and verify that the Apache metrics are being collected&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Write it down a step to collect tomcat metrices to datadog&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1 Install the Datadog Agent: The Datadog Agent is required to collect metrics from your Tomcat servers&lt;/p&gt;

&lt;p&gt;2 Enable JMX Remote on Tomcat: The Datadog Agent collects Tomcat and JVM metrics exposed by JMX via the JMXFetch plugin13. You need to enable JMX Remote on your Tomcat servers&lt;/p&gt;

&lt;p&gt;3 Configure the Datadog Agent for Tomcat: Edit the tomcat.d/conf.yaml file in the conf.d/ folder at the root of your Agent’s configuration directory to collect Tomcat metrics and logs1. See the sample tomcat.d/conf.yaml for all available configuration options&lt;/p&gt;

&lt;p&gt;4 Restart the Datadog Agent: After making these changes, restart the Datadog Agent to start collecting metrics &lt;/p&gt;

&lt;p&gt;5 Verify Metrics in Datadog: Log into your Datadog account and verify that the Apache metrics are being collected&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Write it down a step to collect docker metrices to datadog&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1 Install the Datadog Agent: The Datadog Agent is required to collect metrics from your Docker containers&lt;/p&gt;

&lt;p&gt;2 Configure the Datadog Agent for Docker&lt;/p&gt;

&lt;p&gt;3 Restart the Datadog Agent: After making these changes, restart the Datadog Agent to start collecting metrics&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Write it down a step to collect mysql metrices to datadog&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1 Install the Datadog Agent: The Datadog Agent is a piece of software that collects metrics and events from your hosts and sends them to Datadog. You can install it using a script provided by Datadog.&lt;/p&gt;

&lt;p&gt;2 Configure MySQL Integration: Once the agent is installed, you need to configure the MySQL integration. This involves creating a configuration file for MySQL in your Agent’s conf.d directory.&lt;/p&gt;

&lt;p&gt;3 Configure MySQL for Monitoring: You need to create a new user for Datadog and grant this user specific permissions to enable monitoring.&lt;/p&gt;

&lt;p&gt;4 Restart the Agent: After setting up the configuration, you need to restart the Datadog agent to start sending metrics to Datadog.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>datadog assignment 2</title>
      <dc:creator>Ayesha </dc:creator>
      <pubDate>Tue, 12 Sep 2023 06:38:44 +0000</pubDate>
      <link>https://www.debug.school/ayeshas/datadog-assignment-2-4bdg</link>
      <guid>https://www.debug.school/ayeshas/datadog-assignment-2-4bdg</guid>
      <description>&lt;p&gt;&lt;strong&gt;#1 Top 10 commands of Datadog Agent&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;datadog-agent status&lt;br&gt;
service datadog-agent stop&lt;br&gt;
service datadog-agent start&lt;br&gt;
service datadog-agent restart&lt;br&gt;
datadog-agent configcheck&lt;br&gt;
datadog-agent diagnose&lt;br&gt;
datadog-agent health&lt;br&gt;
datadog-agent check&lt;br&gt;
datadog-agent completion&lt;br&gt;
datadog-agent config&lt;/p&gt;

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

&lt;p&gt;Copy the system-probe example configuration:&lt;/p&gt;

&lt;p&gt;sudo -u dd-agent install -m 0640 /etc/datadog-agent/system-probe.yaml.example /etc/datadog-agent/system-probe.yaml&lt;br&gt;
Edit /etc/datadog-agent/system-probe.yaml to enable the process module:&lt;/p&gt;

&lt;p&gt;system_probe_config:&lt;br&gt;
  process_config:&lt;br&gt;
    enabled: true&lt;br&gt;
Restart the Agent:&lt;/p&gt;

&lt;p&gt;sudo systemctl restart datadog-agent&lt;br&gt;
Note: If the systemctl command is not available on your system, run the following command instead: sudo service datadog-agent restart&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;#3 Top 5 Techniques for troubleshooting Datadog Agent&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Status: Use sudo service datadog-agent status or sudo systemctl status datadog-agent to check if the Datadog Agent is running.&lt;br&gt;
Logs: Check the logs in /var/log/datadog for error messages.&lt;br&gt;
Configuration: Verify the agent configuration in /etc/datadog-agent/datadog.yaml.&lt;br&gt;
Connectivity: Run sudo datadog-agent info to check if the agent is connected to the Datadog backend.&lt;br&gt;
Firewalls: Ensure ports 443 and 8125 are open if a firewall is running.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Datadog – Day 1 – 11 Sept – 2023</title>
      <dc:creator>Ayesha </dc:creator>
      <pubDate>Mon, 11 Sep 2023 07:28:49 +0000</pubDate>
      <link>https://www.debug.school/ayeshas/datadog-day-1-11-sept-2023-4237</link>
      <guid>https://www.debug.school/ayeshas/datadog-day-1-11-sept-2023-4237</guid>
      <description>&lt;p&gt;&lt;strong&gt;1.What is Obserbability and its advantage?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;ans: observability is the extent to which you can understand the internal state or condition of a complex system based only on knowledge of its external outputs. The more observable a system, the more quickly and accurately you can navigate from an identified performance problem to its root cause, without additional testing or coding.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.Difference betweenb Obserbability Monitoring?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Monitoring is a practice of watching over systems, whereas Observability is about understanding the state of systems.&lt;br&gt;
Monitoring is reactive and often involves alerting based on predefined thresholds, while Observability is proactive and involves understanding why a system behaves the way it does&lt;br&gt;
**&lt;br&gt;
3.What is Datadog?**&lt;/p&gt;

&lt;p&gt;Datadog is a SaaS-based data analytics platform that allows developers and IT administrators to observe, track, and visualize key metrics from their applications.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.What is Datadog Agent and How it works?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The Datadog Agent is a piece of software that runs on your hosts. It collects events and metrics from these hosts and sends them to Datadog, where you can analyze your monitoring and performance data.&lt;/p&gt;

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

&lt;p&gt;The main components of the Datadog Agent are:&lt;/p&gt;

&lt;p&gt;Collector: Runs checks and collects metrics.&lt;br&gt;
Forwarder: Sends payloads to Datadog.&lt;br&gt;
DogStatsD: A Golang implementation of Etsy’s StatsD metric aggregation daemon.&lt;br&gt;
APM Agent: Collects traces.&lt;br&gt;
Process Agent: Collects live process information.&lt;/p&gt;

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