Grepr supported integrations and regions
This page provides an overview of the observability platform and cloud storage integrations supported by the Grepr platform. This page also specifies the features supported by each integration, including whether it can be used as a source or a sink.
If you require an integration or AWS region that Grepr does not support, contact support@grepr.ai.
Grepr supported regions
The Grepr SaaS offering runs in only the AWS us-east-1 region.
Supported integrations: cloud storage
Grepr supports AWS S3 for storing, querying, and backfilling raw data. See Use AWS S3 as a Grepr data lake.
Supported integrations: observability platforms
A Grepr integration provides the configuration details needed to connect to an external system, such as an observability platform. Integrations support moving data into Grepr and between Grepr and external systems by enabling the creation of sources and sinks in your Grepr pipelines.
Some integrations support the automatic creation of reduction exceptions based on information returned by vendor tools. These exceptions ensure that Grepr passes through important messages without aggregation. For some integrations, this feature is available when the integration is enabled as a cloud source, which allows Grepr to read and process data from the external service. 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 | Exception parsing |
|---|---|---|---|
| Datadog | Yes | Yes | Yes |
| Splunk | HEC, HTTP | HEC only | Yes |
| Google Cloud Platform | Yes | No 1 | Not applicable 2 |
| Grafana Cloud | Yes | Yes | No |
| New Relic | Yes | Yes | No |
| OpenTelemetry | Yes | Yes | Not applicable |
| Sumo Logic | Yes | Yes | No |
| AWS S3 3 | Yes | No | 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 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. ↩