Skip to main content
Xoxoday Plum supports exporting logs and telemetry data to external monitoring tools through APIs, syslog forwarding, and scheduled batch exports, giving IT and security teams full visibility within their preferred observability stack.

Exporting Logs and Telemetry from Xoxoday Plum

Visibility into platform activity is a core requirement for enterprise IT and security operations teams. Xoxoday Plum provides multiple export pathways so your organisation can centralise reward and incentive platform data within existing monitoring infrastructure — without building bespoke integrations from scratch.

Export Methods Available

Xoxoday Plum delivers log and telemetry data through three primary mechanisms. API-based export allows your operations team to programmatically pull logs on demand or on a defined schedule. This suits organisations running custom dashboards or automation pipelines that ingest data from multiple enterprise systems simultaneously. Syslog forwarding pushes log streams in real time to your designated syslog receiver. This is the preferred method for teams using SIEM solutions, where low-latency event ingestion directly supports threat detection and incident response workflows. Batch exports package log data into structured files delivered at regular intervals. This option works well for organisations processing activity records in data warehouses or long-term compliance archives.

What Data Can Be Exported

Xoxoday Plum telemetry exports include authentication events, redemption transactions, API call records, and administrative actions taken within the platform. This breadth of data supports both operational monitoring and compliance reporting. For organisations operating under ISO 27001 or SOC 2 Type II frameworks, exported audit logs provide the evidence trail required during formal assessments. Security and compliance teams can correlate Xoxoday Plum activity with events from other enterprise applications, building a unified view of access and data-handling across systems.

A Practical Use Case

Consider an organisation that has standardised on a centralised log management platform. Their IT security team already ingests events from HR systems such as SAP SuccessFactors or Darwinbox alongside other application-level logs. By enabling syslog forwarding from Xoxoday Plum, the security team receives reward platform events into the same pipeline — applying identical alerting rules, retention policies, and anomaly detection without any additional tooling overhead.

Configuring Your Export

Export configuration is handled through the Xoxoday Plum administration console. Your IT team can define the export method, target endpoint, log verbosity level, and delivery frequency to match the requirements of your monitoring stack. Once connected, exported data flows continuously with no manual intervention, ensuring your observability tools always reflect current platform activity. Xoxoday Plum support teams can assist with endpoint configuration and data format requirements during initial setup. Learn more: [Xoxoday Plum Help Centre — General](

How does Xoxoday Plum handle API rate limits?

Understand the throttling policies that govern data export and integration calls from Xoxoday Plum.

What audit log data does Xoxoday Plum retain?

Learn about audit log retention periods, data scope, and accessing historical records for compliance reviews.