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

Add tags in the response message of outputs.proto #855

Closed
leodido opened this issue Sep 25, 2019 · 16 comments
Closed

Add tags in the response message of outputs.proto #855

leodido opened this issue Sep 25, 2019 · 16 comments

Comments

@leodido
Copy link
Member

leodido commented Sep 25, 2019

What would you like to be added:

A (repeated) field in the response message output.proto protobuf definition aimed at tagging the outputs that the gRPC output server emits.

Also we probably want the tags field to be in the request message too for filtering.

Why is this needed:

To provide a mechanism to filter/tag output events. Ref #822.

@stale
Copy link

stale bot commented Nov 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Nov 24, 2019
@stale stale bot closed this as completed Dec 1, 2019
@fntlnz
Copy link
Contributor

fntlnz commented Dec 1, 2019

I still like this !

@fntlnz fntlnz reopened this Dec 1, 2019
@stale stale bot removed the wontfix label Dec 1, 2019
@stale
Copy link

stale bot commented Jan 30, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 30, 2020
@stale stale bot closed this as completed Feb 6, 2020
@leodido leodido reopened this Feb 28, 2020
@stale stale bot removed the wontfix label Feb 28, 2020
@stale
Copy link

stale bot commented Apr 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Apr 28, 2020
@fntlnz
Copy link
Contributor

fntlnz commented Apr 29, 2020 via email

@stale stale bot removed the wontfix label Apr 29, 2020
@stale
Copy link

stale bot commented Jun 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jun 28, 2020
@leodido
Copy link
Member Author

leodido commented Jun 29, 2020

Keep

@stale stale bot removed the wontfix label Jun 29, 2020
@stale
Copy link

stale bot commented Aug 29, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Issues labeled "cncf", "roadmap" and "help wanted" will not be automatically closed. Please refer to a maintainer to get such label added if you think this should be kept open.

@stale stale bot added the wontfix label Aug 29, 2020
@leodido
Copy link
Member Author

leodido commented Aug 31, 2020

/help

@stale stale bot removed the wontfix label Aug 31, 2020
@stale
Copy link

stale bot commented Oct 31, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Issues labeled "cncf", "roadmap" and "help wanted" will not be automatically closed. Please refer to a maintainer to get such label added if you think this should be kept open.

@stale stale bot added the wontfix label Oct 31, 2020
@leogr
Copy link
Member

leogr commented Nov 2, 2020

/help

@poiana
Copy link

poiana commented Nov 2, 2020

@leogr:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@stale stale bot removed wontfix labels Nov 2, 2020
@poiana
Copy link

poiana commented Jan 31, 2021

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

@poiana
Copy link

poiana commented Mar 2, 2021

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

@poiana
Copy link

poiana commented Apr 1, 2021

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana
Copy link

poiana commented Apr 1, 2021

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@poiana poiana closed this as completed Apr 1, 2021
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

4 participants