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

[receiver/purefa] Purefa Receiver implementation for logs telemetry #29709

Closed
dgoscn opened this issue Dec 8, 2023 · 5 comments
Closed

[receiver/purefa] Purefa Receiver implementation for logs telemetry #29709

dgoscn opened this issue Dec 8, 2023 · 5 comments

Comments

@dgoscn
Copy link
Contributor

dgoscn commented Dec 8, 2023

Component(s)

receiver/purefa

Is your feature request related to a problem? Please describe.

The Pure Storage FlashArray Receiver supports only metrics telemetry and is necessary for the implementation of logs telemetry to collect health & alerts data and audit data.

Describe the solution you'd like

The current receiver should include support for logs.

Describe alternatives you've considered

No response

Additional context

cc @chrroberts-pure @jpkrohling

@dgoscn dgoscn added enhancement New feature or request needs triage New item requiring triage labels Dec 8, 2023
Copy link
Contributor

github-actions bot commented Dec 8, 2023

Pinging code owners for receiver/purefa: @jpkrohling @dgoscn @chrroberts-pure. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1 crobert-1 removed the needs triage New item requiring triage label Dec 8, 2023
@crobert-1
Copy link
Member

crobert-1 commented Dec 8, 2023

@dgoscn Do you have a description or link on how to collect logs from a Pure Storage FlashArray? Are you going to be adding configuration options to the receiver?

Removed needs triage as the code owner and original implementer is the one who submitted this enhancement.

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Apr 15, 2024
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants