You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the Salesforce filebeat module is run, the data collected is duplicate because of the issue with the cursor set. The cursor should ideally be storing the created date for the last ingested event. However, after the update of the mechanism of chained calls as a part of this PR from the Elastic Team, the cursor value is not being set which leads to duplication of data being ingested because of the “WHERE” condition in the SOQL Query not running with the expected cursor value.
Build filebeat inside x-pack/filebeat using mage build
Enable salesforce filebeat module
Configure the module and filebeat.yml to add the required credentials
Run filebeat
The data ingested is duplicate at every interval. For example, if an interval of 5 mins is set, the same set of events would be ingested every 5 mins.
Root Cause: The value of the cursor last_published_login is not being set. This seems to be a limitation in the implementation/enhancement of the chained calls mechanism in httpjson.
When the Salesforce filebeat module is run, the data collected is duplicate because of the issue with the cursor set. The cursor should ideally be storing the created date for the last ingested event. However, after the update of the mechanism of chained calls as a part of this PR from the Elastic Team, the cursor value is not being set which leads to duplication of data being ingested because of the “WHERE” condition in the SOQL Query not running with the expected cursor value.
x-pack/filebeat
usingmage build
salesforce
filebeat modulefilebeat.yml
to add the required credentialslast_published_login
is not being set. This seems to be a limitation in the implementation/enhancement of the chained calls mechanism in httpjson.The text was updated successfully, but these errors were encountered: