We’d love to help you get linkerd working for your use case, and we’re very interested in your feedback!
If you’re having trouble or think you’ve found a bug, start by checking the FAQ. If you still need help, you can reach us in a couple of ways:
- Ask questions about configuration or troubleshooting in the linkerd Discourse instance.
- File issues about bugs or feature requests in github issues.
- Chat with us in the linkerd public Slack.
- Email us at [email protected]
You can also report bugs or file feature requests on the linkerd Github repo.
Diagnosing why linkerd is having trouble can be tricky. You can help us by providing a few things.
First, a metrics dump is often critical for us to understanding what linkerd is doing. You can accomplish this by running the following script:
#!/bin/bash while true; do curl -s http://localhost:9990/admin/metrics.json > l5d_metrics_`date -u +'%s'`.json sleep 60 done
This script will produce one file a minute.
If these metrics are insufficient, we may also ask you to capture some network traffic. One way to do this is with tcpdump:
$ /usr/sbin/tcpdump -s 65535 'tcp port 4140' -w linkerd.pcap
(assuming you’re running linkerd on the default port of
Run this command while the problem is occurring and assemble the results in a tar or zip file. You can attach these files directly to the Github issue.