
One important thing to note as you plan your deployments is that are two main ways to deploy osquery depending on your use case(s). For more information, see the official deployment guide. osquery will require root or system privileges to get a lot of detailed system information, although it is possible to glean some information when not ran as 'root'. Osquery is agent software that must run directly on your endpoints (e.g, your OSX installation or Linux servers).
Osquery ram cpu usage full#
Select count(pid) as total, name from processes group by name order by total desc limit 10 Īs you can see, you can use standard SQL including limits, aggregates, and joins, you can ask powerful questions about your infrastructure! And you’re not just limited to process information – you can view the full list of ‘tables’ you can query from in the documentation (plus we’ll explore more in the examples below). Return process count, name for the top 10 most active processes Select pid, name, uid, resident_size from processes order by resident_size desc limit 10 osquery at a glance Query for top 10 largest processes by resident memory size We’ll talk about some more of these below. For example: if you suspect a malicious process is running on a system, you can query for the process by name or even a filename it has open. From a security perspective, it can be used to query your endpoints to detect, investigate, and proactively hunt for various types of threats. Osquery is a flexible tool and can be used for a variety of use cases to troubleshoot performance and operational issues. Osquery allows you to craft your system queries using SQL statements, making it easy to use by security engineers that are already familiar with SQL.

Osquery is an open source tool created by Facebook for querying various information about the state of your machines.

Last updated at Wed, 21:29:25 GMT What is osquery?
