-
-
Notifications
You must be signed in to change notification settings - Fork 739
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Document how to use "--profile" flag.
- Loading branch information
Showing
2 changed files
with
19 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,3 +9,4 @@ platform and how you can troubleshoot and debug them. | |
|
||
rules | ||
ssh | ||
database |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
Troubleshooting Database Issues | ||
=============================== | ||
|
||
This section contains information on how to troubleshoot database (MongoDB) related issues. | ||
|
||
Troubleshooting performance and missing index related issues | ||
------------------------------------------------------------ | ||
|
||
If some of the API requests are slow you receive back "too much data" error, this could be caused | ||
by an inefficient database query or a missing index. | ||
|
||
To troubleshoot this issue, you should start the offending service (e.g. ``st2api``) with the | ||
``--debug`` / ``--profile`` flag. | ||
|
||
When this flag is used the service runs in the profiling mode meaning all the executed MongoDB | ||
queries and related profiling information (which indexes were used, how many records / rows were | ||
scanned, how long the query took, etc.) will be logged in the service log under the DEBUG log | ||
level. |