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

Current data issue #253

Open
MarkTasker opened this issue Aug 14, 2020 · 6 comments
Open

Current data issue #253

MarkTasker opened this issue Aug 14, 2020 · 6 comments
Assignees

Comments

@MarkTasker
Copy link

The data stored in the pg database is 1 hour old and I would like to make this as up to date as possible. Is this an issue at the perfmon level or in the process taking an hour to process the data and store it in the database.

If it's the process is there a way to reduce that time so we can get data sooner?

@danjrahm danjrahm self-assigned this Aug 17, 2020
@danjrahm
Copy link
Contributor

Hello,

To clarify, is this the data being polled by TabMon?

If you would like data to be polled by TabMon at a higher frequency, you can always adjust the PollInterval in the TabMon config. The PollInterval will look like this:

If this is about the data in Tableau Server's postgres database, that should be up to date as long as the connection is live.

Please let me know if that helps.

Thanks,
Dan

@MarkTasker
Copy link
Author

Hi Dan,
Thank you for getting back to me. The polling interval is set as follows:

However, the data timestamp is postgres is always 1 hour behind current time. I'd like to figure out why there is a lag between the TabMon process which looks to run every minute and the data being available in the postgres database.

@MarkTasker
Copy link
Author

!-- Polling rate, in seconds --
PollInterval value="60"

@MarkTasker
Copy link
Author

Could it be due to BST?

@MarkTasker
Copy link
Author

It appears to be the calculation:
DATETIME(INT((FLOAT([Timestamp]))*(1440/[Minute Interval]))/(1440/[Minute Interval]))
if you try DATETIME(INT((FLOAT(Now()))) you get the hour difference when comparing to now()
Not sure if I am using the latest version as this could already be fixed.

@MarkTasker
Copy link
Author

To get around the lost hour I am just adding it back in to the rounded timestamp equation:
DATETIME(INT((FLOAT([Timestamp])+(1/24))*(1440/[Minute Interval]))/(1440/[Minute Interval]))

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

2 participants