Grepr supported integrations and regions
This page provides a comprehensive overview of the integrations supported by the Grepr platform, including observability platform and cloud storage integrations. This page also specifies the features supported by those integrations, such as whether an integration can be used as a source or sink, or if a vendor’s query language is supported.
The Grepr platform is continuously enhanced based on customer requirements. If you require an integration or AWS region not supported by Grepr, contact our support team at support@grepr.ai.
Grepr supported regions
The Grepr SaaS offering runs in only the AWS us-east-1 region.
Supported integrations: data lake storage
Grepr supports AWS S3 for storing, querying, and backfilling raw data. See Use AWS S3 as a Grepr data lake.
Supported integrations: data sources and sinks
Data sources and sinks are used to flow data into and out of the Grepr platform. These are typically integrations with third-party observability platforms. For some integrations, Grepr also supports:
- The vendor’s native query language, such as the Datadog, New Relic, or Splunk query languages.
- The automatic creation of reduction exceptions based on information returned by vendor tools. These exceptions ensure that important messages are passed through without aggregation. To learn more, see Selective Reduction with Exceptions.
The following are the observability platform and tool integrations supported by Grepr as data sources and sinks:
| Integration | As source | As sink | Query language | Exception parsing |
|---|---|---|---|---|
| Datadog | Yes | Yes | Yes | Yes |
| Splunk | HEC, HTTP | HEC only | Yes | Yes |
| Google Cloud Platform | Yes | No 1 | Not applicable 2 | Not applicable 3 |
| New Relic | Yes | Yes | No | No |
| OpenTelemetry | Yes | Yes | Not applicable | Not applicable |
| Sumo Logic | Yes | Yes | No | No |
| AWS CloudTrail | Yes | Not applicable | Not applicable | Not applicable |
| AWS S3 4 | Yes | No | Not applicable | Not applicable |
Footnotes
-
Although Grepr supports streaming data from GCP, you cannot use GCP as a sink. Instead, you configure a supported sink for the output from your Grepr pipeline. To learn more, see Google Cloud Platform observability with Grepr and Datadog. ↩
-
Because GCP data is sent to a non-GCP sink, you can use the query language capabilities of the sink integration. For example, if you use the Datadog integration as a sink, you can use the Datadog query language. ↩
-
Because the exception parsing feature is configured as a separate step in your pipeline, support for this feature is based on the sink configured on the pipeline. ↩
-
The support mentioned in this table is for reading from arbitrary files in AWS S3 and writing to files in arbitrary formats, such as JSON or plain text. To learn about using S3 as data lake storage, see Use AWS S3 as a Grepr data lake. ↩