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
Last update of basescript code we implemented unique_id construction in this format "20171214T203104_b4141665-e10d-11e7-8fe1-901b0ecdc716"
In our crawler components for clusterevent logs we are creating unique_id by taking event_id in this format "20171214T203104_b4141667e10d67e78fe1901b0ecdc716"
Finally the unique_id for logs in two different formats difference is -.
We discussed with @prashanthellina about this issue so we are decided to convert at basescript code remove - in between id using uuid.uuid1().hex to maintain one structure.
@Basha-Shaik
unique_idconstruction in this format"20171214T203104_b4141665-e10d-11e7-8fe1-901b0ecdc716"crawlercomponents forclustereventlogs we are creatingunique_idby takingevent_idin this format"20171214T203104_b4141667e10d67e78fe1901b0ecdc716"unique_idfor logs in two different formats difference is-.basescriptcode remove-in between id usinguuid.uuid1().hexto maintain one structure.