Visual Service Grouping | Feature Requests

Render

Create

Roadmap

Feature Requests

Visual Service Grouping

in progress

Hamed Montazeri

Related services should be grouped together on the UI to make them easier to manage and visualize together.

June 4, 2020

Anurag Goel

Merged in a post:

Group services by app/scope

Oleg Komarov

The dashboard is getting crowded with a web app having other private and public dependecies. 
We also recreate the same setup for staging and playground. The only way we can now distinguish pertinent services is e.g. by prefixing the name with staging- or playground-
. 
It would be nice to be able to group services by app/scope/namespace.
Also that could be extended to have a consolidated log per app (akin to Heroku log by app with the info from all its dynos).

September 10, 2019

August 30, 2020

Anurag Goel

Merged in a post:

sort services by name instead of last modified

Braden Sidoti

its confusing when they keep moving around on the dashboard

July 30, 2020

August 30, 2020

Anurag Goel

marked this post as

in progress

Yashu Mittal

I was also trying to similar thing in Render, creating new service for each environment but it was quite difficult to manage since all services was under one roof.

Getting this visual pipeline deployment system will be a lot more helpful.

Anurag Goel

Merged in a post:

Group services

Yashu Mittal

Seeing all the services in one single list can be bit cluttered.

Instead, I would like to group all the services by "Service Type" or "Labels"

July 14, 2020

Yashu Mittal

Having an option to group services using label would help a lot.

Anurag Goel

marked this post as

planned

Anurag Goel

Merged in a post:

UI-Based Instance Grouping

Aaron Ng

I know there's render.yaml for coordinating everything at once– but something I'd find really nice is a dashboard where I can order each of the instances into groups (Production / Staging) and order those instances however I'd like inside those groups.

This way I can just start all of my staging services at once without clicking into all of them– I could just start the group. My staging instances also won't get mixed-up with my production instances because of the changing order based on recent deploy times.

January 26, 2020

Jaap Frolich

This would be awesome. For our use case we don't need a service in multiple groups. And if resources are shared a shared group would be good enough. Mostly to organize the dashboard.

Anurag Goel

Definitely on the list. We've considered both service groups and tags for this. Would you need a service to be in multiple groups at the same time?

Oleg Komarov

Anurag Goel: We would, e.g. our celery worker and celery brokers are shared by staging and production.

→