Skip to main content
bradley
Expert ⭐️
June 28, 2024
New Idea

S3 Export as Rule Action

Related products:CS Rules Engine
  • June 28, 2024
  • 9 replies
  • 115 views

Basically a repost of this: 

that I made during the Horizon Rules Beta a year ago, but figured I’d make it into a votable (and visible idea).

 

I would love to see S3 Export as an action, rather than having to go into your data setup, toggle it on and set it up on a given fetch like you do for DD today.

 

Having it instead as an action, would give you more flexibility in how you can use the S3 as well as make it more intuitive. I realize there isn’t a carryover to Data Designer for this, so also leaving the option to do it as it is today is fine (albeit a bit confusing), but I would consider it an “action” and having all of those in one place just makes sense.

 

As an added bonus, you could easily filter your rules by Action Type of “S3”, instead of todays method of document, guess and check, poke around in Analyzer, or some combination of those.

9 replies

romihache
VIP ⭐️⭐️⭐️⭐️⭐️
June 28, 2024

This is a great idea!

Continuous improvement is better than delayed perfection
dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
June 28, 2024

Anything that lets us stay where we are while building (rather than having to resort to documentation and moving from a rule to data setup) would be fantastic. The filtering by action type sounds 🔥!

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
benwanlessmenlo
Contributor ⭐️⭐️⭐️⭐️⭐️
June 28, 2024

I’ve taken to adding “S3” in the name of the rule, but I don’t believe that this is a good long term solution.

bradley
bradleyAuthor
Expert ⭐️
June 28, 2024

I’ve taken to adding “S3” in the name of the rule, but I don’t believe that this is a good long term solution.

yea, naming conventions are good to standardize for clarity, but the fact it’s the only way to track that kind of metadata on the rules page is bonkers

heather_hansen
VIP ⭐️⭐️⭐️⭐️⭐️
June 28, 2024

I too use naming conventions, but it would be great for S3 exports to behave like other actions. 

Expert ⭐️
July 2, 2024

Concur with this but for different reasons.

 

When you go to test run a rule it won’t truly export which is a current issue IMO since it is an action and not part of a task.

spencer_engel
Expert ⭐️
July 12, 2024

Thank you for posting this. I’m trying to migrate our S3 stuff to a different bucket and am struggling to identify all the assets that either import from or export to S3 😒

bradley
bradleyAuthor
Expert ⭐️
July 12, 2024

Thank you for posting this. I’m trying to migrate our S3 stuff to a different bucket and am struggling to identify all the assets that either import from or export to S3 😒

I was trying to track a file export down just yesterday - after auditing all our rules over the last few weeks and couldn’t find it. Turns out it was buried in one of the 20 fetches of a rule I didn’t have marked as an “export” rule. S3 is such a trap!

heather_hansen
VIP ⭐️⭐️⭐️⭐️⭐️
October 1, 2024

I also just ran into this where my data team informed me that there was an issue with one of the files we were ingesting, and I had no easy way to find where we were ingesting that file.