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
Add support for the ui block to be defined in job.group and job.group.task. Additionally, add support for alloc-specific ui links. Both could be achievable via some sort of url templating schema:
For more complex jobs, it may be useful to link out to external services - logs and metrics being the key ones - at a group or task level. This would allow for aggregated data that is specific to those levels - which is important in jobs that have multiple groups, or cases where there are multiple tasks within a group (such as for sidecars).
Additionally, having links out for just allocations would allow folks to filter to the exact allocation that is being looked at. This is super useful when trying to figure out why one or more allocations are misbehaving.
Attempted Solutions
At the moment, I need to copy the allocation ID and then paste it into a form elsewhere. This works for me but developers may be less clear as to where to browse on external services to filter data. Worse still, it makes it more difficult to migrate across external services (as in, if I move from Grafana => DataDog or back for logs/metrics) as now I need to communicate that change to developers and teach them the new way to do things. Having those links be embeddable in the Nomad UI will make it easier for folks to use those links.
The text was updated successfully, but these errors were encountered:
Hi @josegonzalez , thanks for this feature request. I think it's a good one; my only pause is around the allocation_link field and I'd like to understand it better.
Is the idea that with allocation_link set to true, the link would show up at /ui/allocations/$allocID (potentially several of them, if each of an allocation's tasks had a ui link)? Or on /ui/allocations/$allocID/$taskName with some tag or icon indicating it's allocation-specific?
Proposal
Add support for the
ui
block to be defined injob.group
andjob.group.task
. Additionally, add support for alloc-specific ui links. Both could be achievable via some sort of url templating schema:Use-cases
For more complex jobs, it may be useful to link out to external services - logs and metrics being the key ones - at a group or task level. This would allow for aggregated data that is specific to those levels - which is important in jobs that have multiple groups, or cases where there are multiple tasks within a group (such as for sidecars).
Additionally, having links out for just allocations would allow folks to filter to the exact allocation that is being looked at. This is super useful when trying to figure out why one or more allocations are misbehaving.
Attempted Solutions
At the moment, I need to copy the allocation ID and then paste it into a form elsewhere. This works for me but developers may be less clear as to where to browse on external services to filter data. Worse still, it makes it more difficult to migrate across external services (as in, if I move from Grafana => DataDog or back for logs/metrics) as now I need to communicate that change to developers and teach them the new way to do things. Having those links be embeddable in the Nomad UI will make it easier for folks to use those links.
The text was updated successfully, but these errors were encountered: