SQL powered operating system instrumentation, monitoring, and analytics.
Go to file
2014-08-28 21:33:44 -07:00
lib@e163809165 [vtable_listening_ports] Listening sockets, IPv4, IPv6 2014-08-19 15:25:16 -07:00
osquery fix memory leak in sqlite3_attach_tables #74 2014-08-28 21:33:44 -07:00
package Adding LaunchDaemon and flagfile to the repo/package 2014-08-26 11:26:52 -07:00
third-party@4dac47d96d updating third-party 2014-08-11 16:57:44 -07:00
tools fix memory leak in sqlite3_attach_tables #74 2014-08-28 21:33:44 -07:00
.clang-format update the formatting in .clang-format 2014-08-15 12:41:47 -07:00
.gitignore Deploy infrastructure for OS X 2014-08-20 00:47:14 -07:00
.gitmodules Deploy infrastructure for OS X 2014-08-20 00:47:14 -07:00
CMakeLists.txt xcode build 2014-08-26 14:39:02 -07:00
Makefile Adding LaunchDaemon and flagfile to the repo/package 2014-08-26 11:26:52 -07:00
osquery.supp adding localtime to valgrind supressions because it's statically allocated, thus not a leak 2014-08-28 17:39:56 -07:00
README.md Update README.md 2014-08-14 19:47:35 -07:00
requirements.txt Initial commit 2014-07-30 17:35:19 -07:00

osquery

Building on OS X

To build osquery on OS X, all you need installed is pip and brew. make deps will take care of installing the appropriate library dependencies, but I recommend taking a look at the Makefile, just in case you see something that might conflict with your personal setup.

Anything that doesn't have a homebrew package is built from source from https://github.com/osquery/third-party, which is a git submodule of this repository which is set up by make deps.

The complete installation/build steps are as follows:

git clone git@github.com:facebook/osquery.git
cd osquery
make deps
make

Once the project is built, try running the project's unit tests:

make runtests

Table Development

Top easy virtual tables

High impact virtual tables