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

[Enhancement] [Jamf Compliance Reporter] Make enhancement in connector with best practices implementation #4574

Merged

Conversation

vinit-chauhan
Copy link
Contributor

Type of change

  • Enhancement

What does this PR do?

Make enhancement in Jamf Compliance Reporter connector with listed best practices.

Sr. NO. Best Practices
1 Verify best practices test cases are executed
2 Verify all automated tests
3 Verify default values of port for TCP, UDP or HTTP Endpoint Input
4 Verify that the data is ingested in kibana for in interval
5 Verify all fields are correctly mapped for all Data streams
6 Verify related.ip field in datastream
7 Verify related.hash field in datastream
8 Verify related.hosts field in datastream
9 Verify related.user field in datastream
10 Verify MAC address should be separated by dash and value should be an array and MAC address should be valid. MAC address is in uppercase form
11 Verify visualizations are not linked with library
12 Verify format of title of visualizations
13 Verify format of title of dashboard
14 Verify Datastream Dashboard
15 Verify filters in visualizations
16 Verify visualizations in different browser
17 Verify README file

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.

How to test this PR locally

  • Clone integrations repo.
  • Install elastic package locally.
  • Start elastic stack using elastic-package.
  • Move to integrations/packages/jamf_compliance_reporter directory.
  • Run the following command to run tests.

elastic-package test

Related issues

Screenshots

image
image
image
image

@vinit-chauhan vinit-chauhan requested a review from a team as a code owner November 7, 2022 13:28
@vinit-chauhan vinit-chauhan changed the title Added Filter instead of KQL in visualizations, Add an on_failure proc… [Enhancement] [Jamf Compliance Reporter] Make enhancement in connector with best practices implementation Nov 7, 2022
@elasticmachine
Copy link

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

@elasticmachine
Copy link

elasticmachine commented Nov 7, 2022

🚀 Benchmarks report

Package jamf_compliance_reporter 👍(0) 💚(0) 💔(1)

Expand to view
Data stream Previous EPS New EPS Diff (%) Result
log 1123.6 814.33 -309.27 (-27.52%) 💔

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

elasticmachine commented Nov 7, 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-11-11T08:17:23.559+0000

  • Duration: 17 min 37 sec

Test stats 🧪

Test Results
Failed 0
Passed 11
Skipped 0
Total 11

🤖 GitHub comments

Expand to view the GitHub comments

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

  • /test : Re-trigger the build.

@elasticmachine
Copy link

elasticmachine commented Nov 7, 2022

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (1/1) 💚
Files 100.0% (47/47) 💚 2.53
Classes 100.0% (47/47) 💚 2.53
Methods 100.0% (156/156) 💚 8.671
Lines 99.321% (3072/3093) 👍 7.625
Conditionals 100.0% (0/0) 💚

@@ -1,30 +1,35 @@
# newer versions go on top
- version: "0.3.0"
- version: '0.3.1'
Copy link
Member

Choose a reason for hiding this comment

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

0.4.0

changes:
- description: Update package to ECS 8.5.0.
type: enhancement
link: https://github.com/elastic/integrations/pull/4285
- version: "0.2.1"
- version: '0.2.1'
Copy link
Member

Choose a reason for hiding this comment

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

Double instead of single quotes

ignore_failure: true
- convert:
field: json.header.event_modifier
target_field: jamf_compliance_reporter.log.header.event_modifier
type: string
ignore_missing: true
ignore_failure: true
Copy link
Member

Choose a reason for hiding this comment

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

While not directly related to this PR, do you mind also removing the ignore_failure?

@@ -1,7 +1,7 @@
format_version: 1.0.0
name: jamf_compliance_reporter
title: Jamf Compliance Reporter
version: "0.3.0"
version: 0.3.1
Copy link
Member

Choose a reason for hiding this comment

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

0.4.0

@P1llus P1llus merged commit 8f04189 into elastic:main Nov 18, 2022
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.

None yet

3 participants