- Plugin version: v3.0.4
- Released on: 2018-04-06
- Changelog
For other versions, see theVersioned plugin docs.
For plugins not bundled by default, it is easy to install by running bin/logstash-plugin install logstash-output-graphtastic. See Working with plugins for more details.
For questions about the plugin, open a topic in the Discuss forums. For bugs or feature requests, open an issue in Github.For the list of Elastic supported plugins, please consult the Elastic Support Matrix.
A plugin for a newly developed Java/Spring Metrics applicationI didn’t really want to code this project but I couldn’t finda respectable alternative that would also run on any Windowsmachine - which is the problem and why I am not going with Graphiteand statsd. This application provides multiple integration optionsso as to make its use under your network requirements possible.This includes a REST option that is always enabled for your usein case you want to write a small script to send the occasionalmetric data.
Find GraphTastic here : https://github.com/NickPadilla/GraphTastic
This plugin supports the following configuration options plus the Common Options described later.
| Setting | Input type | Required |
|---|---|---|
No |
||
No |
||
No |
||
No |
||
string, one of |
No |
|
No |
||
No |
||
No |
Also see Common Options for a list of options supported by alloutput plugins.
- Value type is number
- Default value is
60
the number of metrics to send to GraphTastic at one time. 60 seems to be the perfectamount for UDP, with default packet size.
- Value type is string
- Default value is
"graphtastic"
if using rest as your end point you need to also provide the application urlit defaults to localhost/graphtastic. You can customize the application urlby changing the name of the .war file. There are other ways to change theapplication context, but they vary depending on the Application Server in use.Please consult your application server documentation for more on applicationcontexts.
- Value type is string
- Default value is
""
setting allows you to specify where we save errored transactionsthis makes the most sense at this point - will need to decideon how we reintegrate these error metricsNOT IMPLEMENTED!
- Value type is string
- Default value is
"127.0.0.1"
host for the graphtastic server - defaults to 127.0.0.1
- Value can be any of:
udp,tcp,rmi,rest - Default value is
"udp"
options are udp(fastest - default) - rmi(faster) - rest(fast) - tcp(don’t use TCP yet - some problems - errors out on linux)
- Value type is hash
- Default value is
{}
metrics hash - you will provide a name for your metric and the metricdata as key value pairs. so for example:
metrics => { "Response" => "%{response}" }
example for the logstash config
metrics => [ "Response", "%{response}" ]
you can also use the dynamic fields for the key value as well as the actual value
- Value type is number
- There is no default value for this setting.
port for the graphtastic instance - defaults to 1199 for RMI, 1299 for TCP, 1399 for UDP, and 8080 for REST
- Value type is number
- Default value is
1
number of attempted retry after send error - currently only way to integrateerrored transactions - should try and save to a file or later consumptioneither by graphtastic utility or by this program after connectivity isensured to be established.
The following configuration options are supported by all output plugins:
- Value type is codec
- Default value is
"plain"
The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output without needing a separate filter in your Logstash pipeline.
- Value type is boolean
- Default value is
true
Disable or enable metric logging for this specific plugin instance.By default we record all the metrics we can, but you can disable metrics collectionfor a specific plugin.
- Value type is string
- There is no default value for this setting.
Add a unique ID to the plugin configuration. If no ID is specified, Logstash will generate one.It is strongly recommended to set this ID in your configuration. This is particularly usefulwhen you have two or more plugins of the same type. For example, if you have 2 graphtastic outputs.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
output { graphtastic { id => "my_plugin_id" }}