Skip to content

Conversation

@shri3016
Copy link

What this PR does

Publishes a blog post announcing Cortex v1.20.0 release, highlighting major new features and their benefits for Cortex users.

The blog post covers:

  • Prometheus Remote Write 2.0 support (experimental)
  • Parquet format support for storage (experimental)
  • Advanced query federation with regex tenant resolver
  • gRPC stream push for distributor-ingester communication
  • Enhanced native histogram support
  • Resource-based monitoring and limiting
  • UTF-8 name validation support

This helps inform the Cortex community about the significant improvements and capabilities introduced in v1.20.0.

Which issue(s) this PR fixes

Fixes #7104

Checklist

  • Documentation added (blog post)
  • Tests updated (N/A - documentation only)
  • CHANGELOG.md updated (N/A - documentation only)

Highlights new features and benefits in v1.20.0 release including:
- Prometheus Remote Write 2.0 support (experimental)
- Parquet format support for storage (experimental)
- Advanced query federation with regex tenant resolver
- gRPC stream push for distributor-ingester communication
- Enhanced native histogram support
- Resource-based monitoring and limiting
- UTF-8 name validation support

Signed-off-by: shri3016] <shriyaktarcar@gmail.com>
@shri3016
Copy link
Author

Hi @yeya24 ,This is my first PR to Cortex which fixes #7104
Can you or anyone from your team please review this and let me know if there's anything else needed from my side or if any changes are required. Thanks!

@shri3016
Copy link
Author

Thanks @yeya24 for allowing the workflow run,I can see that 3 tests are failing,can you guide on what is to be done from my side? Thank you!

@yeya24
Copy link
Contributor

yeya24 commented Jan 16, 2026

Probably just my personal opinion but I think we should probably dive deeper here. This blog post seems similar to the release post we did

Co-authored-by: Friedrich Gonzalez <1517449+friedrichg@users.noreply.github.com>
Signed-off-by: Shriya Kamat Tarcar <73349138+shri3016@users.noreply.github.com>
@shri3016
Copy link
Author

Thanks for the feedback @friedrichg and @yeya24
I’ve removed the quantitative cost-savings claim and updated the wording to focus on query performance and storage footprint without specific numbers.
Please let me know if this revision looks good or if you’d like any further adjustments.Thanks!

@yeya24
Copy link
Contributor

yeya24 commented Jan 16, 2026

Again I feel this is just rewriting what we have from the changelog and it is too shallow to me.
I'd expect we dive deeper to those features and adding screenshots, etc. Instead of just calling them out.

…d limiting

Signed-off-by: shri3016] <shriyaktarcar@gmail.com>
@pull-request-size pull-request-size bot added size/L and removed size/M labels Jan 20, 2026
@shri3016
Copy link
Author

Hi @yeya24 , I've addressed your feedback by rewriting the blog as a deep-dive on the Resource-Based Query Protection feature. My revised post now includes

  • Architecture diagrams showing the throttling flow
  • Complete YAML configuration examples
  • Prometheus metrics and Grafana alert examples
  • Drawbacks and "when to use" guidance

Please let me know if this is more in line with what you were looking for,Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publish blog post to outline new features in latest version 1.20

3 participants