x-pack/filebeat/input/salesforce: Implement a new Salesforce input

[kush-elastic]

Description

Introducing a new filebeat input -- Salesforce. The existing input used for the Salesforce module was not a good choice and it didn't give us the flexibility to address some issues we were facing with HTTPJSON.

New Salesforce input is introduced to have greater control over authentication, how data is fetched and processed, and more. There are several clients available for Salesforce written in Go that execute SOQL queries against the Salesforce server and do the other needful steps (e.g., fetching EventLogFile) which were previously done in HTTPJSON. Please note that this will be completely independent of HTTPJSON input and hence there would be no relation.

Please read the technical doc to read more about the decisions taken here.

Checklist

• [x] My code follows the style guidelines of this project
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] I have made corresponding change to the default configuration files
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to Run this Input

Configuration

Following is the sample configuration for salesforce input:

- type: salesforce
  enabled: true
  version: 56
  auth.oauth2:
    user_password_flow:
      enabled: true
      client.id: client-id
      client.secret: client-secret
      token_url: https://instance-id.develop.my.salesforce.com
      user: [email protected]
      password: salesforce-instance-password
    jwt_bearer_flow:
      enabled: true
      client.id: client-id
      client.username: [email protected]
      client.key_path: server_client.key
      url: https://login.salesforce.com
  url: https://instance-id.develop.my.salesforce.com
  event_monitoring_method:
    event_log_file:
      enabled: true
      interval: 1h
      query:
        default: "SELECT Id,CreatedDate,LogDate,LogFile FROM EventLogFile WHERE EventType = 'Login' ORDER BY CreatedDate ASC NULLS FIRST"
        value: "SELECT Id,CreatedDate,LogDate,LogFile FROM EventLogFile WHERE EventType = 'Login' AND CreatedDate > [[ .cursor.event_log_file.last_event_time ]] ORDER BY CreatedDate ASC NULLS FIRST"
      cursor:
        field: "CreatedDate"
    object:
      enabled: true
      interval: 5m
      query:
        default: "SELECT FIELDS(STANDARD) FROM LoginEvent"
        value: "SELECT FIELDS(STANDARD) FROM LoginEvent WHERE EventDate > [[ .cursor.object.first_event_time ]]"
      cursor:
        field: "EventDate"

• Type: Identifies the input type as salesforce.

• Enabled: Indicates whether the Salesforce input is active. Example: true

• Version: Specifies the version of the Salesforce API to be used for the input. Example: 56

• Auth/OAuth2 Configuration:

  • User Password Flow:

    • Enabled: Enables OAuth2 User Password Flow for authentication. Example: true
    • client.id: The OAuth2 client ID used for authentication. Example: 3MMG9pAzvMkjMb6nzW6iSPJU2rxCryzVeeo7KAuRlI1uqDsJhxow76lQ5Eks2KSfr1o8D1PoMoGQCPPILldkB
    • client.secret: The OAuth2 client secret used for authentication. Example: C497A710C21497FB0A0A68B8DAF78ALFBE010C65BFBE076E85B9B37553D6CBCA
    • token_url: The Base URL for obtaining OAuth2 tokens. Example: https://devabcdin-org-ed.develop.my.salesforce.com
    • username: The Salesforce instance username or user ID for authentication. Example: [email protected]
    • password: The Salesforce user's password for authentication. Example: salesforce-instance-password

  • JWT Bearer Flow:

    • Enabled: Enables OAuth2 JWT Bearer Flow for authentication. Example: true
    • client.id: The OAuth2 client ID used for authentication. Example: 3MMG9pAzvMkjMb6nzW6iSPJU2rxCryzVeeo7KAuRlI1uqDsJhxow76lQ5Eks2KSfr1o8D1PoMoGQCPPILldkB
    • client.username: The Salesforce username used for authentication. Example: [email protected]
    • client.key_path: The path to the private key file used for JWT authentication. Example: server_client.key
    • url: The Salesforce authentication endpoint URL. Example: https://login.salesforce.com

• URL: Specifies the base URL of the Salesforce instance. Example: https://devabcdin-org-ed.develop.my.salesforce.com

