Re:Osquery: Expose the operating system as a relational data...
by marpaia on Wednesday October 29, 2014 @10:11PM
(#8531002)
Hmn, no, not really. there is no underlying datastore for the data that you query. it's all generated on the fly.
[ Parent
| on HN ]
Re:Osquery: Expose the operating system as a relational data...
by avifreedman on Thursday October 30, 2014 @12:37AM
(#8531400)
Cool. Would be interesting to see if that comes up as a common request; we have found the ability to do real-time and historic to be interesting for query-ability for system data.
Have you seen the other neat functionality about the Akamai query system? They allow (actually require) devs to create callbacks that get exposed as query tables to do debugging (vs letting devs on machines as first or second line of debugging).
It's an interesting paradigm though again the way they use it, like osquery, is only real-time and using the psql/OpenTSDB method allows for history as well as real-time.
osquery (and Akamai Query's) syntax is definitely simpler. We do plan to add a logical schema to map tags in OpenTSDB to logical columns to help with that.
Re:Osquery: Expose the operating system as a relational data...
by spydum on Wednesday October 29, 2014 @10:38PM
(#8531068)
seems like it would be minimal effort for someone to slap sqlite and a makeshift ETL process to build time series?
edit: and after more reading, looks like the ETL could be done with osqueryd, and a plugin to push output to sqlite if desired -- even better!