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
{{ message }}
Repository navigation
4.0 Monitor - review and remove unused REST endpoints before release #6319
My guess is that the underlying REST endpoints were removed, but the dropdown menu was not removed in the UI (an oversight).
The Monitor used to retain a single monolithic Java object and the UI pages showed portions of that object. The XML/JSON summary endpoints just serialized that single object and returned it to the user.
The data that drives the UI now can be retrieved by a user if they hit the underlying REST endpoint themselves. I'm thinking we can remove these menu items from the UI. @ctubbsii@DomGarguilo - thoughts?
The XML/JSON object at that endpoint was semi-stable, and provided to users to grab useful system state without the need to scrape html on various monitor pages. It predates the move to AJAX, and had been intended to be more stable than the REST endpoints we added to power the various page views. It is probably better to encourage users to configure a proper metrics sink and collect data that way instead, so it's probably okay that it is removed. However, I am bracing for complaints from users, and I suspect some may resort to scraping the page views or using the REST endpoints behind the views directly, even though they aren't expected to be stable.
in pr 6317, the "ec" endpoint was removed. That endpoint is still available in WebViews.java. There is also a similar endpoint "compactions" which the page seems broken. Both "ec" and "compaction" lead to an Active Compactions table. Right now it seems the "compactions" endpoint may not be used
/** * Returns the active compactions template. * * @return Active compactions model */@GET@Path("ec")
@Template(name = "/default.ftl")
publicMap<String,Object> getActiveCompactions() {
Map<String,Object> model = getModel();
model.put("title", "Active Compactions");
model.put("template", "ec.ftl");
model.put("js", "ec.js");
returnmodel;
}
in pr 6317, the "ec" endpoint was removed. That endpoint is still available in WebViews.java. There is also a similar endpoint "compactions" which the page seems broken. Both "ec" and "compaction" lead to an Active Compactions table. Right now it seems the "compactions" endpoint may not be used
I think the /compactions can be removed. /ec is used however. the screenshot you have on the active compactions page is correct it just means no compactions are running
Activity
Remove unused api endpoints, methods, data structures (#6404)
Amemeda commentedon Aug 13, 2026
The endpoints (rest/xml and rest/json) in this REST dropdown in monitor both lead to 404 error, were these not fully removed?
dlmarion commentedon Aug 13, 2026
My guess is that the underlying REST endpoints were removed, but the dropdown menu was not removed in the UI (an oversight).
The Monitor used to retain a single monolithic Java object and the UI pages showed portions of that object. The XML/JSON summary endpoints just serialized that single object and returned it to the user.
The data that drives the UI now can be retrieved by a user if they hit the underlying REST endpoint themselves. I'm thinking we can remove these menu items from the UI. @ctubbsii @DomGarguilo - thoughts?
Amemeda commentedon Aug 13, 2026
If that is the case I can remove it
ctubbsii commentedon Aug 13, 2026
The XML/JSON object at that endpoint was semi-stable, and provided to users to grab useful system state without the need to scrape html on various monitor pages. It predates the move to AJAX, and had been intended to be more stable than the REST endpoints we added to power the various page views. It is probably better to encourage users to configure a proper metrics sink and collect data that way instead, so it's probably okay that it is removed. However, I am bracing for complaints from users, and I suspect some may resort to scraping the page views or using the REST endpoints behind the views directly, even though they aren't expected to be stable.
Amemeda commentedon Aug 19, 2026
in pr 6317, the "ec" endpoint was removed. That endpoint is still available in WebViews.java. There is also a similar endpoint "compactions" which the page seems broken. Both "ec" and "compaction" lead to an Active Compactions table. Right now it seems the "compactions" endpoint may not be used
DomGarguilo commentedon Aug 19, 2026
I think the
/compactionscan be removed./ecis used however. the screenshot you have on the active compactions page is correct it just means no compactions are running