• Event Monitoring Method:

  • Event Log File:

    • Enabled: Enables monitoring of Salesforce Event Log Files. Example: true
    • Interval: Checks for new events at regular intervals. Example: 1h
    • Query:
      • default: Default SOQL query to retrieve Event Log Files. Example: "SELECT Id,CreatedDate,LogDate,LogFile FROM EventLogFile WHERE EventType = 'Login' ORDER BY CreatedDate ASC NULLS FIRST"
      • value: Dynamic SOQL query with a cursor condition based on the last event timestamp. Example: "SELECT Id,CreatedDate,LogDate,LogFile FROM EventLogFile WHERE EventType = 'Login' AND CreatedDate > [[ .cursor.event_log_file.last_event_time ]] ORDER BY CreatedDate ASC NULLS FIRST"
    • Cursor:
      • field: Specifies the field used as a cursor for tracking changes. Example: "CreatedDate"

  • Object:

    • Enabled: Enables monitoring of Salesforce objects. Example: true
    • Interval: Checks for new events at regular intervals. Example: 5m
    • Query:
      • default: Default SOQL query to retrieve Salesforce objects. Example: "SELECT FIELDS(STANDARD) FROM LoginEvent"
      • value: Dynamic SOQL query with a cursor condition based on the first event timestamp. Example: "SELECT FIELDS(STANDARD) FROM LoginEvent WHERE EventDate > [[ .cursor.object.first_event_time ]]"
    • Cursor:
      • field: Specifies the field used as a cursor for tracking changes. Example: "EventDate"

Related issues

• Relates https://github.com/elastic/obs-infraobs-team/issues/1248
• Relates https://github.com/elastic/obs-infraobs-team/issues/1274

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b new_salesforce_input upstream/new_salesforce_input
git merge upstream/main
git push upstream new_salesforce_input

[mergify[bot]]

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @kush-elastic? 🙏. For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 135 min 39 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-11T11:23:12.934+0000

• Duration: 50 min 21 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	27542
Skipped	1922
Total	29464

Steps errors

Expand to view the steps failures

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'org.jenkinsci.plugins.workflow.steps.FlowInterruptedException'

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 183 min 30 sec

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 7 min 30 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 35 min 0 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-11T21:11:51.084+0000

• Duration: 180 min 58 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	28720
Skipped	2015
Total	30735

:green_heart: Flaky test report

Tests succeeded.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-12T08:59:39.545+0000

• Duration: 180 min 59 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	28720
Skipped	2015
Total	30735

:green_heart: Flaky test report

Tests succeeded.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-18T06:21:47.213+0000

• Duration: 70 min 39 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	25498
Skipped	1839
Total	27337

Steps errors

Expand to view the steps failures

Show only the first 10 steps failures

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 3 min 31 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 0 min 19 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 0 min 18 sec . View more details here
• Description: mage build unitTest

x-pack/libbeat-unitTest - mage build unitTest

• Took 4 min 23 sec . View more details here
• Description: mage build unitTest

x-pack/libbeat-unitTest - mage build unitTest

• Took 1 min 43 sec . View more details here
• Description: mage build unitTest

x-pack/libbeat-unitTest - mage build unitTest

• Took 1 min 43 sec . View more details here
• Description: mage build unitTest

x-pack/libbeat-goIntegTest - mage goIntegTest

• Took 5 min 23 sec . View more details here
• Description: mage goIntegTest

x-pack/libbeat-goIntegTest - mage goIntegTest

• Took 1 min 29 sec . View more details here
• Description: mage goIntegTest

x-pack/libbeat-goIntegTest - mage goIntegTest

• Took 1 min 23 sec . View more details here
• Description: mage goIntegTest

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'hudson.AbortException: script returned exit code 1'

:green_heart: Flaky test report

Tests succeeded.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-18T08:03:33.823+0000

• Duration: 75 min 43 sec

Test stats :test_tube:

Test	Results
Failed	1
Passed	31043
Skipped	1882
Total	32926

Test errors

Expand to view the tests failures

Build&Test / metricbeat-pythonIntegTest / test_connection – metricbeat.module.zookeeper.test_zookeeper.ZooKeeperMntrTest_1

Expand to view the error details

 AssertionError: 2 != 1 

Expand to view the stacktrace

 self = <test_zookeeper.ZooKeeperMntrTest_1 testMethod=test_connection>

    @unittest.skipUnless(metricbeat.INTEGRATION_TESTS, "integration test")
    @pytest.mark.tag('integration')
    def test_connection(self):
        """
        ZooKeeper server module outputs an event.
        """
        self.render_config_template(modules=[{
            "name": "zookeeper",
            "metricsets": ["connection"],
            "hosts": self.get_hosts(),
            "period": "5s"
        }])
        proc = self.start_beat()
        self.wait_until(lambda: self.output_lines() > 0)
        proc.check_kill_and_wait()
        self.assert_no_logged_warnings()
    
        output = self.read_output_json()
>       self.assertEqual(len(output), 1)
E       AssertionError: 2 != 1

module/zookeeper/test_zookeeper.py:102: AssertionError 

Steps errors

Expand to view the steps failures

Show only the first 10 steps failures

x-pack/filebeat-goIntegTest - mage goIntegTest

• Took 6 min 17 sec . View more details here
• Description: mage goIntegTest

x-pack/filebeat-goIntegTest - mage goIntegTest

• Took 3 min 53 sec . View more details here
• Description: mage goIntegTest

x-pack/filebeat-goIntegTest - mage goIntegTest

• Took 3 min 53 sec . View more details here
• Description: mage goIntegTest

x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest

• Took 7 min 7 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest

• Took 3 min 35 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest

• Took 3 min 36 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 7 min 39 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 2 min 27 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 2 min 28 sec . View more details here
• Description: mage build unitTest

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'org.jenkinsci.plugins.workflow.steps.FlowInterruptedException'

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-18T09:11:31.564+0000

• Duration: 9 min 6 sec

Steps errors

Expand to view the steps failures

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'org.jenkinsci.plugins.workflow.steps.FlowInterruptedException'

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-18T09:16:00.558+0000

• Duration: 151 min 37 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	28732
Skipped	2015
Total	30747

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-18T11:41:56.424+0000

• Duration: 178 min 3 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	28756
Skipped	2015
Total	30771

:green_heart: Flaky test report

Tests succeeded.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify[bot]]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b new_salesforce_input upstream/new_salesforce_input
git merge upstream/main
git push upstream new_salesforce_input

[elasticmachine]

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-18T21:38:48.616+0000

• Duration: 146 min 11 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	28762
Skipped	2015
Total	30777

Steps errors

Expand to view the steps failures

metricbeat-pythonIntegTest - mage pythonIntegTest

• Took 33 min 35 sec . View more details here
• Description: mage pythonIntegTest

Building Beats » Beats Packaging » PR-37331

• Took 0 min 9 sec . View more details here
• Description: null

:green_heart: Flaky test report

Tests succeeded.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-21T06:00:19.063+0000

• Duration: 8 min 26 sec

Steps errors

Expand to view the steps failures

Shell Script

• Took 0 min 7 sec . View more details here
• Description: HOME=/var/lib/jenkins/workspace/Beats_beats_PR-37331 GO_VERSION=1.20.11 ./dev-tools/run_with_go_ver make test-mage

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 7 min 37 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 77 min 45 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:broken_heart: Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-21T07:29:57.590+0000

• Duration: 130 min 42 sec

Test stats :test_tube:

Test	Results
Failed	8
Passed	31602
Skipped	1882
Total	33492

Test errors

Expand to view the tests failures

Build&Test / x-pack/filebeat-goIntegTest / TestInput/event_monitoring_method_object_with_default_query_only – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestInput/event_monitoring_method_object_with_default_query_only
server.URL: http://127.0.0.1:42135
    input_test.go:142: 
        	Error Trace:	/var/lib/jenkins/workspace/PR-37331-30-cf936830-41da-4396-8cfb-acf029c9084e/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input_test.go:142
        	Error:      	Received unexpected error:
        	            	no auth provider enabled accessing config
        	Test:       	TestInput/event_monitoring_method_object_with_default_query_only
--- FAIL: TestInput/event_monitoring_method_object_with_default_query_only (0.00s)
 

Build&Test / x-pack/filebeat-unitTest / TestInput/event_monitoring_method_object_with_default_query_only – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestInput/event_monitoring_method_object_with_default_query_only
server.URL: http://127.0.0.1:35081
    input_test.go:142: 
        	Error Trace:	/var/lib/jenkins/workspace/PR-37331-30-e9f35b53-2628-4548-b738-5116fb62bdaf/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input_test.go:142
        	Error:      	Received unexpected error:
        	            	no auth provider enabled accessing config
        	Test:       	TestInput/event_monitoring_method_object_with_default_query_only
--- FAIL: TestInput/event_monitoring_method_object_with_default_query_only (0.00s)
 

Build&Test / x-pack/filebeat-windows-2022-windows-2022 / TestInput/event_monitoring_method_object_with_default_query_only – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestInput/event_monitoring_method_object_with_default_query_only
server.URL: http://127.0.0.1:2324
    input_test.go:142: 
        	Error Trace:	C:/Users/jenkins/workspace/PR-37331-30-50d4ada3-af24-49ba-8ea2-0cdafa950487/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input_test.go:142
        	Error:      	Received unexpected error:
        	            	no auth provider enabled accessing config
        	Test:       	TestInput/event_monitoring_method_object_with_default_query_only
--- FAIL: TestInput/event_monitoring_method_object_with_default_query_only (0.00s)
 

Build&Test / x-pack/filebeat-windows-2016-windows-2016 / TestInput/event_monitoring_method_object_with_default_query_only – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestInput/event_monitoring_method_object_with_default_query_only
server.URL: http://127.0.0.1:17694
    input_test.go:142: 
        	Error Trace:	C:/Users/jenkins/workspace/PR-37331-30-52716415-84a1-4c62-8ca8-42df47b9663f/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input_test.go:142
        	Error:      	Received unexpected error:
        	            	no auth provider enabled accessing config
        	Test:       	TestInput/event_monitoring_method_object_with_default_query_only
--- FAIL: TestInput/event_monitoring_method_object_with_default_query_only (0.00s)
 

Build&Test / x-pack/filebeat-goIntegTest / TestInput – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestInput
--- FAIL: TestInput (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xb93eec]

goroutine 56 [running]:
testing.tRunner.func1.2({0xc55100, 0x14082a0})
	/var/lib/jenkins/workspace/PR-37331-30-cf936830-41da-4396-8cfb-acf029c9084e/.gvm/versions/go1.20.11.linux.amd64/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
	/var/lib/jenkins/workspace/PR-37331-30-cf936830-41da-4396-8cfb-acf029c9084e/.gvm/versions/go1.20.11.linux.amd64/src/testing/testing.go:1529 +0x39f
panic({0xc55100, 0x14082a0})
	/var/lib/jenkins/workspace/PR-37331-30-cf936830-41da-4396-8cfb-acf029c9084e/.gvm/versions/go1.20.11.linux.amd64/src/runtime/panic.go:884 +0x213
github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce.getSFDCConfig(0xc0003a33e0)
	/var/lib/jenkins/workspace/PR-37331-30-cf936830-41da-4396-8cfb-acf029c9084e/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input.go:361 +0x6c
github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce.TestInput.func1(0xc0003a09c0)
	/var/lib/jenkins/workspace/PR-37331-30-cf936830-41da-4396-8cfb-acf029c9084e/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input_test.go:166 +0x3ff
testing.tRunner(0xc0003a09c0, 0xc000394820)
	/var/lib/jenkins/workspace/PR-37331-30-cf936830-41da-4396-8cfb-acf029c9084e/.gvm/versions/go1.20.11.linux.amd64/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
	/var/lib/jenkins/workspace/PR-37331-30-cf936830-41da-4396-8cfb-acf029c9084e/.gvm/versions/go1.20.11.linux.amd64/src/testing/testing.go:1629 +0x3ea
 

Build&Test / x-pack/filebeat-unitTest / TestInput – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestInput
--- FAIL: TestInput (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xb93eec]

goroutine 45 [running]:
testing.tRunner.func1.2({0xc55100, 0x14082a0})
	/var/lib/jenkins/workspace/PR-37331-30-e9f35b53-2628-4548-b738-5116fb62bdaf/.gvm/versions/go1.20.11.linux.amd64/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
	/var/lib/jenkins/workspace/PR-37331-30-e9f35b53-2628-4548-b738-5116fb62bdaf/.gvm/versions/go1.20.11.linux.amd64/src/testing/testing.go:1529 +0x39f
panic({0xc55100, 0x14082a0})
	/var/lib/jenkins/workspace/PR-37331-30-e9f35b53-2628-4548-b738-5116fb62bdaf/.gvm/versions/go1.20.11.linux.amd64/src/runtime/panic.go:884 +0x213
github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce.getSFDCConfig(0xc00035c120)
	/var/lib/jenkins/workspace/PR-37331-30-e9f35b53-2628-4548-b738-5116fb62bdaf/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input.go:361 +0x6c
github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce.TestInput.func1(0xc00034d6c0)
	/var/lib/jenkins/workspace/PR-37331-30-e9f35b53-2628-4548-b738-5116fb62bdaf/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input_test.go:166 +0x3ff
testing.tRunner(0xc00034d6c0, 0xc000354f40)
	/var/lib/jenkins/workspace/PR-37331-30-e9f35b53-2628-4548-b738-5116fb62bdaf/.gvm/versions/go1.20.11.linux.amd64/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
	/var/lib/jenkins/workspace/PR-37331-30-e9f35b53-2628-4548-b738-5116fb62bdaf/.gvm/versions/go1.20.11.linux.amd64/src/testing/testing.go:1629 +0x3ea
 

Build&Test / x-pack/filebeat-windows-2022-windows-2022 / TestInput – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestInput
--- FAIL: TestInput (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x8 pc=0x9872ac]

goroutine 45 [running]:
testing.tRunner.func1.2({0xa403c0, 0x11de2b0})
	C:/Users/jenkins/workspace/PR-37331-30-50d4ada3-af24-49ba-8ea2-0cdafa950487/.gvm/versions/go1.20.11.windows.amd64/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
	C:/Users/jenkins/workspace/PR-37331-30-50d4ada3-af24-49ba-8ea2-0cdafa950487/.gvm/versions/go1.20.11.windows.amd64/src/testing/testing.go:1529 +0x39f
panic({0xa403c0, 0x11de2b0})
	C:/Users/jenkins/workspace/PR-37331-30-50d4ada3-af24-49ba-8ea2-0cdafa950487/.gvm/versions/go1.20.11.windows.amd64/src/runtime/panic.go:884 +0x213
github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce.getSFDCConfig(0xc00032a360)
	C:/Users/jenkins/workspace/PR-37331-30-50d4ada3-af24-49ba-8ea2-0cdafa950487/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input.go:361 +0x6c
github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce.TestInput.func1(0xc000324680)
	C:/Users/jenkins/workspace/PR-37331-30-50d4ada3-af24-49ba-8ea2-0cdafa950487/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input_test.go:166 +0x3ff
testing.tRunner(0xc000324680, 0xc000320be0)
	C:/Users/jenkins/workspace/PR-37331-30-50d4ada3-af24-49ba-8ea2-0cdafa950487/.gvm/versions/go1.20.11.windows.amd64/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
	C:/Users/jenkins/workspace/PR-37331-30-50d4ada3-af24-49ba-8ea2-0cdafa950487/.gvm/versions/go1.20.11.windows.amd64/src/testing/testing.go:1629 +0x3ea
 

Build&Test / x-pack/filebeat-windows-2016-windows-2016 / TestInput – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestInput
--- FAIL: TestInput (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x8 pc=0x11c72ac]

goroutine 57 [running]:
testing.tRunner.func1.2({0x12803c0, 0x1a1e2b0})
	C:/Users/jenkins/workspace/PR-37331-30-52716415-84a1-4c62-8ca8-42df47b9663f/.gvm/versions/go1.20.11.windows.amd64/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
	C:/Users/jenkins/workspace/PR-37331-30-52716415-84a1-4c62-8ca8-42df47b9663f/.gvm/versions/go1.20.11.windows.amd64/src/testing/testing.go:1529 +0x39f
panic({0x12803c0, 0x1a1e2b0})
	C:/Users/jenkins/workspace/PR-37331-30-52716415-84a1-4c62-8ca8-42df47b9663f/.gvm/versions/go1.20.11.windows.amd64/src/runtime/panic.go:884 +0x213
github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce.getSFDCConfig(0xc00036a330)
	C:/Users/jenkins/workspace/PR-37331-30-52716415-84a1-4c62-8ca8-42df47b9663f/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input.go:361 +0x6c
github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce.TestInput.func1(0xc000355a00)
	C:/Users/jenkins/workspace/PR-37331-30-52716415-84a1-4c62-8ca8-42df47b9663f/src/github.com/elastic/beats/x-pack/filebeat/input/salesforce/input_test.go:166 +0x3ff
testing.tRunner(0xc000355a00, 0xc00035cbb0)
	C:/Users/jenkins/workspace/PR-37331-30-52716415-84a1-4c62-8ca8-42df47b9663f/.gvm/versions/go1.20.11.windows.amd64/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
	C:/Users/jenkins/workspace/PR-37331-30-52716415-84a1-4c62-8ca8-42df47b9663f/.gvm/versions/go1.20.11.windows.amd64/src/testing/testing.go:1629 +0x3ea
 

Steps errors

Expand to view the steps failures

Show only the first 10 steps failures

x-pack/filebeat-goIntegTest - mage goIntegTest

• Took 6 min 46 sec . View more details here
• Description: mage goIntegTest

x-pack/filebeat-goIntegTest - mage goIntegTest

• Took 3 min 44 sec . View more details here
• Description: mage goIntegTest

x-pack/filebeat-goIntegTest - mage goIntegTest

• Took 3 min 39 sec . View more details here
• Description: mage goIntegTest

x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest

• Took 7 min 52 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest

• Took 3 min 34 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2022-windows-2022 - mage build unitTest

• Took 3 min 38 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 8 min 31 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 3 min 42 sec . View more details here
• Description: mage build unitTest

x-pack/filebeat-windows-2016-windows-2016 - mage build unitTest

• Took 3 min 47 sec . View more details here
• Description: mage build unitTest

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'hudson.AbortException: script returned exit code 1'

:bug: Flaky test report

:grey_exclamation: There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

:broken_heart: There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Build&Test / x-pack/filebeat-goIntegTest / TestInput/event_monitoring_method_object_with_default_query_only – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce
• Name: Build&Test / x-pack/filebeat-unitTest / TestInput/event_monitoring_method_object_with_default_query_only – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce
• Name: Build&Test / x-pack/filebeat-windows-2022-windows-2022 / TestInput/event_monitoring_method_object_with_default_query_only – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce
• Name: Build&Test / x-pack/filebeat-windows-2016-windows-2016 / TestInput/event_monitoring_method_object_with_default_query_only – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce
• Name: Build&Test / x-pack/filebeat-goIntegTest / TestInput – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce
• Name: Build&Test / x-pack/filebeat-unitTest / TestInput – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce
• Name: Build&Test / x-pack/filebeat-windows-2022-windows-2022 / TestInput – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce
• Name: Build&Test / x-pack/filebeat-windows-2016-windows-2016 / TestInput – github.com/elastic/beats/v7/x-pack/filebeat/input/salesforce

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 8 min 50 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 42 min 23 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 9 min 21 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 30 min 29 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 178 min 32 sec

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 10 min 40 sec

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-21T16:42:00.775+0000

• Duration: 179 min 34 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	28810
Skipped	2015
Total	30825

:green_heart: Flaky test report

Tests succeeded.

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-25T20:21:45.321+0000

• Duration: 6 min 37 sec

Steps errors

Expand to view the steps failures

Error signal

• Took 0 min 0 sec . View more details here
• Description: tar: step failed with error null

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-12-25T20:22:45.350+0000

• Duration: 71 min 38 sec

Test stats :test_tube:

Test	Results
Failed	0
Passed	28376
Skipped	2015
Total	30391

Steps errors

Expand to view the steps failures

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'org.jenkinsci.plugins.workflow.steps.FlowInterruptedException'

:robot: GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)