The log viewer in the Enterspeed Management App just received a huge update 🪵

The update focuses on two things: Making it easier to find the right logs, and making it easier to get an overview of the logs.

With the new update, you can now filter on a long list of properties – and not only level, service, and source entity id as before. You can add multiple filters, select operators like is, is not and in – and you can even add filters directly from a specific log entry in order to find logs with similar values. This should improve your chance of finding the log entries you are logging for quite a bit. And not only a single log entry, but also other log entries leading up to the event in order to figure out what started it.

The log list has a set of default columns (Timestamp, Level, Service and Message), but from a specific log entry, you can now toggle any property to be visible in the list as well. This'll give you a better overview when you begin to dig into the list of log entries.

Besides the two new main features, there's a long list or minor improvements, like filtering on relative time intervals, improved navigation options to related objects, and more readable teaser messages.

Go ahead and check it out. We hope you enjoy the new update 🚀

Quickly finding the right file is important in order to work efficiently in any code base and the same goes for the schemas in Enterspeed.

On the Schemas page you can now click the small Search in schemas icon to the right of the search field in order to search by content.

This means the you can now find all schemas with a trigger on a specific source entity type or all schemas with a reference to a specific schema or partial schema that you are maybe considering changing or deleting.

The search result is displayed nicely with highlighting of the specific lines where a match was found.

We continue to expand the list of destinations that you can setup directly in the Management app. Today, we have added two new destinations:

1️⃣ Elastic Search

2️⃣ Clerk.io

Read more about how to use these destinations in our documentation.

If you have logged in to your Enterspeed tenant this week, we are sure that you have already noticed what we are now announcing. But we enjoy launch announcements too much to just drop the feature without a post!

We have included 5 key metrics for your Enterspeed tenant:

• Number of source entities
• Number of Delivery API requests
• Data storage usage
• Queued jobs
• Delivery API availability and server response time

Keep an eye on your plan usage

All Enterspeed tenants have an associated plan, and instead of only being notified when you have crossed your usage limits, you can now keep an eye on your usage directly from the dashboard.

For source entities, this is a simple number of source entities currently ingested and a tick marking the limit on your specific plan.

The graph for Delivery API requests includes two numbers. First, the actual number of used Delivery API requests in the current month. Secondly, we calculate the projected number of Delivery API requests for the current month. It uses a simple forecast model by looking at the previous usage in the current month and projecting that to the end of the month. The tick marks the limit of Delivery API requests.

The third metric shows the current data storage for your tenant. The data storage is the size of all the ingest source entities and again, the tick marks the limit.

Queued jobs

Enterspeed prepares all data asynchronously so that website visitors don't have to wait. When new data is ingested or a schema is deployed, this triggers the processing and one or more jobs are added to the queue. When you ingest a large amount of source entities or deploy one or more schemas that trigger on a large number of source entities, you can now monitor the progress from the app.

Delivery API stats

Availability and performance are the foundation of Enterspeed, and we track these metrics rigorously internally. Now all of our users can follow the global availability and performance metrics across all tenants from the dashboard.

We want to add a small note to the Server response time metric. We monitor this from the Enterspeed application, so we can't include network latency, DNS, and SSL handshaking in this metric. If you want to monitor this, you need to use your own APM tools from the client side.

Let us know what you think

If you have any questions or feedback regarding the metrics dashboard, then we highly appreciate if you share it with us. Please reach out on your Slack support channel or via support@enterspeed.com

Enterspeed is no different from other software; things go wrong, and then you need to figure out why. So we are very happy to announce that you can now access the logs for our destinations the Enterspeed Management app.

If you just want to see how it works, then head over to Settings and the Logs section ➡️

If you want to read more about the feature, then we recommend reading our What to Do When Things Go Wrong blog post?

Only last week, we announced the availability of creating and managing the Algolia, Azure Service Bus, and Webhooks destinations via the Management app. Today, we are expanding the list of destinations to include:

1️⃣ Relewise

2️⃣ Typesense

3️⃣ Elastic App Search

Read more about how to use these destinations in our documentation.

We're thrilled to announce this update: Destinations can now be configured via the management app 🎉

What are Destinations? They're your gateway to effortless integration with third-party services like Algolia and for custom integrations with Azure Service Bus, and Webhooks. With Destinations, pushing data where it's needed has never been easier.

Previously a feature by request, Destinations are now available to all tenants via the Enterspeed Management App.

Curious to learn more? Dive into our documentation on integrating with Enterspeed.

The Management App have been updated, for this release you will notice some smaller features and changes:

↕️ It is now possible to sort both source entities and views by updated date
⬅️ You can hide the left sidebar to give more space for schemas
📋 The JSON document in the testing pane is saved when opening/closing the testing pane
🌚 Dark mode colours have been given a refresh
⌨️ More keyboard navigation options from the ctrl/cmd-k menu powered by CommandBar
🌍 View connected sources on the Environment settings

We hope you enjoy the small new features and we are looking forward to releasing more Management App features. If you have any feedback or questions, then please reach out on your Slack support channel or via support@enterspeeed.com

It is now possible to filter which source entities you want to initiate a reprocess action for. The reprocess action is used when an update to one source entity should also trigger the processing of a schema that isn't directly triggered by that source entity.Until now, it has been possible to reprocess by schema or source entity origin ID. With the introduction of the .filteroption, reprocessing can be done very specifically, yet flexibly and dynamically.

An example of using the filter for the reprocess action is when a product source entity type should trigger the processing of one or more category pages. Using the filter option is similar to the filter method when using references. Below is a simple example:

Read more about actions in the documentation.

Here's a bonus tip for all you eager beavers who can't wait to dive in without even glancing at the manual: Reprocess actions only kick into gear during ingest, not when you're flinging schemas around - because let's face it, schemas don't rearrange the data the reprocess actions are designed to tinker with. So, take a breather, grab a cuppa, and maybe give that documentation a cheeky little peek, eh?

We keep expanding the list of integrations to Enterspeed, and this time it’s a new destination integration from Enterspeed to an external Azure Service Bus.

With this integration, a message is pushed to your own or any other external service bus whenever a view is created, updated, or deleted. In many ways, this works just like our webhooks. However, if you prefer a service bus and are working in the Azure environment, you now have an extra option to choose from. The service bus integration supports both queues and topics as destinations.

As with our other destinations, you decide at the schema level which views should trigger a message.

JavaScript schema example: