{"_id":"5809f027a0c3150f00ae47fa","category":{"_id":"56a20bdf8b2e6f0d0018ea84","pages":["56a20e302255370d00ad5ecb"],"project":"56a1f77442dfda0d00046285","__v":1,"version":"56a1f77542dfda0d00046288","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-22T11:00:47.207Z","from_sync":false,"order":3,"slug":"features","title":"Features"},"version":{"_id":"56a1f77542dfda0d00046288","__v":9,"project":"56a1f77442dfda0d00046285","createdAt":"2016-01-22T09:33:41.397Z","releaseDate":"2016-01-22T09:33:41.397Z","categories":["56a1f77542dfda0d00046289","56a1fdf442dfda0d00046294","56a2079f0067c00d00a2f955","56a20bdf8b2e6f0d0018ea84","56a3e78a94ec0a0d00b39fed","56af19929d32e30d0006d2ce","5721f4e9dcfa860e005bef98","574e870be892bf0e004fde0d","5832fdcdb32d820f0072e12f"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"user":"56d5952da0b5600b000b1e71","__v":1,"parentDoc":null,"project":"56a1f77442dfda0d00046285","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-10-21T10:38:31.618Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":7,"body":"## What's on this page?\n\nYou can find and filter errors in your code and see their stack traces and occurrence data.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/1f286d0-errors.png\",\n        \"errors.png\",\n        2560,\n        1260,\n        \"#2f5172\"\n      ],\n      \"caption\": \"Errors\"\n    }\n  ]\n}\n[/block]\n## Why is it helpful?\n\nSome errors may be more critical than others. With the help of this page you can easily find the errors which need an urgent fix.\n\n## Searching\n\nYou can filter by time range and keywords using the search dialog.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/a15dd7d-error_search_dialog.png\",\n        \"error_search_dialog.png\",\n        2560,\n        1260,\n        \"#303a48\"\n      ],\n      \"caption\": \"Errors search dialog\"\n    }\n  ]\n}\n[/block]\nThe keyword filter searches for a fuzzy match with entered words in the error name, message and stack trace. If you would like to be more specific, you can use the following query language.\n\n- Logical operators: You can use the words AND, OR and NOT as logical operators between keywords. For example: error OR exception AND NOT type.\n\n- Boolean operators: You can use the + or - minus sign prefix as boolean operators. Words prefixed with a + must be included in the result, while words prefixed with a - must not be included. For example: error -type.\n\n- Grouping: You can group your keywords with parentheses to alter operator precedence. For example: error AND (range OR type).\n\n- Exact phrases: put your phrases in quotes for an exact match. For example: \"type error\".\nWild cards: add single character wildcards with ? and multi-character wildcards with *. For example: r?nge err*.\n\n- Fuzziness: You can specify the maximum edit distance, which may result in a match with a ~ postfix. For example: error~2 matches eror and erorr.\n\n- Proximity: You can specify a word level proximity of exact phrases by a ~ postfix. For example: \"type error\"~2 matches 'error type' and 'type custom error'.\n\n- Word boosting: You can specify the weight of a single word with a ^ postfix. For example: type^3 error will consider type three times more relevant than error.\n\n- Per field search: You can prefix a word with fieldName: to restrict the search to that field. For example: name:error stack:function. The three usable field names are name, message and stack.\n\n- Field existence: You can filter results where a particular field exists with the \\_exists\\_: and \\_missing\\_: prefixes. For example: \\_exists\\_:stack. \n\n- Regular expressions: You can also use regular expressions wrapped in / for more powerful searches. For example: /t?pe(ch[ea]ck)/.\n\n### Example queries\n\n*Searching for errors that are not caused by validation.*\n\n- query: -validation\n- result: Everything, which doesn't have the word 'validation' in its name, message or stack trace.\n\n*Searching for everything except TypeErrors.*\n\n- query: name:(NOT \"TypeError\")\n- result: Everything, which has a name other than TypeError.\n\n*Searching for network related errors, but not timeouts.*\n\n- query: socket network http connection -timeout\n- result: Everything that has some of the network related words, but doesn't include the word 'timeout'.\n\n*Searching for errors caused by typos.*\n\n- query: -myFunction +(myFunction~2)\n- result: Everything that doesn't include the word 'myFunction', but includes a word with at most two edit distance to 'myFunction' (likely a typo).\n\n*Searching for errors which do not have a stack trace.*\n\n- query: \\_missing\\_:stack\n- result: Everything that has no stack trace.\n- use case: Filter out the cases where you report custom errors to trace, but forgot to include a stack trace.\n\n## Ordering\n\nYou can order the search result by keyword relevancy, last occurrence or occurrence count.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/6c0257a-error_ordering.png\",\n        \"error_ordering.png\",\n        2560,\n        1248,\n        \"#2f5073\"\n      ],\n      \"caption\": \"Error ordering\"\n    }\n  ]\n}\n[/block]\n## Error details\n\nYou can open the details view by clicking on an error entry. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/da0086a-error_details.png\",\n        \"error_details.png\",\n        2556,\n        1260,\n        \"#273d4e\"\n      ],\n      \"caption\": \"Error details\"\n    }\n  ]\n}\n[/block]\nThe RELATED TRACE button links the the related trace in the [Trace page](https://trace-docs.risingstack.com/docs/trace-view). Use it to find out more about the context in which the error occurred.\n\n## Keyword highlighting\n\nIf errors are filtered by keywords, the relevant words will be highlighted by a yellow background.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/697e296-error_highlighting.png\",\n        \"error_highlighting.png\",\n        2554,\n        1254,\n        \"#f0f2f4\"\n      ],\n      \"caption\": \"Error highlighting\"\n    }\n  ]\n}\n[/block]","excerpt":"Search for errors in your code with a flexible query language","slug":"errors","type":"basic","title":"Errors"}

Errors

Search for errors in your code with a flexible query language

## What's on this page? You can find and filter errors in your code and see their stack traces and occurrence data. [block:image] { "images": [ { "image": [ "https://files.readme.io/1f286d0-errors.png", "errors.png", 2560, 1260, "#2f5172" ], "caption": "Errors" } ] } [/block] ## Why is it helpful? Some errors may be more critical than others. With the help of this page you can easily find the errors which need an urgent fix. ## Searching You can filter by time range and keywords using the search dialog. [block:image] { "images": [ { "image": [ "https://files.readme.io/a15dd7d-error_search_dialog.png", "error_search_dialog.png", 2560, 1260, "#303a48" ], "caption": "Errors search dialog" } ] } [/block] The keyword filter searches for a fuzzy match with entered words in the error name, message and stack trace. If you would like to be more specific, you can use the following query language. - Logical operators: You can use the words AND, OR and NOT as logical operators between keywords. For example: error OR exception AND NOT type. - Boolean operators: You can use the + or - minus sign prefix as boolean operators. Words prefixed with a + must be included in the result, while words prefixed with a - must not be included. For example: error -type. - Grouping: You can group your keywords with parentheses to alter operator precedence. For example: error AND (range OR type). - Exact phrases: put your phrases in quotes for an exact match. For example: "type error". Wild cards: add single character wildcards with ? and multi-character wildcards with *. For example: r?nge err*. - Fuzziness: You can specify the maximum edit distance, which may result in a match with a ~ postfix. For example: error~2 matches eror and erorr. - Proximity: You can specify a word level proximity of exact phrases by a ~ postfix. For example: "type error"~2 matches 'error type' and 'type custom error'. - Word boosting: You can specify the weight of a single word with a ^ postfix. For example: type^3 error will consider type three times more relevant than error. - Per field search: You can prefix a word with fieldName: to restrict the search to that field. For example: name:error stack:function. The three usable field names are name, message and stack. - Field existence: You can filter results where a particular field exists with the \_exists\_: and \_missing\_: prefixes. For example: \_exists\_:stack. - Regular expressions: You can also use regular expressions wrapped in / for more powerful searches. For example: /t?pe(ch[ea]ck)/. ### Example queries *Searching for errors that are not caused by validation.* - query: -validation - result: Everything, which doesn't have the word 'validation' in its name, message or stack trace. *Searching for everything except TypeErrors.* - query: name:(NOT "TypeError") - result: Everything, which has a name other than TypeError. *Searching for network related errors, but not timeouts.* - query: socket network http connection -timeout - result: Everything that has some of the network related words, but doesn't include the word 'timeout'. *Searching for errors caused by typos.* - query: -myFunction +(myFunction~2) - result: Everything that doesn't include the word 'myFunction', but includes a word with at most two edit distance to 'myFunction' (likely a typo). *Searching for errors which do not have a stack trace.* - query: \_missing\_:stack - result: Everything that has no stack trace. - use case: Filter out the cases where you report custom errors to trace, but forgot to include a stack trace. ## Ordering You can order the search result by keyword relevancy, last occurrence or occurrence count. [block:image] { "images": [ { "image": [ "https://files.readme.io/6c0257a-error_ordering.png", "error_ordering.png", 2560, 1248, "#2f5073" ], "caption": "Error ordering" } ] } [/block] ## Error details You can open the details view by clicking on an error entry. [block:image] { "images": [ { "image": [ "https://files.readme.io/da0086a-error_details.png", "error_details.png", 2556, 1260, "#273d4e" ], "caption": "Error details" } ] } [/block] The RELATED TRACE button links the the related trace in the [Trace page](https://trace-docs.risingstack.com/docs/trace-view). Use it to find out more about the context in which the error occurred. ## Keyword highlighting If errors are filtered by keywords, the relevant words will be highlighted by a yellow background. [block:image] { "images": [ { "image": [ "https://files.readme.io/697e296-error_highlighting.png", "error_highlighting.png", 2554, 1254, "#f0f2f4" ], "caption": "Error highlighting" } ] } [/block]