@grepr/cli 1.2.0 → 1.3.0-94fe60c

package/build/dist/docs-index/9fc7ecc8-48dd-4473-9cea-ad4319de2cc8.txt

@@ -1,24 +0,0 @@
-# WriteOtlp
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-  description: Name of the integration.
-
-- name: version (required)
-  type: integer
-  description: Version of the integration. Should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
-
-- name: payload (required)
-  type: `Otlp`
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this integration is associated with.
-
-- name: type (required)
-  type: enum: `otlp`
-  description: The type of the integration. This is used to determine the payload type.

package/build/dist/docs-index/a00cf03f-8551-4e18-aec4-67864cea41aa.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/a00cf03f-8551-4e18-aec4-67864cea41aa.txt

@@ -1,30 +0,0 @@
-# Delete a single OTLP integration secret header
-
-**DELETE** `/v1/integrations/otlp/{id}/secret-headers/{name}`
-
-**Operation ID**: `deleteSecretHeader`
-**Summary**: Delete a single OTLP integration secret header
-Deletes a single secret HTTP header from an OTLP integration.
-
-## Tags
-- OpenTelemetry Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-- **name** (required) - path
-  - Type: string
-
-## Responses
-
-### 204
-
-Secret header deleted successfully
-
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/a0fac060-5bef-497f-b9ac-921a1660b2d9.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/a0fac060-5bef-497f-b9ac-921a1660b2d9.txt

@@ -1,35 +0,0 @@
-# Add users to a team
-
-**POST** `/v1/teams/{id}/users`
-
-**Operation ID**: `addUsersToTeam`
-**Summary**: Add users to a team
-Add users to a team.
-
-## Tags
-- Teams
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `UsersUpdate`
-
-## Responses
-
-### 200
-
-The list of users and roles that were successfully assigned.
-
-- **Content-Type**: `application/json` / `UsersUpdate`
-### 401
-
-Unauthorized
-
-### 404
-
-Not Found

package/build/dist/docs-index/a12ff3d1-8138-4c77-bac7-0b630ef8ad45.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a12ff3d1-8138-4c77-bac7-0b630ef8ad45.txt

@@ -1,44 +0,0 @@
-# ReadS3DataWarehouse
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-  description: Name of the integration.
-
-- name: version (required)
-  type: integer
-  description: Version of the integration. Should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
-
-- name: payload (required)
-  type: `S3DataWarehouse`
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this integration is associated with.
-
-- name: id (required)
-  type: string
-  description: The integration id
-
-- name: organizationId (required)
-  type: string
-  description: Organization ID of the integration.
-
-- name: jobIds (required)
-  type: array of string
-  description: List of job IDs associated with the integration.
-
-- name: createdAt (required)
-  type: string
-  description: Timestamp when the integration was created.
-
-- name: updatedAt (required)
-  type: string
-  description: Timestamp when the integration was last updated.
-
-- name: type (required)
-  type: enum: `s3-data-warehouse`
-  description: The type of the integration. This is used to determine the payload type.

package/build/dist/docs-index/a1524187-861d-4e3a-8717-d251ce562272.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a1524187-861d-4e3a-8717-d251ce562272.txt

@@ -1,18 +0,0 @@
-# Resource
-
-Resource information describing the entity that produced the telemetry data.
-
-**Type**: `object`
-
-## Properties
-
-- name: droppedAttributesCount (optional)
-  type: integer
-  description: Number of attributes that were dropped due to limits.
-
-- name: entityRefs (optional)
-  type: array of `EntityRef`
-  description: Set of entities that participate in this Resource.
-
-- name: attributes (optional)
-  type: `Variant`

package/build/dist/docs-index/a189174a-0027-477e-8fc8-dfe13b5f25bc.json

@@ -1 +0,0 @@
-{"docType":"doc"}

package/build/dist/docs-index/a189174a-0027-477e-8fc8-dfe13b5f25bc.txt

