본문으로 건너뛰기

변환

도착하는 각 이벤트를 저장하기 전에 다듬습니다. 이벤트를 버리거나, 속성의 이름을 바꾸거나 제거하거나 해시하거나, 속성을 필수로 만듭니다.

What a rule does

Transformations sit under Connect. Each rule runs on every arriving event it applies to, top to bottom, before anything stores or shows the event, and a change applies within a minute. A project holds at most 50 rules. New rule asks for a name, the events it applies to (an event name, a prefix ending in *, or a lone * for every event) and what it does:

  • Drop events: stop matching events from being stored.
  • Rename a property: move a property’s value to a new name.
  • Remove properties: delete properties, such as card numbers, before they are stored.
  • Hash properties: replace values with a keyed hash that still matches across events.
  • Require properties: check that events carry the properties they must, each with an optional type (text, number, true or false). An event that fails is dropped, or kept with what failed listed in $invalid.

Order, testing and history

The list reads each rule as a sentence, with a switch to turn it on or off and how many events it matched today and yesterday. Drag a rule by its grip to change the order the rules run in. Test runs a sample event (a name and its properties as JSON) through the enabled rules and shows what each rule did and what would be stored, or which rule dropped it. Opening a rule shows the Rule itself and its Changes: who created it and which fields each edit changed.

Permissions, API and agents

Adding, changing, reordering or deleting a rule needs prodantix.events.manage. REST serves the rules under /v1/projects/{projectId}/transformations, and agents read them and test an event against them over MCP (prodantix.events.transformations, prodantix.events.test_transformations).