Dashboards public links not working #1238
Comments
|
the result from celery command |
|
There are 3 issues here:
|
|
Haven't do anything and now I am getting:
And I don't think it is related with #1194. All queries already have results. I will try to investigate more in depth. |
|
Actually this Internal Server Error is because I used the older link (I generated a new one for the dashboard when was testing it). I think that here we should respond with a 410 or 404 error... |
|
I have just arrived at this line: Locally, I added a line inside def calculate_metrics_on_exception(error):
metrics_logger.error(error)
if error is not None:
calculate_metrics(MockResponse(500, '?', -1))I got this: |
|
I think the last message is more related to the issue number 1. Regarding the main issue, that is the widgets not displaying on public dashboards, my guess is: WDYT @arikfr ? |
|
I tried to log the |
|
Did you manage to understand why the dashboard doesn't load? Or it's loading now? If it's not, can you check |
|
About the It's just a feeling, as I didn't have the chance to debug it yet. |
|
Metrics & |
|
Yesterday I ended up with the following:
Somehow the current_user is being set with an I added some 'logging' lines to the method above. def record_event(org, user, options):
logging.info('user')
logging.info(user)
logging.info('options')
logging.info(options)
logging.info('instance of ApiKey : {}'.format(isinstance(user, ApiKey)))
logging.info('instance of user is: {}'.format(type(user)))
if isinstance(user, ApiUser):
options.update({
'api_key': user.name,
'org_id': org.id
})
#[...]the logs: After see that we were passing an ApiKey, I get confused with the last lines. The With a log line at the end of the method I could see that it worked. The final code: def record_event(org, user, options):
logging.info('user')
logging.info(user)
logging.info('options')
logging.info(options)
logging.info('instance of ApiKey : {}'.format(isinstance(user, ApiKey)))
logging.info('instance of user is: {}'.format(type(user)))
if isinstance(user, ApiUser):
options.update({
'api_key': user.name,
'org_id': org.id
})
elif isinstance(user, ApiKey):
options.update({
'api_key': user.api_key,
'org_id': org.id
})
elif isinstance(user.id, unicode):
options.update({
'api_key': user.id,
'org_id': org.id
})
else:
options.update({
'user_id': user.id,
'org_id': org.id
})
options.update({
'user_agent': request.user_agent.string,
'ip': request.remote_addr
})
if 'timestamp' not in options:
options['timestamp'] = int(time.time())
logging.info(options)
record_event_task.delay(options)The traceback is not raised anymore. No more issues with the |
Of course -- the issue with record_event was never preventing the dashboard to load. Did you check api_error.log and the browser console when loading the dashboard? |
|
The browser console is raising an error: I already saw that, but started to investigate at the server (don't ask me why 😑 ) I will take a look after lunch. |
|
I use docker. to see the logs I run |
|
When using Docker the logs are not saved to files but piped to stdout (and Is any of the queries on this dashboard using parameters? On Aug 19, 2016 6:54 PM, "Wesley" notifications@github.com wrote:
|
|
in fact they are Em Sex, 19 de ago de 2016 13:07, Arik Fraimovich notifications@github.com
|
|
Actually, not sure right now. I know now that we are using filter or Em Sex, 19 de ago de 2016 13:12, Wesley Batista <
|
|
I give up on trying to understand... I have updated to the latest version and it is fixed. |
|
I'm glad it works for you now, although I wonder what fixed it, as I don't remember fixing anything related... :-) Anyway, closing. |
Issue Summary
Hello guys,
Trying to share a dashboard I am getting this:
The log starting from the call:
I think that it is something related to events recording:
I also think that it is strange to get so much
status=500on the calls reported in the log.I have tried to reproduced the steps on the demo instance and it works just fine.
Steps to Reproduce
Technical details:
The text was updated successfully, but these errors were encountered: