Now using Promise.allSettled we can handle each error independently, should we handle the rejected state of the createPipelineIfNotExists functions? Are the subsequent functions affected by the creation of the pipeline somehow?
Also, should we start collecting Telemetry data on these errors to know more about what circumstances makes them happen and how we can improve error handling in the future?
Hey @opauloh, regarding having telemetry data on those errors: all our logs are automatically sent to centralize env, here you can find a dashboard the contains our logs.
Regarding the error handling, I agree, if one index failed it shouldn't impact the rest indices.
Hey @opauloh, regarding having telemetry data on those errors: all our logs are automatically sent to centralize env, here you can find a dashboard the contains our logs.
After the recent changes the cloud_security_posture transform plugin, the
initializeCspIndices
function looks like this:Now using
Promise.allSettled
we can handle each error independently, should we handle the rejected state of thecreatePipelineIfNotExists
functions? Are the subsequent functions affected by the creation of the pipeline somehow?Also, should we start collecting Telemetry data on these errors to know more about what circumstances makes them happen and how we can improve error handling in the future?