title: Critical AWS RDS_47_replica Events
body: <p>If there are ways to adjust RDS to scale better during ( timeframe (1:20 PM ET - 1:50 PM ET))these periods of increased usage; or if we'd need an additional replica?
  The DB was executing during this timeframe (1:20 PM ET - 1:50 PM ET)</p>
  <pre><code>MySQL Host: mysql-dec-47-replica.comhjpbnmlkq.us-east-1.rds.amazonaws.com
  Name    Currently running threads
  Group   Current Connections
  Type    Critical
  Threshold   200
  Value   900
  </code></pre>
  <blockquote>
  <p>Advice    If the database is overloaded you'll get an increased number of
  queries running. Occasional spikes are OK for very short period of
  time. Too many active threads indicate that:</p>
  <ol>
  <li>MySQL is taking too much time to process you requests.</li>
  <li>You are continuously retrieving/updating large datasets. Make sure that queries are tuned to use indexes. Execute SHOW FULL PROCESSLIST
  of find queries that are getting locked continuously. Try isolating
  long running queries by enabling the slow query log.</li>
  </ol>
  </blockquote>
  <pre><code>Name    Seconds behind master
  Group   Replication
  Type    Warning
  Threshold   60
  Value   63
  </code></pre>
  <blockquote>
  <p>Advice    This value is useful only if the network between Slave and
  Master is fast. If the network is fast, investigate why this server is
  so far behind the master. Sometimes, other processes on the slave can
  impact the MySQL server. Try to improve the connectivity between the
  Master and Slave. This value can also get very high if the Slave was
  unable to to connect to MASTER at some point in time. In that case,
  the slave would eventually catch up with the master</p>
  </blockquote>
  <p>Is there monitoring we could enable to be altered of this earlier, either in RDS or in CloudWatch?</p>