November 2024
Announcing enhanced notifications, new connectors, connector updates, and introducing a new feature: stream selection.
Features
Notification Enhancements
Outbound notifications have been vastly improved and now contain a lot more relevant information. The formatting has also been updated to use specific formatting features for the Channel being used. An example slack notification:
Webhook Style Sources
In addition to the common REST API based Source Connectors Tarsal already supports, Tarsal now supports the ability for a Source Connector to push data to Tarsal via a custom webhook endpoint URL. This will enable Tarsal to build and support a variety of new sources, and we have already released our first connector using this platform: Tray.ai
Webhook Style Destinations
Tarsal now also supports sending data to a Webhook style destination. This will enable Tarsal to build and support a variety of new destination connectors, and we have already release our first connector using this platform: Sumo Logic
Terraform for AWS S3 (Destination)
A new Terraform script is available for configuring the AWS S3 Destination. Please contact us via https://support.tarsal.cloud if you would like to to use the Terraform script in your environment(s).
Additional Enhancements
- Users configured with SSO authentication are now restricted from authenticating using the username/password login method.
- Role mappings are now optional in the SAML configuration.
- A default "Flow Name" has been added as "Source Name -> Destination Name". This can be changed.
- Added the ability to retest a connector after a failed first test.
- Authentication type audit logs messages have been improved
- Authentication type audit log operations have been revisiting and broken out into more discrete operations
- Notification Message History has been updated to show additional information
Bug Fixes
- Pagination resetting after using the actions column has been fixed
- The "Test" button now works on the slack notification edit page
- "Month to date" graphs are no longer skewed by 1 day
- Notifications no longer send to disabled/inactive channels
Connectors
Default Ingest Period
To standardize our Source Connectors, the Start Date has been removed as a configuration option, and Source Connectors now default to ingesting the last 2 weeks upon their first run. There are some exceptions:
- Wiz defaults to -1 minute.
- Zendesk will import all records (not timestamp based)
New Connectors
| Source Connectors | Destination Connectors |
|---|---|
| AWS S3 | Azure Blob Storage |
| Github | Sumo Logic |
| Open AI ChatGPT Enterprise | |
| Oracle Fusion Cloud Applications | |
| Polymer | |
| Tray.ai | |
| Zendesk |
Connector Updates
| Connector | Type | Changes |
|---|---|---|
| Atlassian Confluence | Source | Empty t_ field values changed from "null" to nullt_ip_address will now be null instead of "" when empty |
| Snowflake | Destination | Now supports table normalization |
| Thinkst Canary | Source | t_ip_address field now pulls from first_seen_std |
| Zoom | Source | Added t_email_addressfield |
New Beta Feature: Stream Selection
We have introduced a new Source Connector feature where you can choose which streams to ingest and which to opt out of. This can help reduce both cost and unwanted data in your destinations. Additionally, all Source Connectors now have the option to automatically ingest new streams when Tarsal adds new streams to a connector.
There will be a phased rollout of Source Connectors updating to support this feature
If you would like to receive a notification of when a specific Connector has been updated to support this feature, please contact us via our support site at https://support.tarsal.cloud.
Initial Source Connectors, which currently ingest > 1 stream, supporting stream selection:
- Thinkst Canary
- Tray.ai
- Zoom
Example UI:
