Noop Inc. noop_

Changelog

October 2, 2024

#15

We continue foundational work from the last couple months and introduce better observability and cost transparency. Along with a few updates to Noop Logic.

Contents

Observability

Observability, or seeing what is happening with running software (in real-time), is a guiding principle for the Noop developer platform. Noop Logs are one example: everything across Noop is logged, from edge and application requests to build events and infrastructure lifecycles. Of course, adding more logs doesn’t make a developer’s life any easier unless those logs are organized and presented in a way that quickly surfaces their value.

To that end, we’ve started introducing data visualizations that leverage Log data to represent the current and historical state of your applications. Last month we added deployment information overlaid onto a visualization showing response code aggregations. Combining these two pieces of information it’s easy to quickly see if a deployment causes a service degradation (or improvement) to a running app.

Data visualization showing deployment events over response codes

As a bonus, the overlay is also color coded to show if a deployment is in progress, completed or failed.

Cost Transparency

Another guiding principle for Noop is cost transparency. We want every decision to factor cost. That’s only possible if it’s easy to see the cost alongside what is being charged. To inform our users about cost without overwhelming, we organized cost summaries that map to the overall organizational structure of a Noop account.

Data visualization showing cost of Environment over time

Each level of a Noop account includes an aggregate cost view for the past month, grouped by day. At the top-most level is the Organization. The Organization is the group of all your Applications, this includes all usage for your entire account. The Organization is further broken down by Application, each Application is the sum of all its Environment and Build usage. Finally, Environments include the individual Component and Resource usage.

Armed with the cost information, it’s trivial to make decisions about how to run Application Environments to save money. Costly test environments can be set to Sleep using our Sleepy Services and Preview Environments can be used to create temporary Environments that last only as long as they’re needed.

Logic Updates

New Operators Include

  • at: Get the value at the specified index in the provided array.
  • split: Returns an array where the supplied string is separated at the specified substring value.
  • array: Constructs a new array.
  • object: Constructs a new object.

Operator Updates Include

These updates allow iterating through object key-value pairs the same as iterating through the array type.