[Index Management] Add Overview tab#164628
Conversation
| codeSnippetArguments | ||
| )} | ||
| showTryInConsole={getConsoleRequest('ingestData')} | ||
| consoleRequest={getConsoleRequest('ingestData')} |
There was a problem hiding this comment.
I think this maybe was an oversight of #164766?
There was a problem hiding this comment.
yes this is fixed in main
TattdCodeMonkey
left a comment
There was a problem hiding this comment.
search-api-panel changes LGTM
|
|
||
| const INDEX_NAME_PLACEHOLDER = 'index_name'; | ||
|
|
||
| export const curlDefinition: LanguageDefinition = { |
There was a problem hiding this comment.
@TattdCodeMonkey is there someone you usually work with to verify the code snippets for each language? I copied this from existing definitions, but would be good to get a pair of 👀 on it to confirm.
There was a problem hiding this comment.
Yes we usually ping the language clients team and see if they can give them a review.
There was a problem hiding this comment.
@TattdCodeMonkey have you considered having a shared place for some of these common client svgs?
There was a problem hiding this comment.
We haven't yet but it would be a good topic for improvement. I know Efe included them in enterprise_search and imported them (see here & here) vs populating the url path. Which might be an option to include them in the search-api-panels package that way but I'm not 100% sure what if that would work in a package.
There was a problem hiding this comment.
Yeah, I was wondering if it might makes sense in the search-api-panels package. I also found there's a kbn-shared-svg package, although it doesn't appear to be used much yet.
There was a problem hiding this comment.
I will as-is for now; but I think it's worth revisiting.
|
Pinging @elastic/platform-deployment-management (Team:Deployment Management) |
|
@elasticmachine merge upstream |
JoshMock
left a comment
There was a problem hiding this comment.
Code snippets for Python and JavaScript look right to me. 👍 Ruby and PHP also seem right, but @ezimuel and @picandocodigo would be best for those. And @Anaethelion for Go.
yuliacech
left a comment
There was a problem hiding this comment.
Great job, @alisonelizabeth!
Code changes LGTM! Index details definitely look better on stateful than serverless when there is hardly any info to display, but we could work on it in a follow up.
|
@elasticmachine merge upstream |
There was a problem hiding this comment.
This is exciting to see this evolve!
When selecting an index and using the bulk action menu (with only a single index selected), the options don't navigate anywhere now. (Perhaps still trying to trigger the flyout?)
I expected these options to take me to the appropriate tab on the detail page.
Perhaps not due to this PR. So if not, I am happy to approve this one and file this elsewhere.
Screenshot--2023-09-07--Index.Management.-.Elastic.mp4
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@sphilipse do you mind reviewing b3a31e3? CI was failing on my PR due to this TS error; I believe it was introduced via #165880. |
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
|
I'm going to go ahead and merge this. If there are any additional changes needed to the clients code, I will open up a follow-up PR (re: #164628 (review)). |
This PR builds out the "Overview" tab on the new index details page.
Note: We will likely iterate on this design in the future.
Fixes #164570
How to test
On serverless:
On stateful:
Screenshots
// Serverless view (index stats info not available)

// Self-managed (with index stats panel)
