An Overview of Node Visibility in Chef Automate

[edit on GitHub]

_images/a2_docs_banner.svg

Danger

This documentation applies to a deprecated version of Chef Automate and will reach its End-Of-Life on December 31, 2019. See the Chef Automate site for current documentation. The new Chef Automate includes newer out-of-the-box compliance profiles, an improved compliance scanner with total cloud scanning functionality, better visualizations, role-based access control and many other features. The new Chef Automate is included as part of the Chef Automate license agreement and is available via subscription.

Chef Automate allows you to monitor and visualize node status and convergence events from any Chef servers or clients in your Chef Automate cluster during a Chef Infra Client run. This data can be filtered and searched in the UI using a simple query language. Searches can then be shared and saved for future reference.

Setup and Configuration

Setup and configuration for node visibility is done through the following steps:

  • Enable the node visibility feature after Chef Automate has been installed on a machine
  • Configure any Chef Infra Client and/or servers to connect to your Chef Automate server to begin ingesting data
  • (Optional) Stream event data out to a websocket consumer for further processing

See Configure Data Collection for more information on the initial setup and configuring Chef Infra Client and server for data ingestion, and Stream Data to learn how to stream data out for further processing.