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
Currently, service name colors are all static, random based on the name, which can lead to the colors of different services looking too similar.
This could be done through simple CSS in the client, or something else defined at the account level, but ideally it would be a part of the otel resource attributes, however I haven't looked into the standard enough to know if you're safe putting arbitrary data there.
The text was updated successfully, but these errors were encountered:
Ye, I've seen the same thing, I agree it's annoying.
It's fine to put arbitrary data in resource attributes, but we would need to extract them and presumably put that data in a new table - currently we don't have a store of resource level attributes, just records.
We can discuss internally how to make this happen.
Description
Currently, service name colors are all static, random based on the name, which can lead to the colors of different services looking too similar.
This could be done through simple CSS in the client, or something else defined at the account level, but ideally it would be a part of the otel resource attributes, however I haven't looked into the standard enough to know if you're safe putting arbitrary data there.
The text was updated successfully, but these errors were encountered: