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

[Feature] PROMQL query support for timestamp in RFC3339 format #12625

Closed
2 of 3 tasks
shamusx opened this issue Sep 18, 2024 · 0 comments · Fixed by #12644
Closed
2 of 3 tasks

[Feature] PROMQL query support for timestamp in RFC3339 format #12625

shamusx opened this issue Sep 18, 2024 · 0 comments · Fixed by #12644
Assignees
Labels
backend OAP backend related. feature New feature
Milestone

Comments

@shamusx
Copy link

shamusx commented Sep 18, 2024

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

PROMQL /api/v1/query have a parameter for time as per docs but expects specific unix timestamp format. Looking to support format outlined as provided in RFC3339 to support integrations that append a different format such as KEDA ScaledObjects.

Use case

Currently time is required to be in specific format being unix timestamp
query=service_apdex{service="*|details|bookinfo|aks-swdemo01-centralus-1|-", layer="MESH"}[3m]&time=1726668431

Ask is to support timestamp in RFC3339 format:
query=service_apdex{service="*|details|bookinfo|aks-swdemo01-centralus-1|-", layer="MESH"}&time=2024-09-18T13:48:18Z

Related issues

No response

Are you willing to submit a pull request to implement this on your own?

  • Yes I am willing to submit a pull request on my own!

Code of Conduct

@shamusx shamusx added the feature New feature label Sep 18, 2024
@wu-sheng wu-sheng added the backend OAP backend related. label Sep 18, 2024
@wu-sheng wu-sheng added this to the 10.1.0 milestone Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend OAP backend related. feature New feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants