Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Custom links based on tags #755

Open
worldtiki opened this issue Jul 19, 2019 · 1 comment
Open

[Feature Request] Custom links based on tags #755

worldtiki opened this issue Jul 19, 2019 · 1 comment

Comments

@worldtiki
Copy link
Contributor

worldtiki commented Jul 19, 2019

A common issue I have is linking events across different monitoring systems. For example, a very common scenario would be me having to copy a trace id from Haystack, open a new tab, open some centralized logging tool like and paste the traceid there to see the logs for that particular trace.

I propose to add a new feature to the Haystack UI where we can configure custom links.
These could be defined in a json file where we would have a title and the rules to build the link itself based on placeholders where we could resolve the values of different tags and potentially time windows as well.
Example below:

[
    {
        "text": "Kibana",
        "url": "http://kibana.mycompany.com/?query=foo_bar=${traceId}"
    },
    {
        "text": "Grafana",
        "url": "http://grafana.mycompany.com/?dashboard=foo_bar=${serviceName}&startTime=${timestamp-5m}&endTime=${timestamp+5m}"
    }
]

The following is a good read on this, and how the same/similar feature works in Jaeger https://itnext.io/custom-links-in-jaeger-ui-3479f72bb815
And a similar feature in Zipkin: https://github.com/openzipkin/zipkin-classic#how-do-i-find-logs-associated-with-a-particular-trace

@mchandramouli
Copy link
Contributor

@worldtiki this was a feature in our previous UI - we lost it when we did the UI. In fact had the same templating like you suggested above with startTime, endTime, serviceName, operationName and traceId. Shouldnt be too hard to add it back in. Both from trends view (start/endtime/servicename and operation) and in trace view (traceid) to any external system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants