The tungsten_newrelic_event Command
The tungsten_newrelic_event script utilises existing Tunsgten monitor scripts and inserts the results into New Relic.
Usage
tungsten_newrelic_event --account [New Relic Account ID] --key [New Relic Insights API Insert Key] [options]
Where:
| Option | Description | Product |
|---|---|---|
--account | Use to spceify your New Relic Account ID. | CTTR |
--connectorAliases: -c | Run check_tungsten_services -c to check for the Connector. | CT |
--criticalAliases: -C | Specify the Critical alert latency level in seconds; optionally used for check_tungsten_latency.Default: 15 | CTTR |
--curl | Use to specify full path the curl binary. | CTTR |
--debugAliases: -d | Enabling debug also implies enabling of verbose. Debug is VERY chatty, avoid unless essential. | CTTR |
--helpAliases: -h | Showe help text. | CTTR |
--hostname | Use to specify full path the hostname binary. | CTTR |
--key | Use to specify your New Relic Insights API Insert key. | CTTR |
--latencyAliases: -l | Run check_tungsten_latency, optionally specify --warn and --crit. | CTTR |
--nodeAliases: -n | Will execute check_tungsten_services -r which on a Tungsten Cluster node will check the Manager and the Replicator, and on a standalone Tungsten Replicator node, will just check the Replicator. | CTTR |
--noexec | Do not execute the Tungsten Nagios Check script. | CTTR |
--onlineAliases: -o | Run check_tungsten_online, optionally specify a service with --service | CTTR |
--policyAliases: -p | Run check_tungsten_policy | CTTR |
--progressAliases: -r | Run check_tungsten_progress, optionally specify a timeout with --timeout, optionally specify a service with --service | CTTR |
--service | Specify a service name; optionally used for check_tungsten_online and check_tungsten_progress. | CTTR |
--servicesAliases: -s | On a Tungsten Cluster node, will execute check_tungsten_services -r -cwhich will check the Manager, the Replicator and the Connector and on a standalone Tungsten Replicator instance, will executecheck_tungsten_services -r that will just check the Replicator. | CTTR |
--test | Do not execute the New Relic API Insert call. | CTTR |
--timeoutAliases: -t | Specify the time to wait for progress to occur; optionally used for check_tungsten_progress.Default: 1 | CTTR |
--tmpfile | Use to specify full path to the temp JSON file. Default: ./new_relic_event.json | CTTR |
--verboseAliases: -v | CTTR | |
--warnAliases: -w | Specify the Warning alert latency level in seconds; optionally used for check_tungsten_latency.Default: 5 | CTTR |
By default all of the following Nagios check scripts under $CONTINUENT_ROOT/tungsten/cluster-home/bin
are executed and the results of each are inserted into NewRelic as the associated EventType.
| Executable | EventType |
|---|---|
check_tungsten_latency | CheckTungstenLatency |
check_tungsten_online | CheckTungstenOnline |
check_tungsten_policy | CheckTungstenPolicy |
check_tungsten_progress | CheckTungstenProgress |
check_tungsten_services -r -c | CheckTungstenServices Tungsten Clustering Only |
check_tungsten_services -r | CheckTungstenServices |
check_tungsten_services -r | CheckTungstenNode |
check_tungsten_services -c | CheckTungstenConnector Tungsten Clustering Only |
If you specify a check to execute by using one or more cli args, then only those checks specified will be run.
curl must be installed and available on the PATH.
You must provide your New Relic Account ID and your New Relic Insights API Insert Key for the script to function.