packages/salesforce: Revamp Salesforce integration - #9629
Conversation
- remove login_stream and logout_stream - update config for login, logout, apex and setupaudittrail data-stream - update configurations
…nto 1278_revamp_salesforce_integration
- Update handlebar files for all the datastreams. - Update pipelines for all the datastreams - Update field mappings - update dashboards
…ps://github.com/kush-elastic/integrations into 1278_revamp_salesforce_integration
|
Updates:
|
|
@kush-elastic @aliabbas-elastic I have made a lot of changes to login data stream. Do have a look: 8c805a8 Changes include:
|
Co-authored-by: subham sarkar <sarkar.subhams2@gmail.com>
Co-authored-by: subham sarkar <sarkar.subhams2@gmail.com>
|
We found this during testing that some of the values (especially for There was one more field with this value |
Co-authored-by: Aliabbas Attarwala <124054599+aliabbas-elastic@users.noreply.github.com>
| unit: ms | ||
| type: long | ||
| description: The time in nanoseconds for the database round trip during login, including time spent in the JDBC driver, network, and database CPU time. | ||
| unit: nanos |
To be honest, this seems like the way to go. I personally don't have an example to compare with to weigh the pros and cons here. But for beta (0.x) stuff, it's understandable that there could be breaking changes. I think that's why it seems like a fair decision. Anyway, we're just merging this pull request. Kush isn't going to push the CHANGELOG changes. We will do it after dashboard PR is also merged; it is nearing completion. So, we still have some time. If we find a better alternative, we'll go with that instead. @kush-elastic Removing changelog right as we discussed? |
Yes @muthu-mps, |
Co-authored-by: subham sarkar <sarkar.subhams2@gmail.com>
💚 Build Succeeded
History
|
|
|
Package salesforce - 0.15.0 containing this change is available at https://epr.elastic.co/search?package=salesforce |
…a streams (#19717) * [salesforce] Re-expose Request Timeout (resource.timeout) for all data streams The Request Timeout setting was dropped in the v0.15.0 revamp (#9629) when the integration moved from the httpjson input to the dedicated salesforce Filebeat input. Since then there was no way to override the input's default 30s HTTP client timeout, so large EventLogFile downloads (notably Apex logs) could fail with "context deadline exceeded" with no available remedy. Re-expose it as a `resource_timeout` variable (default 30s, in Advanced options) across all four data streams (apex, login, logout, setupaudittrail), wiring it to `resource.timeout` in each stream template. Update the troubleshooting docs to reflect the current error signature and bump the package version to 1.8.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * [salesforce] Point changelog link to the PR Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>





Description
This PR introduces a new input method for our Salesforce integration and related changes, designed to overcome the limitations of HTTPJSON input in handling large data volumes from Salesforce Event Log Files (ELF) and real-time event monitoring. The new approach utilizes SOQL queries to directly collect data from Salesforce, offering improved performance, reliability, and scalability. This change addresses several issues with the current implementation and enables more efficient processing of Salesforce data, enhancing our overall integration capabilities.
Checklist
changelog.ymlfile.Related issues
Screenshots
Configurations
Before

After