@@ -1,142 +0,0 @@
----
-description: "Grepr's SOC 2 Type II certified security program includes enterprise infrastructure, compliance, and data protection for secure observability."
----
-
-import { HiddenFAQ } from '@/components/HiddenFAQ'
-
-# Security in the Grepr platform
-
-At Grepr, security is foundational to everything Grepr builds. The robust security program ensures your data remains protected, meeting stringent compliance requirements while enabling your business to operate with confidence.
-
-## Trust and compliance
-
-### SOC 2 Type II certification
-
-Grepr has successfully completed a SOC 2 Type II audit by an independent third-party auditor, verifying that security controls are not only well-designed but operating effectively over time. This rigorous assessment validates commitment to:
-
-- **Security**: Protecting customer data and systems from unauthorized access.
-- **Availability**: Ensuring systems are available as committed.
-- **Processing integrity**: Processing data completely, accurately, and in a timely manner.
-- **Confidentiality**: Protecting information designated as confidential.
-- **Privacy**: Handling personal information in accordance with privacy commitments.
-
-To request the complete SOC 2 Type II report, please contact the [security team](mailto:security@grepr.io).
-
-For the most information on subprocessors and compliance certifications, visit the [Trust Center](https://trust.grepr.ai/).
-
-## Security architecture
-
-### Authenticate to the Grepr platform
-
-- **Secure identity management**: Authentication to the Grepr UI uses OAuth 2.0 with [Auth0](https://auth0.com/). Grepr supports SAML as well as OpenID Connect (OIDC) to ease and secure identity management for customers.
-- **API security**: All Grepr APIs implement OAuth 2.0 for robust authentication and authorization.
-- **Zero credential storage**: Grepr does not store your passwords or credentials in data stores. Grepr partners with [Auth0](https://auth0.com/) for secure identity and access management.
-- **Role-based access controls**: Granular permissions ensure you can only access the resources you need.
-
-### Infrastructure security
-
-- **Amazon Web Services (AWS) enterprise infrastructure**: The production environment runs on AWS, utilizing industry-leading security features and best practices.
-- **Network isolation**: All server infrastructure resides within dedicated AWS Virtual Private Clouds (VPCs) with no direct internet accessibility.
-- **Data encryption**: Data is encrypted both in transit (Transport Layer Security (TLS) 1.2+) and at rest using strong encryption standards.
-- **Secure data architecture**: Grepr implements efficient data storage using Apache Parquet and Apache Iceberg table formats, with raw data secured in Amazon S3.
-- **API key security**: API keys are securely stored in AWS Secrets Manager with strict access controls.
-
-### Vulnerability management and remediation
-
-- **Continuous vulnerability scanning**: Infrastructure and applications undergo regular automated and manual security scans to identify potential vulnerabilities.
-- **Software composition analysis**: Grepr continuously monitors software dependencies and libraries for known vulnerabilities through automated tools integrated into the CI/CD pipeline.
-- **Rapid remediation**: Critical vulnerabilities are addressed within 24 hours, with clear Service Level Agreements (SLAs) for all severity levels.
-- **Patch management**: Grepr maintains a structured process for timely application of security patches across infrastructure and application stack.
-- **Third-party security assessments**: Regular independent security assessments complement the internal vulnerability management program.
-
-### Proactive security operations
-
-- **Continuous monitoring**: Advanced monitoring, alerting, and intrusion detection systems provide real-time visibility into security posture.
-- **Threat intelligence**: Grepr leverages industry threat intelligence to stay ahead of emerging security threats.
-- **Penetration testing**: Independent third-party security firms conduct regular penetration tests of infrastructure and applications. Reports are available upon request.
-
-## Enterprise security program
-
-### Governance and risk management
-
-- **Security policies**: Grepr maintains formal, regularly-reviewed policies covering information security, risk management, and operational security.
-- **Risk assessment**: Systematic evaluation processes identify, assess, and mitigate security risks.
-- **Vendor security assessment**: Grepr rigorously evaluates third-party vendors to ensure they meet security standards.
-
-### Employee security
-
-- **Security training**: All employees complete mandatory security awareness training upon joining and regularly thereafter.
-- **Secure development**: Engineers follow secure coding practices, with security reviews integrated throughout the development lifecycle.
-- **Access controls**: Grepr enforces least-privilege access controls and multi-factor authentication for all staff.
-
-### Business continuity
-
-- **Disaster recovery**: Disaster recovery plans ensure business continuity in adverse situations.
-- **Data backups**: Regular data backups with verified recovery procedures protect your information.
-- **High availability design**: The architecture minimizes single points of failure for critical systems.
-
-### Incident response
-
-- **Incident management framework**: A formal incident response plan guides handling of security events.
-- **Response team**: The dedicated security team is prepared to respond rapidly to security incidents.
-- **Breach notification**: Clear procedures ensure timely and appropriate communications in the event of a security incident.
-
-## Deployment options
-
-- **Software as a Service (SaaS) deployment**: The standard cloud offering provides enterprise security with minimal overhead.
-- **Private cloud**: For organizations with strict compliance requirements, Grepr offers private cloud deployment options.
-
-## Security assurance
-
-Grepr understands that enterprise buyers require ongoing assurance of security practices:
-
-- **Regular attestations**: The SOC 2 Type II certification is renewed annually.
-- **Transparency**: Grepr is committed to clear communication about security practices.
-- **Continuous improvement**: The security program evolves with emerging threats and best practices.
-
-## Contact the security team
-
-For detailed security information, compliance documentation, or to report security concerns, please contact the security team at [security@grepr.io](mailto:security@grepr.io).
-
-<HiddenFAQ faqs={[
-  {
-    q: "Is Grepr SOC 2 certified?",
-    a: "Yes, Grepr has completed a SOC 2 Type II audit verifying that security controls are well-designed and operating effectively. The certification covers security, availability, processing integrity, confidentiality, and privacy."
-  },
-  {
-    q: "How does Grepr authenticate users?",
-    a: "Grepr uses OAuth 2.0 with Auth0 for UI authentication and supports SAML and OpenID Connect (OIDC) for enterprise identity management. Grepr does not store passwords or credentials directly."
-  },
-  {
-    q: "How are Grepr APIs secured?",
-    a: "All Grepr APIs implement OAuth 2.0 for robust authentication and authorization. Access tokens are obtained from Auth0 and must be included as Bearer tokens in API requests."
-  },
-  {
-    q: "How is data encrypted in Grepr?",
-    a: "Data is encrypted in transit using TLS 1.2 or higher and at rest using strong encryption standards. API keys are securely stored in AWS Secrets Manager with strict access controls."
-  },
-  {
-    q: "What infrastructure does Grepr use?",
-    a: "Grepr runs on Amazon Web Services (AWS) enterprise infrastructure with dedicated Virtual Private Clouds (VPCs). The infrastructure includes network isolation, advanced monitoring, and automated security scanning."
-  },
-  {
-    q: "How does Grepr manage vulnerabilities?",
-    a: "Grepr conducts continuous automated and manual security scans, monitors software dependencies for known vulnerabilities, and maintains strict SLAs for remediation (24 hours for critical vulnerabilities)."
-  },
-  {
-    q: "Does Grepr perform penetration testing?",
-    a: "Yes, independent third-party security firms conduct regular penetration tests of Grepr infrastructure and applications. Penetration testing reports are available upon request."
-  },
-  {
-    q: "What are Grepr's access control practices?",
-    a: "Grepr enforces least-privilege access controls for all staff, requires multi-factor authentication, and implements role-based access controls (RBAC) for granular permissions."
-  },
-  {
-    q: "How does Grepr handle security incidents?",
-    a: "Grepr maintains a formal incident response plan with a dedicated security team prepared to respond rapidly. Clear procedures ensure timely notification in the event of a security incident."
-  },
-  {
-    q: "Can I get the complete Grepr security documentation?",
-    a: "Yes, contact the security team at security@grepr.io to request the complete SOC 2 Type II report, subprocessor information, compliance certifications, and other security documentation."
-  }
-]} />

package/build/dist/docs-index/a248212d-cb47-40c4-8499-4a593c01b9ba.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a248212d-cb47-40c4-8499-4a593c01b9ba.txt

@@ -1,13 +0,0 @@
-# GreprJobGraph
-
-**Type**: `object`
-
-## Properties
-
-- name: vertices (required)
-  type: array of `Operation`
-  description: Operations that make up the vertices of the Grepr job graph
-
-- name: edges (required)
-  type: array of string
-  description: Edges that connect the vertices of the Grepr job graph

package/build/dist/docs-index/a2de4fc2-05ab-4151-826a-e2b8eafd7ce6.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/a2de4fc2-05ab-4151-826a-e2b8eafd7ce6.txt

@@ -1,28 +0,0 @@
-# updateRolesForUserInTeam
-
-**PUT** `/v1/teams/{id}/users/{userId}/roles`
-
-**Operation ID**: `updateRolesForUserInTeam`
-**Summary**: No summary provided.
-## Tags
-- Teams
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-- **userId** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `RoleUpdate`
-
-## Responses
-
-### default
-
-default response
-
-- **Content-Type**: `application/json` / `RoleUpdate`

package/build/dist/docs-index/a326fad4-579d-4c41-bdc9-144f647804e4.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a326fad4-579d-4c41-bdc9-144f647804e4.txt

@@ -1,16 +0,0 @@
-# LogsBranch
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-
-- name: predicate (required)
-  type: `EventPredicate`
-
-- name: type (required)
-  type: enum: `logs-branch`
-  description: Splits events based on a predicate. Positive matches go to the main output. Negative matches go to the 'else' output.
-

package/build/dist/docs-index/a3467ff6-5d96-40bd-b1cb-29f6b6acef34.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a3467ff6-5d96-40bd-b1cb-29f6b6acef34.txt

@@ -1,16 +0,0 @@
-# ParseQueryResponse
-
-**Type**: `object`
-
-## Properties
-
-- name: valid (optional)
-  type: boolean
-  description: Whether a query is valid.
-
-- name: errorMessage (optional)
-  type: string
-  description: The error message if there is an error
-
-- name: parsedQuery (optional)
-  type: `ParsedQueryTree`

package/build/dist/docs-index/a59b583b-71a7-49e2-a36d-855b030ae289.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a59b583b-71a7-49e2-a36d-855b030ae289.txt

@@ -1,13 +0,0 @@
-# MessageExactMatchNode
-
-**Type**: `object`
-
-## Properties
-
-- name: exactValue (required)
-  type: string
-  description: The exact message value to match.
-
-- name: type (required)
-  type: enum: `message-exact-match-node`
-  description: A node that represents an exact message match in a parsed query.

package/build/dist/docs-index/a5b9fa37-dcc4-4e58-858a-b0dc1f77ea19.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/a5b9fa37-dcc4-4e58-858a-b0dc1f77ea19.txt

@@ -1,24 +0,0 @@
-# Delete a Datadog integration
-
-**DELETE** `/v1/integrations/datadog/{id}`
-
-**Operation ID**: `delete`
-**Summary**: Delete a Datadog integration
-Deletes an integration to connect to Datadog. This will delete the associated keys as well. No-op if already deleted.
-
-## Tags
-- Datadog Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Responses
-
-### 204
-
-Integration deleted successfully
-
-### 401
-
-Unauthorized

package/build/dist/docs-index/a60ce768-5e6c-498f-9582-2794d9f6b3b6.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/a60ce768-5e6c-498f-9582-2794d9f6b3b6.txt

@@ -1,34 +0,0 @@
-# Creates or updates a Datadog integration api key
-
-**PUT** `/v1/integrations/datadog/{id}/api-key`
-
-**Operation ID**: `upsertApiKey`
-**Summary**: Creates or updates a Datadog integration api key
-Creates an API key for a Datadog integration if it doesn't exist and updates it otherwise.  If the key is updated while the integration is being used by a pipeline, the  new key will be picked at pipeline restart, rescaling or an update.  Ingestion supports the previous and the updated key for up to 24 hours of  a key update. Make sure to change the key used by the agents to send data within  24 hours of an update for a seamless transition
-
-## Tags
-- Datadog Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `SecretApi`
-
-## Responses
-
-### 204
-
-Api key upserted successfully.
-
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.

package/build/dist/docs-index/a6deaf28-ed38-4368-85ff-4cd1b2534a1f.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a6deaf28-ed38-4368-85ff-4cd1b2534a1f.txt

@@ -1,14 +0,0 @@
-# TraceAction
-
-Base class for trace actions. Actions execute on traces matching SQL predicates after sampling decisions have been made.
-
-**Type**: `object`
-
-## Properties
-
-- name: actionId (required)
-  type: string
-  description: Unique identifier for this action within the TraceReducer. Must be alphanumeric with hyphens and underscores only.
-
-- name: type (required)
-  type: string

package/build/dist/docs-index/a6fd4d6e-d905-4555-be8f-dbb78fa723b6.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a6fd4d6e-d905-4555-be8f-dbb78fa723b6.txt

@@ -1,29 +0,0 @@
-# backfillQuery
-
-The query to use for the backfill. This scopes the data that will be backfilled into the sink. It can also refer to variables generated by a trigger. Variables use __ (a double underscore) at the beginning and they are specified as part of the trigger description.
-
-**Type**: `object`
-
-## One Of
-
-This schema accepts one of the following types:
-
-### Option 1
-`DatadogQueryPredicate`
-
-### Option 2
-`MetricEventPredicate`
-
-### Option 3
-`SplQueryPredicate`
-
-### Option 4
-`NewRelicQueryPredicate`
-
-### Option 5
-`NrqlQueryPredicate`
-
-## Properties
-
-- name: query (optional)
-  type: string

package/build/dist/docs-index/a8e30f67-0037-46eb-9b7b-ae2a8e3871b3.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a8e30f67-0037-46eb-9b7b-ae2a8e3871b3.txt

@@ -1,44 +0,0 @@
-# ReadDataWarehouse
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-  description: Name of the integration.
-
-- name: version (required)
-  type: integer
-  description: Version of the integration. Should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
-
-- name: payload (required)
-  type: `DataWarehouse`
-
-- name: teamIds (optional)
-  type: array of string
-  description: The team IDs that this integration is associated with.
-
-- name: id (required)
-  type: string
-  description: The integration id
-
-- name: organizationId (required)
-  type: string
-  description: Organization ID of the integration.
-
-- name: jobIds (required)
-  type: array of string
-  description: List of job IDs associated with the integration.
-
-- name: createdAt (required)
-  type: string
-  description: Timestamp when the integration was created.
-
-- name: updatedAt (required)
-  type: string
-  description: Timestamp when the integration was last updated.
-
-- name: type (required)
-  type: enum: `data-warehouse`
-  description: The type of the integration. This is used to determine the payload type.

package/build/dist/docs-index/a8fde5fb-7db5-4f0c-8115-3c99c6df7a19.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/a8fde5fb-7db5-4f0c-8115-3c99c6df7a19.txt

@@ -1,43 +0,0 @@
-# Update a custom role
-
-**PUT** `/v1/roles/{roleId}`
-
-**Operation ID**: `updateRole`
-**Summary**: Update a custom role
-Updates an existing custom role. System roles cannot be updated.
-
-## Tags
-- Roles
-## Parameters
-
-- **roleId** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `UpdateRole`
-
-## Responses
-
-### 200
-
-Role updated successfully
-
-- **Content-Type**: `application/json` / `Role`
-### 400
-
-Invalid request data or system role
-
-### 403
-
-Insufficient permissions
-
-### 404
-
-Role not found
-
-### 409
-
-Role name already exists

package/build/dist/docs-index/a97c2107-7209-4deb-b64d-91f0ec296c9f.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/a97c2107-7209-4deb-b64d-91f0ec296c9f.txt

@@ -1,28 +0,0 @@
-# SplunkLogSink
-
-**Type**: `object`
-
-## Properties
-
-- name: name (required)
-  type: string
-
-- name: integrationId (required)
-  type: string
-  description: The Splunk integration id.
-
-- name: additionalTags (optional)
-  type: array of string
-  description: Additional tags to add to the logs when writing to Splunk. Gets combined with the integration's additionalTags.
-
-- name: indexOverride (optional)
-  type: string
-  description: Override index to be set when writing to Splunk
-
-- name: defaultIndex (optional)
-  type: string
-  description: Default index to be set when writing to Splunk if no index is set.
-
-- name: type (required)
-  type: enum: `splunk-log-sink`
-  description: Writes processed events to splunk.