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

Allow users to select fields displayed in an event #20

Closed
coccyx opened this issue Jan 21, 2021 · 2 comments · Fixed by #821
Closed

Allow users to select fields displayed in an event #20

coccyx opened this issue Jan 21, 2021 · 2 comments · Fixed by #821
Assignees
Labels
Milestone

Comments

@coccyx
Copy link
Collaborator

coccyx commented Jan 21, 2021

No description provided.

@coccyx coccyx added the cli label Jan 21, 2021
@coccyx coccyx self-assigned this Jan 21, 2021
@iapaddler iapaddler assigned seanvaleo and unassigned coccyx Mar 2, 2022
@ghost ghost added this to the Next Maintenance (1.0.2) milestone Mar 3, 2022
@seanvaleo
Copy link
Collaborator

QA INSTRUCTIONS

Part 1
Do:

docker run --rm -it cribl/scope:<VERSION_ID>
apt update
apt install curl -y
scope curl wttr.in
scope events
scope events --fields net_bytes_recv
scope events --fields net_bytes_sent,net_bytes_recv
scope events --fields net_bytes_sent,net_bytes_recv --match net_bytes
scope events --fields nonexistent
# etc...

Expect:
You are able to select any field from the event.body.data object. View the json output with scope events -j to see data field names.

@seanvaleo seanvaleo linked a pull request Mar 7, 2022 that will close this issue
@jrcheli
Copy link
Contributor

jrcheli commented Mar 10, 2022

I bugathoned this with v1.0.2-rc0 on 10-Mar-2022. Looks great!

@abetones abetones added release-note Issues & PRs that should be listed in release notes and removed release-note Issues & PRs that should be listed in release notes labels Mar 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants