Release blog 2025.1 - The Spring Release
Axual 2025.1 is here with exciting new features and updates. Whether you're strengthening security, improving observability, or bridging old legacy systems with modern event systems, like Kafka, Axual 2025.1 is built to keep you, your fellow developers, and engineers ahead of the game.
On this page
With the release of Axual 2025.1, we’re thrilled to introduce Audit History, a powerful new feature designed to enhance governance tracking.
One of the key highlights is its advanced tracking mechanism, which records critical actions performed on governance resources, ensuring greater transparency and accountability.
Let’s explore the most exciting updates.
Audit History in Self-Service
What is its purpose?
The Audit History Feature is a tracking mechanism that records key actions performed on Governance resources, such as an Instance being created or an Application being updated.
Who is this useful for?
It gives Tenant Admins visibility into changes, ensuring transparency, security, and accountability. By maintaining a detailed history of modifications, this feature helps in troubleshooting incidents and enforcing governance policies.
Explanation in more detail
The Audit History tab is available to Tenant Admin in the Tenant menu, the user can see all events happened in his organization and filter by multiple criteria like:
- Resource Type and Resource Name
- Actor
- Action
- Time Range
You can read more about the Audit History feature here
Restrict Update and Deployment actions in Self-Service
What is its purpose?
In some organizations, the Tenant Admin wants to allow only a few group members to update resources without restricting the visibility of those resources to other members.
With the Update and Deploy Owner Resources settings in the Tenant, the Tenant Admin could control this behavior.
Who is this useful for?
It allows Tenant Admins to make the Self-Service a view-only portal for most users, giving edit permissions to only a few selected users.
This approach fits well in a GitOps approach where a non-human user is used to create, update, and delete resources using the infrastructure-as-a-code, and all human users can just view resources with the Self-Service.
Explanation in more detail
By default, the Tenant settings for Update and Deploy Owned Resources is set to All Group Members. This means that any group member can perform any changes to the owned resources.
When the Tenant settings for Update and Deploy Owned Resources is set to Only Resource Managers, only members of the group marked as Resource Managers can make changes to the owned resources.
With this feature, Users have more granular control over who is allowed to make changes to the resource within a Team.
General Improvements
In our release notes, you will find other, more minor, updates to our product, which we are continuously improving with your feedback.
Check them out here.
Begin your Kafka journey with Axual
Axual 2025.1 is packed with cutting-edge features that simplify your Kafka setup and take security, scalability, and monitoring to new heights. Whether you're optimizing Kafka interface management with an intuitive WYSIWYG interface or implementing Graphical Data flow, Axual 2025.1 delivers the tools you need to stay ahead of the curve.
Ready to take your event stream management to the next level? Contact us today or book a demo to get started with Axual 2025.01 and unlock the full potential of your Kafka ecosystem.
Answers to your questions about Axual’s All-in-one Kafka Platform
Are you curious about our All-in-one Kafka platform? Dive into our FAQs
for all the details you need, and find the answers to your burning questions.
Related blogs
Consumer group offsets are essential components in Apache Kafka, a leading platform for handling real-time event streaming. By allowing organizations to scale efficiently, manage data consumption, and track progress in data processing, Kafka’s consumer groups and offsets ensure reliability and performance. In this blog post, we'll dive deep into these concepts, explain how consumer groups and offsets work, and answer key questions about their functionality. We'll also explore several practical use cases that show how Kafka’s consumer groups and offsets drive real business value, from real-time analytics to machine learning pipelines.
Apache Kafka is a powerful event-streaming platform, but does your enterprise need to go all in from day one? In this blog, we explore why starting small with Kafka is the best strategy. Learn how an incremental approach can help you reduce complexity, and scale efficiently as your needs grow. Whether you're new to Kafka or looking for a practical implementation strategy, this guide will set you on the right path.
Kafka Consumer Configuration is at the heart of building efficient, scalable, and reliable data streaming applications. Whether you’re working with event-driven architectures, batch data ingestion, or real-time stream processing, the right configurations can make all the difference. In this guide, we’ll explore the most important Kafka consumer settings, break down their impact, and showcase practical use cases to help you optimize performance. By the end, you’ll have a clear roadmap to fine-tune your Kafka consumers for maximum efficiency.