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
I think, the linked custom links in Chronograf should work irrespective of OAuth2 being enabled especially since Chronograf doesn't behave like a OAuth2 proxy.
Let me describe my use case. I have ELK, Jaeger-ui and Chronograf under different base paths. I would like to have all there services running under the same hostname but different paths.
Therefore, I have a central oauth2 proxy in my case https://github.com/bitly/oauth2_proxy that does authentication. Therefore, I don't necessarily need the OAuth2 authentication from Chronograf.
I would like to provide custom links in chronograf to kibana and jaeger. However, with the current implementation, it isn't possible.
Irrespective of when these above features are implemented, I strongly believe that custom links should not depend on whether OAuth2 in Chronograf is used or not because these custom links need to be secured, they will be secured.
The text was updated successfully, but these errors were encountered:
Puneeth-n
changed the title
Linked custom links should irrespective of OAuth2 settings
Linked custom links should be renendered irrespective of OAuth2 settings in Chronograf
Sep 18, 2018
Puneeth-n
changed the title
Linked custom links should be renendered irrespective of OAuth2 settings in Chronograf
Custom links should be rendered irrespective of OAuth2 settings in Chronograf
Sep 18, 2018
@Puneeth-n thanks for reporting. this feature was specifically focused around our cloud offering which always has auth enabled. We will look to update where the links are stored in a future ui redesign.
Another option that will be released in 1.7 chronograf will be a "Notes" cell type that allows markdown. You could possibly add a note cell to your dashboards with links to the other tools. It's not ideal, but might be better than nothing.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I think, the linked custom links in Chronograf should work irrespective of OAuth2 being enabled especially since Chronograf doesn't behave like a OAuth2 proxy.
Let me describe my use case. I have ELK, Jaeger-ui and Chronograf under different base paths. I would like to have all there services running under the same hostname but different paths.
foo.bar.com/monitoring
=>chronograf
foo.bar.com/tracing
=>Jaeger
foo.bar.com/logging
=>elk
Therefore, I have a central
oauth2 proxy
in my case https://github.com/bitly/oauth2_proxy that does authentication. Therefore, I don't necessarily need the OAuth2 authentication fromChronograf
.I would like to provide custom links in chronograf to kibana and jaeger. However, with the current implementation, it isn't possible.
I think, custom links should be modeled in similar lines to what
Jaeger
does. https://www.jaegertracing.io/docs/1.6/deployment/#ui-configurationIdeally, It would be nice to have Chronograf as a central place for viewing metrics, traces and logs. However, There seems to be
Irrespective of when these above features are implemented, I strongly believe that custom links should not depend on whether OAuth2 in Chronograf is used or not because these custom links need to be secured, they will be secured.
The text was updated successfully, but these errors were encountered: