Send events via the CLI agent

Send events

After filling the required values in the previous section, we can start sending actor’s generated events via Manufactory agent.

Required keys

• --actor (required) object - Pairs containing attribute name and the corresponding value while considering the correct attribute names and data types. Please refer to Get Actors schema.
• --event (required) object - Pairs containing attribute name and the corresponding value while considering the correct attribute names and data types. Please refer to Get events schema.

Actor example

{
    "city": "New York",
    "country": "USA",
    "username": "john.doe",
    "email": "john.doe@email.com"
}

Event example

{
    "event_name": "login",
    "event_type": "user-actions",
    "made_purchase": false
}

Before we pass actor and event objects, we need to encode the objects using base64.

Agent example

manufactory-agent --actor=ewogICAgImNpdHkiOiAiTmV3I \
                  --event=ewogICAgImV2ZW50X25hbWUiO==

The agent will handle the authentication and sending events, then it will shut down.

Related articles

Rest Api > Send events via the REST API

The POST /events endpoint enables sending actor profiles by requiring org_id project_id actor_profile and attributes with specific data formatting and returns a success message upon completion.

Collector > Collecting events via our CLI agent

The Manufactory agent serves as an alternative data transmission solution ideal for IoT devices with limited resources or scenarios requiring API load reduction through direct event sending capabilities.

Websocket > Send events via the web socket

A websocket connection enables real-time event transmission by sending messages with event type and attributes which returns a status confirmation upon successful delivery.

Manufactory > Collector

A data collection system enables event and actor information transmission through REST API websocket or CLI agent integration while providing a simple interface for viewing the collected data.