Update roadmap.md #6475
Update roadmap.md #6475
Conversation
Fixes #5251 Signed-off-by: Charlie Le <[email protected]>
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (2)
docs/roadmap.md:14
- The word 'utilised' should be spelled 'utilized' to match American English conventions.
We have a [helm chart](https://github.com/cortexproject/cortex-helm-chart) but it needs work before it can be effectively utilised by different backends.
docs/roadmap.md:18
- The sentence 'adds' is incomplete. It should be 'adds the following features:' or something similar.
[Prometheus Remote Write 2.0](https://prometheus.io/docs/specs/remote_write_spec_2_0/) adds
| ## Downsampling | ||
| Downsampling means storing fewer samples, e.g. one per minute instead of one every 15 seconds. | ||
| This makes queries over long periods more efficient. It can reduce storage space slightly if the full-detail data is discarded. |
There was a problem hiding this comment.
We have #4322 but it doesn't need to be part of the roadmap. I don't see this with priority
There was a problem hiding this comment.
I think downsampling support is a nice feature for our long term roadmap
There was a problem hiding this comment.
I can add this back in the longer-term roadmap so that attention can still be brought towards it in the future.
docs/roadmap.md
Outdated
| ## Per-metric retention | ||
|
|
||
| Cortex blocks storage supports deleting all data for a tenant after a time period (e.g. 3 months, 1 year), but we would also like to have custom retention for subsets of metrics (e.g. delete server metrics but retain business metrics). |
There was a problem hiding this comment.
This can be removed. You can use a different tenant for different metrics with different retention today
| ## Exemplar support | ||
| [Exemplars](https://docs.google.com/document/d/1ymZlc9yuTj8GvZyKz1r3KDRrhaOjZ1W1qZVW_5Gj7gA/edit) | ||
| let you link metric samples to other data, such as distributed tracing. | ||
| As of early 2021 Prometheus will collect exemplars and send them via remote write, but Cortex needs to be extended to handle them. |
There was a problem hiding this comment.
This can be removed, exemplar support is already there
There was a problem hiding this comment.
I think there is a effort on prometheus to create a storage for exemplars, but i agree, still early to put on the roadmap.
|
|
||
| ## Scalability | ||
|
|
||
| Scalability has always been a focus for the project, but there is a lot more work to be done. We can now scale to 100s of Millions of active series but 1 Billion active series is still an unknown. |
There was a problem hiding this comment.
1 Billion active series in single tenant is doable today.
There are of course other scalability points we could still implement. I don't think we should put them in the roadmap, they are not that critical
|
|
||
| ## Billing and Usage analytics | ||
|
|
||
| We have all the metrics to track how many series, samples and queries each tenant is sending but don't have dashboards that help with this. We plan to have dashboards and UIs that will help operators monitor and control each tenants usage out of the box. |
There was a problem hiding this comment.
I created cortexproject/cortex-jsonnet#64 because this is nice. But it doesn't need to be part of the roadmap
|
We can discuss some ideas on the next community call i guess. Some that i can think of:
|
Added these items to the agenda for our next community call on Jan 30, 2025. https://docs.google.com/document/d/1shtXSAqp3t7fiC-9uZcKkq3mgwsItAJlH6YW6x1joZo/edit?usp=sharing |
|
Hi Folks, Happy New Year! Sorry I missed this week's meeting. Will catch up on notes and on slack. |
docs/roadmap.md
Outdated
|
|
||
| ## Auth Gateway | ||
| ## Support for Prometheus Remote Write 2.0 |
There was a problem hiding this comment.
Should we mention it is a short term roadmap, IIUC?
This sounds like something we can support soon as there is already PR for it now
There was a problem hiding this comment.
We should have roadmap items for longer terms
There was a problem hiding this comment.
I can add a new section for longer term road map items (2+ months) and add a date to the top for when the document was last updated to provide an anchor for the reader on when the expected date of completion should be.
| ## Downsampling | ||
| Downsampling means storing fewer samples, e.g. one per minute instead of one every 15 seconds. | ||
| This makes queries over long periods more efficient. It can reduce storage space slightly if the full-detail data is discarded. |
There was a problem hiding this comment.
I think downsampling support is a nice feature for our long term roadmap
What this PR does:
Updates roadmap
Which issue(s) this PR fixes:
Fixes #5251
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]