valitydev/osquery-1
14
0
Fork 0
mirror of https://github.com/valitydev/osquery-1.git synced 2024-11-07 09:58:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Added note to explain results from failed queries (#2376)

Browse Source
This commit is contained in:
Gary 2016-08-16 16:39:43 +01:00 committed by Teddy Reed
parent 0161edf15d
commit 87bc28e313
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/wiki/deployment/performance-safety.md
View File

@ -63,6 +63,8 @@ The results (utilization=2) suggest running `processes_binding_to_ports` less of
To estimate how often these should run you should evaluate what a differential in the information means from your visibility requirement's perspective (how meaningful is a change vs. how often you check for the change). Then weigh that value against the performance impact of running the query.
Queries that fail to execute (for example, due to a non-existent table) will return the highest category result '3' and the value '-1' for all statistics.
## Continuous Build
The continuous integration for osquery is currently under development. The previous CI solution was unreliably failing builds due to network and memory issues.