These are chat archives for getredash/redash

24th
Aug 2016
Neil Shah
@shahneil88
Aug 24 2016 01:50
@arikfr - It still needs user to hover mouse over. I have similar requirement as @norbertbede . I want y axis to display values, without hovering over to the bar.
Use case is, I have put up weekly trend information on a display TV in my office. We could see the trend in bar chart, but people also want to see the values displayed on top of it, for better understanding
Something similar to given in https://plot.ly/python/bar-charts/ , "Styled Bar Chart with Direct Labels"
Norbert Bede
@norbertbede
Aug 24 2016 03:56
@arikfr no. still hover required. @shahneil88 yes agree.
HenroRitchie
@HenroRitchie
Aug 24 2016 06:45
Morning all. I have a problem, I cannot restart the service for redash. The error I get is :http://localhost:9001 refused connection
HenroRitchie
@HenroRitchie
Aug 24 2016 07:12
I had to restart the server to fix the problem. Any reason why this happens?
Florian Pieront
@fpieront
Aug 24 2016 09:51
@HenroRitchie looks like a Supervisorctl error message. It means Supervisorctl can't connect to the supervisord service. it's either not running our your supervisorctl is starting up with a different config

I always have to initiate supervisorctl by specifying the path to the config (same one as used by supervisord) explicitly. For example:

sudo supervisorctl -c /path/to/supervisord/config.conf

in my case this is (on an ubuntu server):
sudo supervisorctl -c /etc/supervisor/supervisord.conf
Florian Pieront
@fpieront
Aug 24 2016 10:16
@arikfr - my next step on redash implementation will be to serve different content & regulate access based on user.
  1. What's the best way to give different users access to different tables? should I add all necessary data sources and assign them based on user groups?
  2. Can I serve dashboard or queries to specific user groups?
Appreciate your guidance
HenroRitchie
@HenroRitchie
Aug 24 2016 13:52
@fpieront Thank you for the feedback. I was hoping for more technical feedback. The redash instance was working fine until yesterday morning. I've only had opportunity to look at it today. The queries were not executing and I thus tried to restart the services. This is when the error occurred. After restarting the instance everything is working fine. I obviously need to figure out what is happening so that I can prevent any future failures.
HenroRitchie
@HenroRitchie
Aug 24 2016 14:27
Hi All. Second question I am running my Redash instance on AWS, but it is extremely slow with frequent 504 time outs. What can I look for when troubleshooting
Florian Pieront
@fpieront
Aug 24 2016 15:11
@HenroRitchie the error you quoted doesn't tell you anything about the Redash process. It's a supervisorctl configutation issue. So there is nothing more technical to infer from your error message
The reason for your server crash is hidden someplace else
HenroRitchie
@HenroRitchie
Aug 24 2016 15:30
@fpieront Ok, thank you. I should probably dig a bit deeper in the log files. Regarding the performance issue I think the problem arose when I tried to query the database with 12000 records. My Redash instance is currently running on a AWS micro server. Is this server big enough or should I look at something a more beefy?
Florian Pieront
@fpieront
Aug 24 2016 15:51
are you using a load balancer in front of your AWS instance? That's given me issues with web apps running on AWS before.
resulting specifically in request timeouts for requests that don't actually take very long
depending on the content of your records and how your table is indexed, it could result in a slow readout. and I believe the I/O spead on aws microinstances is also not good. so it's entirely possible IMO that even something small could result in a timeout for the load balancer if you're running one
Arik Fraimovich
@arikfr
Aug 24 2016 17:25
@HenroRitchie it might be that the supervisord instance is being killed by the OOM killer, because you don't have enough memory. same goes for why you get 504 or queries not returning. if you used the image we supply, you can check logs at /opt/redash/logs.
@norbertbede @shahneil88 I think there is already a GitHub issue for this request, but if not, you're welcome to open. If you can find how to do this with the Plot.ly JS library, and document it in the issue, it will greatly improve the chances of this being implemented in the short term :-)
Norbert Bede
@norbertbede
Aug 24 2016 19:15
@arikfr i will try this in next week. also im interested improve counter widget by arrow UP/Down displaying trend between target and actual - or reported and -1 or +1 period
in my opinion 2 small things make attractive and helpful redash usability
Arik Fraimovich
@arikfr
Aug 24 2016 21:10
@norbertbede improvements to the counter visualization are welcomed!