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

Timestamp not returning correctly. #32

Closed
JustinTweedie opened this issue Jun 23, 2021 · 10 comments
Closed

Timestamp not returning correctly. #32

JustinTweedie opened this issue Jun 23, 2021 · 10 comments

Comments

@JustinTweedie
Copy link

I have compiled the plugin on a Ubuntu machine with the latest Grafana version.
The OPC UA connects correctly but all timestamps are "1970-01-01 02:27:04".

@alydersen
Copy link
Contributor

Hi @JustinTweedie !

Have you tried to use the dome OPC UA server at opc.tcp://opcua.prediktor.com:4880 to see if you get the same issue with timestamps there?

@JustinTweedie
Copy link
Author

JustinTweedie commented Jun 25, 2021 via email

@sleiban
Copy link
Collaborator

sleiban commented Jun 25, 2021

Hi, Justin!
What kind of aggregation have you specified? Raw or Interpolative are usually good choices.

image

Br.
Oddvar

@JustinTweedie
Copy link
Author

JustinTweedie commented Jun 25, 2021 via email

@sleiban
Copy link
Collaborator

sleiban commented Jun 25, 2021

You should find log files beneath the plugin directory. plugins\opcua\logs

Br.
Oddvar

@JustinTweedie
Copy link
Author

JustinTweedie commented Jun 25, 2021 via email

@alydersen
Copy link
Contributor

Hi Justin,

I'd think this is something wrong in the build/compile, as this doesn't happen other places we've seen. Could you try to build it on another machine?

@JustinTweedie
Copy link
Author

JustinTweedie commented Jun 25, 2021 via email

@alydersen
Copy link
Contributor

Hello @JustinTweedie,

Could it be that 470f76f have fixed your issue? It is part of the main branch now.

@alydersen
Copy link
Contributor

@JustinTweedie The plugin is listed in the official store now, so that should make it a lot easier for you to test it again. Thanks to @srclosson :-)

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

No branches or pull requests

3 participants