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

adds second part of tracing system calls using eBPF blog #1149

Conversation

ashutoshcloud
Copy link
Contributor

@ashutoshcloud ashutoshcloud commented Sep 14, 2023

Signed-off-by: ashutoshcloud ( [email protected] ) (CloudDefense.AI)

What type of PR is this?

/kind content

Any specific area of the project related to this PR?

/area blog

What this PR does / why we need it:

This PR adds second part for the blog Tracing System Calls Using eBPF

Issif and others added 4 commits September 20, 2023 10:17
Signed-off-by: Thomas Labarussias <[email protected]>
Signed-off-by: ashutoshreddy <[email protected]>
Signed-off-by: Mike Coleman <[email protected]>
Signed-off-by: ashutoshreddy <[email protected]>
Signed-off-by: Mike Coleman <[email protected]>
Signed-off-by: ashutoshreddy <[email protected]>
Signed-off-by: ashutoshreddy <[email protected]>
@poiana
Copy link

poiana commented Sep 20, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ashutoshcloud
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

title: Tracing System Calls Using eBPF - Part 2
linktitle: Tracing System Calls Using eBPF - Part 2
description: Learn how to trace system calls using eBPF probes.
date: 2023-09-12
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
date: 2023-09-12
date: 2023-09-21

@poiana
Copy link

poiana commented Dec 20, 2023

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 Jan 19, 2024

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

@leogr
Copy link
Member

leogr commented Feb 14, 2024

/remove-lifecycle rotten

@leogr
Copy link
Member

leogr commented Feb 14, 2024

Hey @ashutoshcloud

Could you address the conflicts?

Also, is there anything missing here? cc @Issif

@poiana
Copy link

poiana commented May 14, 2024

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

@ashutoshcloud
Copy link
Contributor Author

ashutoshcloud commented May 15, 2024 via email

@leogr
Copy link
Member

leogr commented May 16, 2024

sure leonardo, let me see what is the issue

On Wed, Feb 14, 2024 at 9:47 PM Leonardo Grasso @.> wrote: Hey @ashutoshcloud https://github.com/ashutoshcloud Could you address the conflicts? Also, is there anything missing here? cc @Issif https://github.com/Issif — Reply to this email directly, view it on GitHub <#1149 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5X7L2GMAERUAEO7H64ENEDYTTPTBAVCNFSM6AAAAAA4YCMLSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBUGE3DAMBUGQ . You are receiving this because you were mentioned.Message ID: @.>

Hey @ashutoshcloud

Let me know if you need any support with this. Thank you!

@leogr
Copy link
Member

leogr commented May 16, 2024

@leogr
Copy link
Member

leogr commented May 16, 2024

/remove-lifecycle stale
/assign

@poiana
Copy link

poiana commented Aug 14, 2024

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 Sep 13, 2024

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 Oct 13, 2024

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 poiana closed this Oct 13, 2024
@poiana
Copy link

poiana commented Oct 13, 2024

@poiana: Closed this PR.

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants