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

Create package for Salesforce integration #3940

Closed
8 tasks
akshay-saraswat opened this issue Aug 2, 2022 · 1 comment · Fixed by #4261, #4323, #4356 or #4410
Closed
8 tasks

Create package for Salesforce integration #3940

akshay-saraswat opened this issue Aug 2, 2022 · 1 comment · Fixed by #4261, #4323, #4356 or #4410

Comments

@akshay-saraswat
Copy link
Contributor

We must migrate Salesforce filebeat module to agent-based integration so that we boost agent/fleet adoption and are ready for any decision related to beats future.

cc: @pmeresanu85 @rameshelastic

All changes

  • Change follows the contributing guidelines
  • Supported versions of the monitoring target are documented
  • Supported operating systems are documented (if applicable)
  • Integration or System tests exist
  • Documentation exists
  • Fields follow ECS and naming conventions
  • At least a manual test with ES / Kibana / Agent has been performed.
  • Required Kibana version set to:
@yug-rajani
Copy link
Contributor

List of backlog items as suggested by @agithomas and discussed with the team:

  • System tests with actual Salesforce instance containerized (Currently, the system tests use the observability/stream image due to the limitations mentioned here)

CC: @milanparmar-crest @lalit-satapathy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment