Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/uninett/argus_ticket_rt
This is a plugin to create tickets in Request Tracker from Argus
https://github.com/uninett/argus_ticket_rt
Last synced: about 1 month ago
JSON representation
This is a plugin to create tickets in Request Tracker from Argus
- Host: GitHub
- URL: https://github.com/uninett/argus_ticket_rt
- Owner: Uninett
- License: gpl-3.0
- Created: 2022-11-18T08:11:12.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2023-12-14T12:23:25.000Z (about 1 year ago)
- Last Synced: 2024-03-14T15:26:57.077Z (10 months ago)
- Language: Python
- Size: 48.8 KB
- Stars: 0
- Watchers: 8
- Forks: 1
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# argus_ticket_rt
This is a plugin to create tickets in Request Tracker from [Argus](https://github.com/Uninett/argus-server)
The API supported is RT V2. RT 4.4 needs [RT::Extension::REST2](https://github.com/bestpractical/rt-extension-rest2)
to support V2, while RT 5.0.0 and later has the support included.
## Settings
* `TICKET_PLUGIN` must be set to `"argus_ticket_rt.RequestTrackerPlugin"`
* `TICKET_ENDPOINT`: Link to instance, absolute URL
* `TICKET_AUTHENTICATION_SECRET`: Standard username/password or token:
```
{
"username": username,
"password": password
}
```
or
```
{
"token": token
}
```
It is recommended to create an RT API user and to ensure that that user has
the necessary authorization for creating tickets in the relevant queue.
Username and password login can be disabled if the login happens through an
external provider. In that case an authentication token should be used.
If authentication tokens are enabled in RT they can be created under
"Logged in as ..." -> "Settings" -> "Auth tokens".
This could however be turned off side-wide or just for that specific user.
In that case please contact the responsible RT administrator.
* `TICKET_INFORMATION`:
Queue (obligatory)
```
{
"queue": queue_name
}
```
### Custom fields (optional)
There are two ways of automatically filling custom fields:
1. Custom fields that are always the same, independent of the incident.
These will be set in `custom_fields_set` with the name of the custom field as key and the fixed value as value.
```
{
"custom_fields_set" : {
"name_of_custom_field": set_value,
}
}
```
2. Custom fields that are filled by attributes of the Argus incident. These are set in `custom_fields_mapping` with the name of the custom field as key and the name of the attribute as it is returned by the API as value (e.g. `start_time`). If the information can be found in the tags the value consists of a dictionary with `tag` as the key and the name of the tag as the value (e.g. {"tag": "host"}).
```
{
"custom_fields_mapping" : {
"name_of_custom_field": attribute_of_incident,
"name_of_custom_field": {"tag": name_of_tag},
}
}
```
## Library
The library used is [rt](https://pypi.org/project/rt/)
instead of [rt-client](https://pypi.org/project/rt-client/)
because "rt-client" does not support token authentication.
## Code style
argus_ticket_rt uses black as a source code formatter. Black can be installed
by running
```console
$ pip install black
```
A pre-commit hook will format new code automatically before committing.
To enable this pre-commit hook, run
```console
$ pre-commit install
```