[Dataset Quality] Provide field limit mitigation option with rollover

[achyutjhunjhunwala]

📓 Summary

Add UI to be able to update the Field Limit. Things to consider

• Validations around how high the limit can be set, should the limit be proposed
• Proper messages around, how they can fix this otherwise like reducing the number of fields sent.
• Rollover the Datastream to see the affected changes.

Acceptance Criteria

• Section to take user input to increase Field Limit as per Wireframes
• The Degraded Fields table on the Main page should start referring to last backing index in the DS
• Show user a message to Rollover if they have done this. (P.S. - Its not possible to preserve this state, meaning if the user did update the size and did not do a rollover, comes later, we will not be able to show this message)

🎨 Design

Figma

[elasticmachine]

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

[achyutjhunjhunwala]

cc: @gbamparop @LucaWintergerst @flash1293

As discussed during the weekly sync, updating the discussions here

1. The option to apply a new limit will only be available to integrations. Non integration dataset will only have the text for field limit but not provide option to do it.
2. After careful consideration, i propose we suggest Current Limit + 30% to the user for New Field Limit to start with.
3. If the user selects a new limit and clicks on Apply the following will happen

• Update the custom component template associated with the index template of the integration. If Custom component does not exist, same will be created.
• Update the last backing index with the new setting as well.
  • If this part is successful, do nothing
  • if updating the last backing index fails, show the user an option to do Rollover. @patpscal Can you help me here with some mock up for triggering the Rollover. This would basically be a second action.
    @mdbirnstiehl I would need a copy as well for the text here. As this would be considered as partial success. That component template was successfully updated but not the last backing index. Hence a manual rollover is required

Text i used for which i need copy is

4. One of the Mitigations is the link to update the Pipeline for Integrations. This should ideally take them to a page where they can either edit or create a @custom pipeline. This solution currently does not exists and a feature request has been created.

An alternate solution to this would be to display the user the name of the custom pipeline they should create with a copy icon next to it.
There should be a link which would take the users to the current create Pipeline Page.

A text must be presented to them, that they can copy the pipeline name and create a custom pipeline to handle this situation.
@mdbirnstiehl @patpscal Can you both help me here with this point 4 in terms of design and copy.

[mdbirnstiehl]

@mdbirnstiehl I would need a copy as well for the text here. As this would be considered as partial success. That component template was successfully updated but not the last backing index. Hence a manual rollover is required

How about:

Changes not applied to new data

The component template was successfully updated with the new field limit, but the changes were not applied to the most recent backing index.
Perform a rollover to apply your changes to new data.

4. One of the Mitigations is the link to update the Pipeline for Integrations. This should ideally take them to a page where they can either edit or create a @custom pipeline. This solution currently does not exists and a feature request has been created.

An alternate solution to this would be to display the user the name of the custom pipeline they should create with a copy icon next to it. There should be a link which would take the users to the current create Pipeline Page.

Do we have a design for this one? Not sure exactly what it will look like and what text we will need here.