Overview
As introduced in our article How to Unleash the power of ATLAS + Weatherman: our new AI chat Support duo, you can now get real-time analyses of any issues affecting your instances and environments. That said, you may be interested in learning the exact capabilities of the system.
In this article, we list the available analyses and the type of instance to which they apply.
Available analyses
All scenarios apply to specific instances unless they have the 'environment' role. For these, you will need to analyze the environment as a whole. Some scenarios are limited to a specific instance type, such as those affecting the database.
Scenarios are automatically selected based on your requirements. Nonetheless, you can refer to the list below to learn which ones exist based on your issue.
| Identifier | Roles | Scenario |
|---|---|---|
| app-server-issues | app_master, app, solo | This scenario covers issues with the application server, which will be one of Puma, Passenger, or Unicorn. This includes cases where the app server is down, unresponsive, or throwing any type of errors. |
| chef-run-issues | This scenario covers cases when facing issues with the Chef run clicking the 'apply' button, or applying changes to an instance. | |
| collectd-fails | This scenario covers cases when the Collectd process is failing or not behaving as expected. | |
| cron-fails | This scenario covers cases when the cron process is failing or not behaving as expected. | |
| db-backup | db_slave, db_master, solo | This scenario covers problems with database backups, such as a backup not completing or throwing an error. |
| db-connections | db_slave, db_master, solo | This scenario covers issues with database connections, such as a high number of concurrent connections affecting the DB, or a DB being unreachable. |
| db-issues | db_slave, db_master, solo | This scenario covers general problems with the database, when the nature of the problem is not known or there's no other scenario that better applies. |
| db-replication | db_slave, db_master | This scenario covers problems with database replication, such as issues for the slave or replica being out of sync, the master being unreachable, etc. |
| deployment-failing | environment | This scenario covers problems when code is failing to be deployed to an environment, or an instance is not working after deploying the code. |
| environment-check | environment | This scenario covers problems with the environment at large, where no specific issue is identified and a general check is required. |
| instance-check | This scenario covers general problems with the instance, where no specific issue is identified and a check is required. | |
| io-wait | This scenario covers issues with high IO wait times for disk usage. | |
| load | This scenario covers issues with high CPU load or usage. | |
| low-disk-space | This scenario covers issues where the disk space is running low on a certain instance, without identifying a specific drive. | |
| low-disk-space-data | This scenario covers issues where the disk space of the /data drive is running low on a certain instance. | |
| low-disk-space-db | This scenario covers issues where the disk space of the /db drive is running low on a certain instance. | |
| low-disk-space-mnt | This scenario covers issues where the disk space of the /mnt drive is running low on a certain instance. | |
| low-disk-space-root | This scenario covers issues where the disk space of the root drive is running low on a certain instance. | |
| promotion | db_slave, db_master | This scenario covers cases when a database is failing to be promoted. |
| slow-queries | db_slave, db_master, solo | This scenario covers issues with slow queries, query performance, or the time for the database to execute the queries. |
| swap | This scenario covers issues with high swap usage. | |
| system-slow | This scenario covers general slowness with the instance. | |
| web-stack-check | app_master, app, solo | This scenario covers problems when a website is not reachable or is experiencing issues. |
| website-down | environment | This scenario covers problems when the website hosted in the environment is not accessible. |
Comments
Article is closed for comments.