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

[BUG] timestamp is in 1000 sec with connector cloudwatch metrics #2366

Open
pjoe opened this issue Oct 30, 2024 · 1 comment
Open

[BUG] timestamp is in 1000 sec with connector cloudwatch metrics #2366

pjoe opened this issue Oct 30, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@pjoe
Copy link

pjoe commented Oct 30, 2024

Describe the bug
The docs says the metric_samples.timestamp should be in unix epoch seconds, but it look to be in 1000 seconds*

To Reproduce
Steps to reproduce the behavior:

  1. Query a metric sample with the connector SELECT timestamp FROM metric_samples WHERE <some filtering> LIMIT 1
  2. Notice the value looks to be in 1000 secs and not secs since unix epoch

Expected behavior
timestamp in unix epoch secs, as per docs

Screenshots / Exceptions / Errors
image

Connector Details (please complete the following information):

  • Version: 2024.42.3
  • Name cloudwatch-metrics

Additional context
Don't think you need the divide by 1000 here:

@pjoe pjoe added the bug Something isn't working label Oct 30, 2024
@colax94
Copy link

colax94 commented Dec 31, 2024

+1 for this, it is not possible to use the connector at the moment because of this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants