New feature: Organizations
Organizations help encompass all development teams working either on the same project or within the same company. In short, Organizations enable you to share:
- Integration tasks with colleagues
- Secure account credentials
- Lookup tables
- Private components
Any of these can be enabled or disabled based on the level of access within the Organizational unit. Yes, that’s right: You can assign roles within organizations
and define the access level for each role. Below you can see an example of roles distribution:
In this example, Admin’s role holds all the rights within the Organizational unit, Integrator‘s role is granted to design integration processes by building the flows and so on (see the picture below), and Guest’s role gives view-only rights to examine the work done by Integrators.
However, the roles names, the number of roles as well as level of access for each role can be customized depending on your requirements
Currently, Organizations are available on-demand. Please note that only elastic.io support team can create an Organization unit and the first Admin for you. After the unit is created, the Organization Admin can invite others and set their level of access.
For more information, please visit the dedicated page in our documentation
New feature: Containers’ Highlight
Previously, if you started an integration flow, you could only see the number of data records that would pass through containers, in other words, integration components sitting inside containers:
Now you can actually see in real time how containers are started and stopped
one by one:
The green bar above each container indicates that it has been started. After data processing is finished, you’ll see the number of data that passed through each container.
The major advantage of this new feature is that you can actually follow the integration flow and identify possible issues even sooner. For example, previously, if there was an error in the code of your component that stopped data from further processing, you would find this out only after the whole integration flow was finished. You would see an error in data processing and have to go through the logs to find the reason behind it.
Now, if there are zero data records shown above you component, but the container is colored in green, than you can immediately see that the container has actually been started successfully, and the problem most likely lies in the component itself.
This new feature saves actually a lot of time spent on finding and debugging errors in the integration flow
This feature is also interesting in combination with Realtime Flows
. In an unlikely event of a container having ‘died’ (unlikely, because if a container ‘dies’, it is automatically restarted unless we ‘killed’ it on purpose for certain reasons), you will be able to see this immediately, as the green bar wouldn’t appear at all.
Improvement: Super latency for Realtime Flows
We continue on making our Realtime Flows
even better and better. As pictures say more than thousand words, here is a picture for you:
This screenshot above shows 90th percentile values aggregated hourly over the last 100 hours. As you can see, it never exceeds 30 milliseconds and the average value is 10 milliseconds
. This super improved latency comes in handy especially in IoT projects, when it is highly important to get large amounts of data processed with very low latency.
What to expect in July
In July we are going to continue working on our new Organizations feature. For one, we are going to introduce an Organizations Switch Bar to allow you to switch between organizations in case you are a member of several.
In addition to that, we are going to refine the representation of integration flow in real time. The Container Highlight was the first step in this direction; next we’re going to introduce real-time notifications about the state of data processing, containers start time, data records updates, etc. All these improvements will help find and debug errors even faster and more easily.
Last but not least, we will be working on a very sophisticated feature meant to replay data processing specifically for data that failed to be processed, for example, if a server where the data is stored misbehaves. Look for more updates on this feature very soon.
Or try the new features now
Request Live Product Tour
We’ve kinda got carried away by our latest cool feature Organizations, so we skipped the May Feature Alert in June. Consider this one a combination of May and June feature alerts;-)
Soooo, we indicated last time that we are going to release a Grand Feature that would include common billing, tasks sharing, components sharing, credentials sharing and role-based access control within one organization. And here it is: