You have several options for getting data into Wavefront:
- You use one or more collector agents and the Wavefront proxy. A collector agent, such as Telegraf or Docker cAdvisor, collects metrics such as capacity and usage from your systems, and outputs them to the Wavefront proxy. The Wavefront proxy works with the Wavefront service to ensure security and end-to-end flow control. See Wavefront Proxies
- If you have a metrics collection infrastructure, your application uses the metrics library to send log files or metrics directly to a Wavefront proxy.
- Wavefront pulls data directly from the cloud, for example, from Amazon Web Services.
The diagram below shows all options.
Wavefront offers many pre-built integrations for different data collection and monitoring tools. Some integrations are Wavefront specific. Others rely on an existing integration between that tool and Graphite. Wavefront natively accepts the Graphite data format. To see all currently available integration, select Integrations from the menu bar. This documentation has additional detail about some integrations.
Wavefront proxies support the following data formats:
- Wavefront data format
- Graphite data format (plaintext and pickle)
- OpenTSDB data format (Telnet interface and HTTP API (JSON))
Before streaming data, we recommend that you understand best practices for naming your data.
Amazon Web Services Integration
The Amazon Web Services integration directly supports ingesting CloudWatch, CloudTrail, and AWS service data. For details on setting up different types of AWS integrations and the metrics available, see:
To quickly get going with getting data into Wavefront, follow the steps in the in-product Getting Started workflow. This workflow explains how to get data flowing from your local machine or from an Amazon Web Service.