telegraf/plugins/outputs/application_insights
Paweł Żak d9736d543f
Revive fixes - part 2 (#8835)
* Revive fixes regarding following set of rules:
[rule.if-return]
[rule.increment-decrement]
[rule.var-declaration]
[rule.package-comments]
[rule.receiver-naming]
[rule.unexported-return]
2021-02-16 18:19:50 -05:00
..
mocks Revive fixes - part 2 (#8835) 2021-02-16 18:19:50 -05:00
README.md [outputs.application_insights] Added the ability to set the endpoint url (#7134) 2020-08-19 18:04:24 -04:00
application_insights.go Revive fixes - part 1 (#8797) 2021-02-08 11:18:40 -05:00
application_insights_test.go Revive fixes - part 1 (#8797) 2021-02-08 11:18:40 -05:00
diagnostic_message_subscriber.go Add Microsoft Application Insights output plugin (#4010) 2018-05-15 16:05:59 -07:00
transmitter.go Revive fixes - part 1 (#8797) 2021-02-08 11:18:40 -05:00

README.md

Application Insights Output Plugin

This plugin writes telegraf metrics to Azure Application Insights.

Configuration:

[[outputs.application_insights]]
  ## Instrumentation key of the Application Insights resource.
  instrumentation_key = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx"
  
  ## Regions that require endpoint modification https://docs.microsoft.com/en-us/azure/azure-monitor/app/custom-endpoints
  # endpoint_url = "https://dc.services.visualstudio.com/v2/track"

  ## Timeout for closing (default: 5s).
  # timeout = "5s"

  ## Enable additional diagnostic logging.
  # enable_diagnostic_logging = false

  ## Context Tag Sources add Application Insights context tags to a tag value.
  ##
  ## For list of allowed context tag keys see:
  ## https://github.com/Microsoft/ApplicationInsights-Go/blob/master/appinsights/contracts/contexttagkeys.go
  # [outputs.application_insights.context_tag_sources]
  #   "ai.cloud.role" = "kubernetes_container_name"
  #   "ai.cloud.roleInstance" = "kubernetes_pod_name"

Metric Encoding:

For each field an Application Insights Telemetry record is created named based on the measurement name and field.

Example: Create the telemetry records foo_first and foo_second:

foo,host=a first=42,second=43 1525293034000000000

In the special case of a single field named value, a single telemetry record is created named using only the measurement name

Example: Create a telemetry record bar:

bar,host=a value=42 1525293034000000000