NCSCALE

Like a <, >, or range for duration, price or whatever numerical values

We are currently working on creating a visual representation of the dependencies and connections between your tools.

By connecting your Stacker account to ncScale, you can enhance your visibility into the processes occurring within your applications. Log Management: Keep your logs organized and easily accessible with our log management feature, which allows you to store and filter logs for up to 30 days. Alerting: Customize your alerts to ensure you stay up-to-date on any crucial developments occurring within your application. Fulltext search: Search for dependencies within your no-code stack.

By connecting your Glide account to ncScale, you can enhance your visibility into the processes occurring within your applications. - Log Management: Keep your logs organized and easily accessible with our log management feature, which allows you to store and filter logs for up to 30 days. - Alerting: Customize your alerts to ensure you stay up-to-date on any crucial developments occurring within your application. - Fulltext search: Search for dependencies within your no-code stack.

The image in the email takes up the entire screen if I don't download pictures. I have to scroll down a lot to find the error message.

Integrate with Pipedream workflows

It would be really nice to be able to purge logs entirely or partially according to one or more filtering criteria.

Currently, when clicking on "See all" next to the "Last edited items" on page "Observability", we access a page "Last edited items". On this page we have an attribute "Tool" which allows to identify the tool only thanks to a logo. When there are several repositories existing for a single tool (e.g. several teams in Make) it could be good to have a text attribute giving more details about the name of the repository, like this is the case when we hover the logo (refer screenshot 1). For now, the workaround is to go directly to the subsection of a dedicated repository (refer screenshot 2)

Search for dependencies not only in the database and in the automation but also in views of your Airtable database.