HTTP and ServiceNow Integration
Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.
5B+
Telegraf downloads
#1
Time series database
Source: DB Engines
1B+
Downloads of InfluxDB
2,800+
Contributors
Table of Contents
Powerful Performance, Limitless Scale
Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.
See Ways to Get Started
Input and output integration overview
The HTTP plugin allows for the collection of metrics from specified HTTP endpoints, handling various data formats and authentication methods.
This output plugin streams metrics from Telegraf directly to a ServiceNow MID Server via HTTP, leveraging the nowmetric
serializer for efficient integration with ServiceNow’s Operational Intelligence and Event Management.
Integration details
HTTP
The HTTP plugin collects metrics from one or more HTTP(S) endpoints, which should have metrics formatted in one of the supported input data formats. It also supports secrets from secret-stores for various authentication options and includes globally supported configuration settings.
ServiceNow
Telegraf can be used to send metric data directly to a ServiceNow MID Server REST endpoint. Metrics are formatted either using ServiceNow’s Operational Intelligence (OI) format or JSONv2 format, enabling seamless integration with ServiceNow’s Event Management and Operational Intelligence platforms. The serializer batches metrics efficiently, reducing network overhead by minimizing the number of HTTP POST requests. This integration allows users to quickly leverage metrics in ServiceNow for enhanced observability, proactive incident management, and performance monitoring, with ServiceNow’s operational intelligence capabilities.
Configuration
HTTP
[[inputs.http]]
## One or more URLs from which to read formatted metrics.
urls = [
"http://localhost/metrics",
"http+unix:///run/user/420/podman/podman.sock:/d/v4.0.0/libpod/pods/json"
]
## HTTP method
# method = "GET"
## Optional HTTP headers
# headers = {"X-Special-Header" = "Special-Value"}
## HTTP entity-body to send with POST/PUT requests.
# body = ""
## HTTP Content-Encoding for write request body, can be set to "gzip" to
## compress body or "identity" to apply no encoding.
# content_encoding = "identity"
## Optional Bearer token settings to use for the API calls.
## Use either the token itself or the token file if you need a token.
# token = "eyJhbGc...Qssw5c"
# token_file = "/path/to/file"
## Optional HTTP Basic Auth Credentials
# username = "username"
# password = "pa$$word"
## OAuth2 Client Credentials. The options 'client_id', 'client_secret', and 'token_url' are required to use OAuth2.
# client_id = "clientid"
# client_secret = "secret"
# token_url = "https://indentityprovider/oauth2/v1/token"
# scopes = ["urn:opc:idm:__myscopes__"]
## HTTP Proxy support
# use_system_proxy = false
# http_proxy_url = ""
## Optional TLS Config
## Set to true/false to enforce TLS being enabled/disabled. If not set,
## enable TLS only if any of the other options are specified.
# tls_enable =
## Trusted root certificates for server
# tls_ca = "/path/to/cafile"
## Used for TLS client certificate authentication
# tls_cert = "/path/to/certfile"
## Used for TLS client certificate authentication
# tls_key = "/path/to/keyfile"
## Password for the key file if it is encrypted
# tls_key_pwd = ""
## Send the specified TLS server name via SNI
# tls_server_name = "kubernetes.example.com"
## Minimal TLS version to accept by the client
# tls_min_version = "TLS12"
## List of ciphers to accept, by default all secure ciphers will be accepted
## See https://pkg.go.dev/crypto/tls#pkg-constants for supported values.
## Use "all", "secure" and "insecure" to add all support ciphers, secure
## suites or insecure suites respectively.
# tls_cipher_suites = ["secure"]
## Renegotiation method, "never", "once" or "freely"
# tls_renegotiation_method = "never"
## Use TLS but skip chain & host verification
# insecure_skip_verify = false
## Optional Cookie authentication
# cookie_auth_url = "https://localhost/authMe"
# cookie_auth_method = "POST"
# cookie_auth_username = "username"
# cookie_auth_password = "pa$$word"
# cookie_auth_headers = { Content-Type = "application/json", X-MY-HEADER = "hello" }
# cookie_auth_body = '{"username": "user", "password": "pa$$word", "authenticate": "me"}'
## cookie_auth_renewal not set or set to "0" will auth once and never renew the cookie
# cookie_auth_renewal = "5m"
## Amount of time allowed to complete the HTTP request
# timeout = "5s"
## List of success status codes
# success_status_codes = [200]
## Data format to consume.
## Each data format has its own unique set of configuration options, read
## more about them here:
## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
# data_format = "influx"
ServiceNow
[[outputs.http]]
## ServiceNow MID Server metrics endpoint
url = "http://mid-server.example.com:9082/api/mid/sa/metrics"
## HTTP request method
method = "POST"
## Basic Authentication credentials
username = "evt.integration"
password = "P@$$w0rd!"
## Data serialization format for ServiceNow
data_format = "nowmetric"
## Metric format type: "oi" (default) or "jsonv2"
nowmetric_format = "oi"
## HTTP Headers
[outputs.http.headers]
Content-Type = "application/json"
Accept = "application/json"
## Optional timeout
# timeout = "5s"
## TLS configuration options
# tls_ca = "/etc/telegraf/ca.pem"
# tls_cert = "/etc/telegraf/cert.pem"
# tls_key = "/etc/telegraf/key.pem"
# insecure_skip_verify = false
Input and output integration examples
HTTP
- Collecting Metrics from Localhost: The plugin can fetch metrics from an HTTP endpoint like
http://localhost/metrics
, allowing for easy local monitoring. - Using Unix Domain Sockets: You can specify metrics collection from services over Unix domain sockets by using the http+unix scheme, for example,
http+unix:///path/to/service.sock:/api/endpoint
.
ServiceNow
-
Proactive Incident Management: Utilize the Telegraf and ServiceNow integration to stream infrastructure and application metrics in real-time to ServiceNow Event Management. Automatically trigger incidents or remediation workflows based on thresholds, significantly reducing incident detection and response times.
-
End-to-End Application Monitoring: Deploy Telegraf agents across multiple layers of an application stack, sending performance metrics directly into ServiceNow. Leveraging ServiceNow’s Operational Intelligence, teams can correlate metrics across components, quickly identifying performance bottlenecks.
-
Dynamic CI Performance Tracking: Integrate Telegraf metrics with ServiceNow’s CMDB by using this plugin to push performance data, allowing automatic updates of Configuration Item (CI) health states based on live metrics. This ensures an accurate and current state of infrastructure health in ServiceNow.
-
Cloud Resource Optimization: Collect metrics from hybrid and multi-cloud infrastructures using Telegraf, streaming directly to ServiceNow. Leverage these metrics for real-time analytics, predictive capacity planning, and resource optimization, enabling proactive management and reduced operational costs.
Feedback
Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.
Powerful Performance, Limitless Scale
Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.
See Ways to Get Started
Related Integrations
Related Integrations
HTTP and InfluxDB Integration
The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.
View IntegrationKafka and InfluxDB Integration
This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.
View IntegrationKinesis and InfluxDB Integration
The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.
View Integration