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: Pure Storage Receiver for FlashBlade #17528

Closed
1 of 2 tasks
dgoscn opened this issue Jan 11, 2023 · 3 comments · Fixed by #17906
Closed
1 of 2 tasks

New component: Pure Storage Receiver for FlashBlade #17528

dgoscn opened this issue Jan 11, 2023 · 3 comments · Fixed by #17906
Assignees
Labels
Accepted Component New component has been sponsored Vendor-Specific Component New component that interfaces with a vendor API and will be maintained by the vendor.

Comments

@dgoscn
Copy link
Contributor

dgoscn commented Jan 11, 2023

The purpose and use-cases of the new component

Pure Storage Receiver for OpenTelemetry

PureStorage has a product called FlashBlade. Currently, we export the arrays to vendor-specific backends, but we want to provide a receiver that will allow customers to send data to their backends of choice

It is possible to see the current FlashBlade OpenMetrics exporter here.

Example configuration for the component

receivers:
  purefb:
    endpoint: http://172.31.60.207:9491/metrics
    arrays:
    - address: gse-fb01
      auth:
        authenticator: bearertokenauth/fb01
    buckets:
    - address: gse-fb01
      auth:
        authenticator: bearertokenauth/fb01
    clients:
    - address: gse-fb01
      auth:
        authenticator: bearertokenauth/fb01
    file:
    - address: gse-fb01
      auth:
        authenticator: bearertokenauth/fb01
    usage:
    - address: gse-fb01
      auth:
        authenticator: bearertokenauth/fb01
    env: dev
    settings:
      reload_intervals:
        array: 
        buckets: 
        clients: 
        file: 
        usage:

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)

Juraci Paixão Kröhling @jpkrohling

Additional context

No response

@dgoscn dgoscn added the needs triage New item requiring triage label Jan 11, 2023
@atoulme atoulme added Vendor-Specific Component New component that interfaces with a vendor API and will be maintained by the vendor. Sponsor Needed New component seeking sponsor and removed needs triage New item requiring triage labels Jan 13, 2023
@atoulme
Copy link
Contributor

atoulme commented Jan 15, 2023

@jpkrohling would you please confirm you are ok to sponsor this component? Thanks!

@jpkrohling
Copy link
Member

I'm this component's sponsor.

@jpkrohling jpkrohling added Accepted Component New component has been sponsored and removed Sponsor Needed New component seeking sponsor labels Jan 20, 2023
@dgoscn
Copy link
Contributor Author

dgoscn commented Jan 23, 2023

cc @chrroberts-pure

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 Vendor-Specific Component New component that interfaces with a vendor API and will be maintained by the vendor.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants