Skip to content

Latest commit

 

History

History
66 lines (47 loc) · 3.64 KB

README.md

File metadata and controls

66 lines (47 loc) · 3.64 KB
Raw

TrueSight Pulse Remedy Integration Plugin

Collects tickets(Incident management and change management) from Remedy servers and collected tickets are sent to Truesight Intelligence as Events. The plugin allows multiple Remedy instances data to be collected with independent polling interval.

Prerequisites

Supported OS

OS Linux Windows OS X
Supported v v v

Runtime Environment

Runtime node.js Python Java
Required v*
* java 1.8+

TrueSight Pulse Meter versions v4.7.1-865 or later

Ingesting historical Remedy data

If you want to import historical Remedy data into TrueSight Intelligence, it is recommended that you ingest the historical data before configuring the plugin for data collection. For more information, see Remedy bulk ingestion on GitHub.

Plugin Configuration Fields

Field Name Description
AR Server Name The host of Remedy server
Port The port of Remedy server
Username The user of Remedy server
Password The password of Remedy server
App Id The App Id for events on TSI
Poll Interval How often (in minutes) to poll for collecting the tickets
Ticket Type Type of tickets to be collected(Incidents or Change)
Field Mapping Type of fields will be collected(more info please check in template section)
Logging Level Logging level for plugin instance (default is info)

Metrics Collected

Metrics Name Description
Remedy Plugin Heartbeat Heartbeat metric(with value 1) for Remedy Plugin
Remedy Invalid Events Count Remedy Invalid events with size greater than limit (32000 bytes)
Remedy Successful Events Ingestion Count Total events successfully ingested to TSI
Remedy Events Ingestion Failure Count Failed event ingestion count to TSI
Remedy Events Ingestion Exception Plugin exception (values as 0/1, 0 as no exception)

Dashboards

  • Remedy Event Ingestion

Templates

  1. Incident Default Template
  2. Change Default Template

References

Remedy Plugin Documentation