Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New component: Snowflake Receiver #14754

Closed
1 of 2 tasks
shalper2 opened this issue Oct 6, 2022 · 2 comments · Fixed by #14778
Closed
1 of 2 tasks

New component: Snowflake Receiver #14754

shalper2 opened this issue Oct 6, 2022 · 2 comments · Fixed by #14778
Labels
Accepted Component New component has been sponsored

Comments

@shalper2
Copy link
Contributor

shalper2 commented Oct 6, 2022

The purpose and use-cases of the new component

Snowflake is a fast growing data cloud company which allows users to store, manipulate, and analyze data in a SaaS platform. Its database functionality has found use across multiple industries and the technology is quickly becoming foundational to new and existing platforms.

The Snowflake receiver would be used to connect to snowflake and then perform queries, converting any results into metrics. Examples could be billing metrics, performance metrics, and security related metrics such as log in attempts. All queries supported by this receiver will be pre defined and included in the receiver module and will target a specific set of metrics to provide parity with existing tools.

While snowflake metrics are accessible through the likes of the signalfx smart agent it makes sense to include a native receiver to improve user experience and reduce the number of tools a customer might need to satisfy their operational requirements.

Example configuration for the component

receivers:
  snowflakedb:
    username: snow
    password: flake
    account: isvery-cool
    warehouse: metricswarehouse
    database: snowflake # defaults to 'snowflake'
    role: accountadmin # defaults to accountadmin (this is inline with default permissions)
    metrics:  # all metrics default to enabled, created using mdatagen
      <metric_name>:
        enabled: <true|false>

Telemetry data types supported

metrics

Is this a vendor-specific component?

  • This is a vendor-specific component
  • If this is a vendor-specific component, I am proposing to contribute this as a representative of the vendor.

Sponsor (optional)

No response

Additional context

No response

@shalper2 shalper2 added the needs triage New item requiring triage label Oct 6, 2022
@codeboten codeboten added Sponsor Needed New component seeking sponsor and removed needs triage New item requiring triage labels Oct 7, 2022
@jpkrohling
Copy link
Member

Given that this is a vendor-specific component, I believe we should call the next sponsor in line.

@dmitryax, are you the next in line, or is the table outdated?

https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#rotating-sponsors

@dmitryax
Copy link
Member

That's correct. I should be the next sponsor

@dmitryax dmitryax added Accepted Component New component has been sponsored and removed Sponsor Needed New component seeking sponsor labels Oct 10, 2022
dmitryax added a commit that referenced this issue Oct 10, 2022
dmitryax added a commit that referenced this issue Oct 10, 2022
Rotate the sponsors list

I'm taking #14754
shalper2 pushed a commit to shalper2/opentelemetry-collector-contrib that referenced this issue Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Component New component has been sponsored
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants