Skip to Content
Sources and SinksIntegrationsOverview

What are Grepr integrations?

A Grepr integration is a configured connection to an external system that enables data exchange between Grepr and that system. Integrations provide the technical foundation for creating sources and sinks in your data pipeline.

Grepr supports two primary types of integrations:

  • Observability platform integrations Connect to monitoring, logging, and APM platforms
  • Cloud storage integrations - Connect to object storage and data warehouse services

Integrations are directly linked to sources and sinks: sources use integrations to read data from external systems, while sinks use integrations to write processed data to external destinations.

Datadog

The Datadog integration supports connecting to Datadog, and supports sourcing data from several Datadog compatible collectors.

See Datadog integration.

Splunk

The Splunk integration provides connectivity to Splunk through Splunk’s HTTP Event Collector (HEC) or S2S over HTTP. This integration supports reading data from Splunk collectors and writing data to Splunk indexes. You can create both sources and sinks using this integration.

See Splunk integration.

New Relic

The New Relic integration connects to New Relic’s observability platform. Use this integration to create sources that retrieve log data from New Relic collectors and sinks that send processed data to New Relic for monitoring and analysis.

See New Relic integration.

Sumo Logic

The Sumo Logic integration connects to Sumo Logic’s cloud-based log management and monitoring platform using the Sumo Logic OTLP/HTTP Source. You can use the integration to create sources that ingest data from Sumo Logic collectors and sinks that send processed data to Sumo Logic.

See Sumo Logic integration.

Google Cloud Platform (GCP)

The GCP integration enables you to stream logs from Google Cloud services to Grepr for processing and analysis, then forward the processed logs to any Grepr-supported observability platform or tool, such as Datadog, Splunk, or New Relic.

See Google Cloud Platform observability with Grepr.

Cloud storage

The Grepr data lake uses AWS S3 to store, manage, and support querying the raw data from your Grepr pipelines. Depending on your requirements, you can choose from two S3 integrations: a Grepr-hosted integration which uses a Grepr-managed S3 bucket, and an integration that uses an S3 bucket in your account. Both integrations provide secure, managed, and efficient storage for your data and an optimized query interface.

To configure the Grepr-hosted integration you only need to assign a name for the integration, and the Grepr platform deploys and manages the S3 bucket.

To use the integration with your own S3 bucket requires that you deploy and configure an S3 bucket in your AWS account, but provides more control of your data. See Host a Grepr data lake with the AWS S3 integration.

Last updated on