[Management] Update management landing page copy#166732
[Management] Update management landing page copy#166732alisonelizabeth merged 9 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/platform-deployment-management (Team:Deployment Management) |
|
IMO the description for the "Connectors" is still possibly confusing for folks who are seeking the search-related connectors. What about something like "Configure connections to third party systems for use in cases and rules." |
I'm happy to update the copy to this. @gchaps wdyt? |
|
+1 to
|
gchaps
left a comment
There was a problem hiding this comment.
In looking over this, I felt that the intro was a too short and the descriptions read better when they are 2 lines. Here are my suggestions. I am interested in what others think.
Intro
Manage data and indices, oversee rules and connectors, organize saved objects and files, and create API keys in a central location.
Cards
Configure and maintain your Elasticsearch indices for data storage and retrieval.
Pivot your data or copy the latest documents into an entity-centric index.
Remove fields, extract values, and perform transformations on your data.
Identify, analyze, and process your data using advanced data analysis.
Manage and view the Logstash event processing pipeline from inputs to outputs.
Detect conditions in apps across Kibana and trigger actions.
Configure connections to third party systems for use in cases and rules.
Manage your saved dashboards, maps, data views, and Canvas workloads.
Monitor the generation of PDF, PNG and CSV reports.
Organize, search, and filter your saved objects by specific criteria.
|
++ But since the ML is not part of this section anymore (as it is in stateful).. I'd remove the word "insights" and keep it just "Alerts" - wdyt? |
|
+1 to removing "Insights" from the category name. |
|
@gchaps thanks for the review! I believe I addressed all the feedback. Mind taking another look?
|
gchaps
left a comment
There was a problem hiding this comment.
Canvas workloads > Canvas workpads. Sorry about that.
Otherwise, text LGTM.
@lcawl, @sixstringcode What do you think of the new intro and shorter text in the cards?
|
IMO we should try to remove the "Kibana" reference from the Rules intro. How about something like "Define when to generate alerts and notifications". Likewise I don't think the "Reporting" app enables you to do any monitoring. How about: "Manage generated PDF, PNG and CSV reports". |
I think we should keep it, I'll be adding a few things for Security. Entity Risk only make sense if it still says insights |
+1 I have been actively removing references to Kibana as well. It doesn't have any context in the new serverless IA's. |
|
@gchaps the new shorter ones look much better. It's VERY minor, but I could see modifying Data Views a little: "Create and manage data you explore from Elasticsearch" or something like that. Object feels like a technical detail we don't need. We should also capture the ones we haven't added yet here. Advanced Settings we have already discussed, but it looks like we will add Maps, Entity Risk and Visualize Library for Security Projects. We'll need copy for those also. #167453 |
|
@sixstringcode How about one of these:
|
|
I've addressed the latest feedback in 271ca6e. @sixstringcode please advise on the final copy for Data Views.
I'm 100% on finalizing copy for these new cards, however, I think the actual code change is out of scope for this PR. |
|
@szabosteve gave me a minor edit to the ML card description so that the word "data" is not repeated:
|
Fair, I'll take care of them on #167453 |
I know it's being picky, but the data comes from Elasticsearch. It's really is a filter of the same data. Retrieved makes it sound like it's been moved or copied. Maybe selected or defined? |
|
Final copy feedback applied via 9c01f33 |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |

Fixes #163997
Note: The "Endpoints" card copy mentioned in the issue will be added in a separate PR. Also, I'm getting clarification on the "Logs" card for Observability; if we need to add it, it can be done via a separate PR.