Skip to main content

Release notes

Release 1.3.0 - TBD​

Nothing planned yet.

If you are missing anything, please head over to give us a heads-up over at Feature Requests, and we'll see what we can do.

Release 1.2.0 - ETA Q1-2026​

New Features​

filterOnRelations​

Squid will be able to filter results based on relations as in give me all CIs that have a Depends on::Used by to a cmdb_ci_service with Lifecycle Stage Operational

New Configurations​

  • tbd

New Relations​

  • tbd

Release 1.1.1 - ETA 12.2025​

Bugfixes​

Memory load when rendering large amounts of referenced entities​

Fixed excessive memory load with large amounts of data (>200.000 entities) combined with multiple large referenced entities resulting in 200.000 base entities and 1.000.000 referenced entities.

Expand to see detailed description of the underlying problem

Squid can stream unlimited amounts of data and is only restricted by the system property glide.db.max_view_records as well as the Rest and JSON Catch All Transaction Quota Rule timeout settings.

Squid can be configured to render the same referenced entity with different target configurations, e.g. the reference field vendor is configured to be rendered with a targetConfig of core_company_minimal, while the reference field manufacturer is configured to be rendered with atargetConfig of core_company_full. It can and does occur that both vendor and manufacturer reference the same company, e.g. Apple. As Squid has conflicting target configurations, it retrieves the referenced entity multiple times, once for each targetConfig, merges the result and renders the merged object in the JSON section references.

Conflicting Reference Target Configurations

Pre 1.1.1 Squid would cache referenced entities before merging them, potentially causing memory issues.

Squid now retrieves referenced entities in a way that causes zero memory load - without increasing the amount of database requests required.

Squid now only holds the sysIds of referenced entities in memory as well as any entities explicitly configured to be cached.

Release 1.1.0 - 26.09.2025​

New Features​

filterOnTags Query Parameter​

Squid is now able to filter results based on tags (cmdb_key_value) as in give me all CIs with tag aws:servicecatalog:productArn = xxx

See filterOnTags

filterOnTeams Query Parameter​

Squid is now able to filter results based on teams related to a ci as in give me all CIs managed_by team teamA ( cmdb_rel_team).

See filterOnTeams

showTags / showTagsInline Query Parameter​

Squid is now able to render tags (cmdb_key_value) as additional properties of entities.

See showTags / showTagsInline

\{config\}.preservePrefix Query Parameter​

Release 1.0.0 introduced the preservePrefix query parameter. This option allows you to preserve the database view prefix on all root entities.

{config}.preservePrefix allows you to preserve the database view prefix for entities rendered as references or relations, i.e., with other configurations the the root configuration.

See {config}.preservePrefix

excludedViewPrefixes Configuration Option​

Squid now allows specific database view prefixes to be excluded from the returned JSON.

Log as JSON - Analyse squid usage and performance with Splunk / ELK​

Some customers are using Splunk, ELK (ElasticSearch, Kibana, Logstash), etc. as central repository for logs and statistics. These tools are generally better suited for detailed analysis than using the standard ServiceNow syslog, which is known to have performance challenges.

syslog is NOT suitable for statistical analysis

This is a known and acknowledged problem. See

Troubleshooting excessive logging (syslog): The syslog table in an instance can grow very large due to excessive, and if this happens, you may notice issues such as: ... Slow performance or even timeouts when trying to query the System Logs

All the logs in ServiceNow: It is not recommended to retain logging for too long as it can grow big quickly. When it is too big, it becomes difficult for analyzing and slow to search.

If this usecase is relevant for you, you can now switch to a JSON log format, making Splunk/ELK ingress easier.

We've built a proprietary LogForwarder that pushes logs from ServiceNow to Splunk/ELK with a maximum latency of 10 seconds. Depending on customer interest, we might offer this as a separate (free) product. As always, give us a heads-up over at Feature Requests, and we'll see what we can do.

New Predefined Configurations​

  • cmdb_ci_ip_address

New Predefined Relations​

none.

Release 1.0.0 - 14.11.2024​

Initial Release

We track. Ok?