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

[Zeek] Add additional data sets #3340

Merged
merged 12 commits into from
Jun 28, 2022
Merged

Conversation

legoguy1000
Copy link
Contributor

@legoguy1000 legoguy1000 commented May 11, 2022

What does this PR do?

Add new data sets for known_hosts, known_certs, known_services, & software logs files.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@legoguy1000 legoguy1000 requested a review from a team as a code owner May 11, 2022 15:46
@elasticmachine
Copy link

elasticmachine commented May 11, 2022

❕ Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Start Time: 2022-05-11T15:47:16.897+0000

  • Duration: 2 min 23 sec

Steps errors 2

Expand to view the steps failures

Google Storage Download
  • Took 0 min 0 sec . View more details here
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: githubApiCall: The REST API call https://api.github.com/orgs/elastic/members/legoguy1000 return the message : java.lang.Exception: httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/legoguy1000 : httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/legoguy1000 : Code: 404Error: {"message":"User does not exist or is not a member of the organization","documentation_url":"https://docs.github.com/rest/reference/orgs#check-organization-membership-for-a-user"}

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

elasticmachine commented May 12, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-06-28T01:49:12.499+0000

  • Duration: 71 min 30 sec

Test stats 🧪

Test Results
Failed 0
Passed 219
Skipped 0
Total 219

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@jamiehynds jamiehynds added Integration:zeek Zeek enhancement New feature or request labels May 12, 2022
packages/zeek/_dev/build/docs/README.md Outdated Show resolved Hide resolved
packages/zeek/data_stream/software/fields/ecs.yml Outdated Show resolved Hide resolved
packages/zeek/data_stream/software/fields/fields.yml Outdated Show resolved Hide resolved
packages/zeek/_dev/build/docs/README.md Outdated Show resolved Hide resolved
packages/zeek/_dev/build/docs/README.md Show resolved Hide resolved
packages/zeek/_dev/build/docs/README.md Outdated Show resolved Hide resolved
packages/zeek/_dev/build/docs/README.md Outdated Show resolved Hide resolved
packages/zeek/data_stream/known_services/fields/ecs.yml Outdated Show resolved Hide resolved
packages/zeek/_dev/build/docs/README.md Outdated Show resolved Hide resolved
@efd6
Copy link
Contributor

efd6 commented May 16, 2022

/test

@legoguy1000
Copy link
Contributor Author

@efd6 can we retest

@efd6
Copy link
Contributor

efd6 commented May 20, 2022

/test

@elasticmachine
Copy link

elasticmachine commented May 20, 2022

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (43/43) 💚
Files 96.341% (79/82) 👎 -0.218
Classes 96.341% (79/82) 👎 -0.218
Methods 86.267% (647/750) 👎 -2.856
Lines 92.968% (8620/9272) 👍 2.933
Conditionals 100.0% (0/0) 💚

@efd6
Copy link
Contributor

efd6 commented May 20, 2022

/test

@legoguy1000
Copy link
Contributor Author

fixed the test error. Ready to retest.

@legoguy1000 legoguy1000 requested a review from efd6 June 13, 2022 12:59
@efd6
Copy link
Contributor

efd6 commented Jun 14, 2022

/test

@legoguy1000
Copy link
Contributor Author

@efd6 Any idea about the error from Elastic Machine or from Jenkins found 0 hits in logs-zeek.known_certs-ep data stream: index_not_found_exception: no such index [logs-zeek.known_certs-ep] Status=404??

Copy link
Contributor

@efd6 efd6 left a comment

Choose a reason for hiding this comment

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

Incidental to looking into the issue:

--- Test results for package: zeek - START ---
FAILURE DETAILS:
zeek/dns test-dns.log:
[0] parsing field value failed: the IP "40.126.31.143" is not one of the allowed test IPs (see: https://github.com/elastic/elastic-package/blob/main/internal/fields/_static/allowed_geo_ips.txt)
zeek/known_certs test-known_certs.log:
[0] parsing field value failed: field "event.kind"'s value "info" is not one of the allowed values (alert, enrichment, event, metric, state, pipeline_error, signal)
zeek/known_hosts test-known_hosts.log:
[0] parsing field value failed: field "event.kind"'s value "info" is not one of the allowed values (alert, enrichment, event, metric, state, pipeline_error, signal)
zeek/known_services test-known_services.log:
[0] parsing field value failed: field "event.kind"'s value "info" is not one of the allowed values (alert, enrichment, event, metric, state, pipeline_error, signal)
zeek/software test-software.log:
[0] parsing field value failed: field "event.kind"'s value "info" is not one of the allowed values (alert, enrichment, event, metric, state, pipeline_error, signal)

@efd6
Copy link
Contributor

efd6 commented Jun 15, 2022

The non-progress issue comes down to the absence of terminating new-lines in the test inputs. There are bunch of other inputs that suffer the same issue, but these all have more than one test line, so they pass because only a single event is required to allow a system test to pass (they would have been found if this were in place).

@legoguy1000
Copy link
Contributor Author

🤦‍♂️ ya I've had this issue before, good catch. I'll fix this in the AM and then I think we should be good.

@efd6
Copy link
Contributor

efd6 commented Jun 15, 2022

The other inputs that have the issue are

  • sample_logs/capture_loss.log
  • sample_logs/dhcp.log
  • sample_logs/files.log
  • sample_logs/notice.log
  • sample_logs/sip.log
  • sample_logs/snmp.log
  • sample_logs/ssh.log
  • sample_logs/ssl.log

@legoguy1000
Copy link
Contributor Author

@efd6 fixed

@efd6
Copy link
Contributor

efd6 commented Jun 15, 2022

/test

@legoguy1000
Copy link
Contributor Author

@efd6 I think i got it now 🤦

@efd6
Copy link
Contributor

efd6 commented Jun 16, 2022

That will fix the non-progress, but host is already populated. You will need to move the host assignments to other fields. I'm not sure where at this stage. I'm looking into this.

@efd6
Copy link
Contributor

efd6 commented Jun 16, 2022

/test

@legoguy1000
Copy link
Contributor Author

The forwarded tag needs to be added so that host is only set by zeek, not by the agent.

@legoguy1000 legoguy1000 requested a review from efd6 June 28, 2022 00:59
@efd6
Copy link
Contributor

efd6 commented Jun 28, 2022

/test

@efd6 efd6 merged commit a89fe94 into elastic:main Jun 28, 2022
@legoguy1000 legoguy1000 deleted the zeek-additional-logs branch June 28, 2022 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:zeek Zeek
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants