Mention plugins in troubleshooting Elasticsearch integration
What does this MR do?
This comes after a recent issue was diagnosed for one of our customers where the plugin was causing the integration not to work. Hopefully calling out plugins in our docs may save some time as customers may be able to spot early on that the plugin is the thing causing issues before asking us to diagnose the problem. Since there are many plugins that are 3rd party to Elasticsearch and they can significantly change the behaviour of Elasticsearch it's impossible for us to test against all plugins and be sure what does and does not work.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team