Skip to content

[Monitoring] Update missed logstash pages to EUI#27258

Merged
chrisronline merged 5 commits intoelastic:masterfrom
chrisronline:monitoring/logstash_eui_missed_parts
Dec 19, 2018
Merged

[Monitoring] Update missed logstash pages to EUI#27258
chrisronline merged 5 commits intoelastic:masterfrom
chrisronline:monitoring/logstash_eui_missed_parts

Conversation

@chrisronline
Copy link
Contributor

This PR updates the logstash monitoring UI to update some missed work from #27064 in regards to the Logstash monitoring UI, specifically the pipeline and node UIs.

I'm not that familiar with these UIs so I'll probably need @justinkambic and/or @ycombinator to double check all of this.

@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@ycombinator
Copy link
Contributor

When I tried to load the Logstash Node Overview page, I got a blank page and an error in the browser's console log:

screen shot 2018-12-17 at 9 46 41 am

@pickypg
Copy link
Member

pickypg commented Dec 17, 2018

How did this pass CI if that error is happening?

But I suspect this PR depends on #27253 noting that many of the changes appear to be in there.

@chrisronline
Copy link
Contributor Author

@pickypg This PR was picked from that one but obviously missed a few things. Fixing up now

@ycombinator
Copy link
Contributor

ycombinator commented Dec 17, 2018

Not a result of this PR, but I noticed that the table on the Logstash Node Listing page is not sortable. Since you're fixing up things, mind fixing this too?

[UPDATE] If it helps, here's the original sorting logic:

const columns = [
{ title: 'Name', sortKey: 'logstash.name', sortOrder: SORT_ASCENDING },
{ title: 'CPU Usage', sortKey: 'process.cpu.percent' },
{ title: 'Load Average', sortKey: 'os.cpu.load_average.1m', },
{ title: 'JVM Heap Used', sortKey: 'jvm.mem.heap_used_percent' },
{ title: 'Events Ingested', sortKey: 'events.out' },
{ title: 'Config Reloads' },
{ title: 'Version', sortKey: 'logstash.version' }
];

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@chrisronline
Copy link
Contributor Author

@ycombinator Done!

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@ycombinator
Copy link
Contributor

Not sure if it's this PR or not, but the filtering on the Logstash Node Listing table does not seem to be working:

dec-18-2018 10-17-15

FWIW, filtering works on the Logstash Pipeline Listing table.

@chrisronline
Copy link
Contributor Author

@ycombinator Hmm. Interesting. I'm investigating now

@chrisronline
Copy link
Contributor Author

@ycombinator Definitely an issue. If it's okay with you, I'd like to address this in a later PR (which I'm working on now) as this affects all of the monitoring tables.

@ycombinator
Copy link
Contributor

Definitely an issue. If it's okay with you, I'd like to address this in a later PR (which I'm working on now)...

I'm good with this being addressed in a follow up PR.

... as this affects all of the monitoring tables.

FWIW, I did not notice this issue on the Logstash Pipeline Listing table, which is also EUI?

@chrisronline
Copy link
Contributor Author

@ycombinator I think it's hit or miss how each table might perform as the filtering/searching logic is somewhat complex and I'm not sure which situations will work and which won't. Therefore, for the follow up PR, I'm going to simplify it and write custom code to handle it in a predicable manner

@ycombinator
Copy link
Contributor

Sounds good @chrisronline. Once you've rebased this PR to resolve the conflict, I'll review it once more. Ping me here when it's ready for review.

@chrisronline
Copy link
Contributor Author

@ycombinator Done and ready for review

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

const pipelineId = $route.current.params.id;
const pipelineHash = $route.current.params.hash || '';
const url = `../api/monitoring/v1/clusters/${clusterUuid}/logstash/pipeline/${pipelineId}/${pipelineHash}`;
const url = pipelineHash
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ycombinator Bug fix here

@chrisronline
Copy link
Contributor Author

@ycombinator FYI, the other PR #27504

Copy link
Contributor

@ycombinator ycombinator left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested this PR functionally and it LGTM.

There are other issues that were found while testing this PR but they exist in master as well, therefore are not a result of this PR.

@chrisronline chrisronline merged commit 8283ea5 into elastic:master Dec 19, 2018
@chrisronline chrisronline deleted the monitoring/logstash_eui_missed_parts branch December 19, 2018 18:14
chrisronline added a commit to chrisronline/kibana that referenced this pull request Dec 19, 2018
* Update logstash to EUI pages

* Adding missed functionality

* Ensure columns are sortable and update the nodes view to use the right base controller methods
chrisronline added a commit that referenced this pull request Dec 21, 2018
* Update logstash to EUI pages

* Adding missed functionality

* Ensure columns are sortable and update the nodes view to use the right base controller methods
@chrisronline
Copy link
Contributor Author

chrisronline commented Dec 21, 2018

Backport:
6.x: 73e66e2
6.6: 2358d9f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants