Telegraf Configuration File in Linux server for oracle log file

Hi Everyone,
I developed oracle log file script for reading the alert log ,
but my issue is databases is created successfully but measurement is not craeted.

script file:
adrcihome=“diag/rdbms/orcl/orcl”
logfile="/tmp/adrci.log"

incident=""
alert=""
alertdescription=""

#unixtime=""
#oldunixtime=""

get ORA messages from the last 5 minutes

$adrci -exec “set\ home\ $adrcihome;show\ alert\ -p\ “message_text like ‘%ORA-%’\ and\ originating_timestamp\ >\ systimestamp-1/288” -term;” > $logfile

get ORA messages from the last day

$adrci -exec “set\ home\ $adrcihome;show\ alert\ -p\ “message_text like ‘%ORA-%’\ and\ originating_timestamp\ >\ systimestamp-1” -term;” > $logfile

convert line endings (if logfile was created on windows)

sed -i ‘s/\r$//’ $logfile

while read line; do
if [[ -z “$line” ]]; then
continue ;
else
# check if line contains datetime
regex=’^[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6} [±][0-9]{2}:[0-9]{2}’
if [[ $line =~ regex ]]; then # the alert time and convert it nanosecond-precision Unix time unixtime=(date -d “$line” +"%s%N")
# reset variables
incident=""
alert=""
alertdescription=""
else
if [[ $unixtime != “” ]]; then
# check if line contains incident number
if [[ line =~ (\(incident=(.*?)\)) ]]; then incident=(echo “${BASH_REMATCH}” | grep -o ‘[0-9]+’)
fi

    # check if ORA message
    if [[ $line =~ (ORA-[0-9]{5}) ]]; then
      # get the ORA error string
      alert=$(echo "${BASH_REMATCH}")

      # get the alert description; escape special characters
      #alertdescription=$(echo $line | grep $alert | cut -d\  -f2- | sed 's/ /\\ /g' | sed 's/,/\\,/g' | sed 's/\"/\\\"/g')
      alertdescription=$(echo $line | grep $alert | cut -d\  -f2- | sed 's/ /_/g' | sed 's/,//g' | sed 's/\"/\\\"/g')
    fi
  fi
fi

fi

if [[ $unixtime != “” && $incident != “” && $alert != “” ]]; then
echo “oracle_alert_logs alert=”$alert",alertdescription="$alertdescription",incident=$incident $unixtime"
else
if [[ $unixtime != “” && $incident == “” && $alert != “” ]]; then
echo “oracle_alert_logs alert=”$alert",alertdescription="$alertdescription",incident=0 $unixtime"
fi
fi

#if [[ $unixtime != “” && $unixtime != $oldunixtime ]]; then

oldunixtime=$unixtime

#fi

done <$logfile

delete the adrci log file

rm $logfile

AgentBase Configuration file :
###############################################################################

Rockwell FTAM - Data Collection - Telegraf Agent Base Configuration

###############################################################################

This is the central agent base configuration used by all Telegraf agents.

Remark: Telegraf input settings must not be configured here. They are located in the component specific configuration files.

###############################################################################

Installation

###############################################################################

Windows service:

1.) Extract Telegraf to: c:\Rockwell\FTApplicationMonitoring\telegraf

2.) Copy this file to: c:\Rockwell\FTApplicationMonitoring\telegraf

2.1.) Copy the desired component metrics configurations to: c:\Rockwell\FTApplicationMonitoring\telegraf\metrics

3.) Create Telegraf service by running this command as admin:

c:\Rockwell\FTApplicationMonitoring\telegraf\telegraf.exe --service install --config c:\Rockwell\FTApplicationMonitoring\telegraf\AgentBaseConfiguration-telegraf.conf --config-directory c:\Rockwell\FTApplicationMonitoring\telegraf\metrics

4.) Start Telegraf service by running this command as admin: c:\Rockwell\FTApplicationMonitoring\telegraf\telegraf.exe --service start

Linux service:

TASK: Describe

Command line testing:

Use this command: telegraf -config AgentBaseConfiguration-telegraf.conf -config-directory YourConfigDirectoryMatchingTheComponentsOfTheServer

E.g. c:\Rockwell\FTApplicationMonitoring\telegraf\telegraf.exe --config c:\Rockwell\FTApplicationMonitoring\telegraf\AgentBaseConfiguration-telegraf.conf --config-directory c:\Rockwell\FTApplicationMonitoring\telegraf\metrics

###############################################################################

AGENT

###############################################################################

Telegraf is entirely plugin driven. All metrics are gathered from the

declared inputs, and sent to the declared outputs.

Plugins must be declared in here to be active.

To deactivate a plugin, comment out the name and any variables.

Use ‘telegraf -config telegraf.conf -test’ to see what metrics a config

file would generate.

Environment variables can be used anywhere in this config file, simply prepend

them with $. For strings the variable must be within quotes (ie, “$STR_VAR”),

for numbers and booleans they should be plain (ie, $INT_VAR, $BOOL_VAR)

Global tags can be specified here in key=“value” format.

[global_tags]

dc = “us-east-1” # will tag all metrics with dc=us-east-1

rack = “1a”

Environment variables can be used as tags, and throughout the config file

user = “$USER”

Configuration for telegraf agent

[agent]

Default data collection interval for all inputs

interval = “10s”

Rounds collection interval to ‘interval’

ie, if interval=“10s” then always collect on :00, :10, :20, etc.

round_interval = true

Telegraf will send metrics to outputs in batches of at most

metric_batch_size metrics.

This controls the size of writes that Telegraf sends to output plugins.

metric_batch_size = 1000

For failed writes, telegraf will cache metric_buffer_limit metrics for each

output, and will flush this buffer on a successful write. Oldest metrics

are dropped first when this buffer fills.

This buffer only fills when writes fail to output plugin(s).

metric_buffer_limit = 10000

Collection jitter is used to jitter the collection by a random amount.

Each plugin will sleep for a random time within jitter before collecting.

This can be used to avoid many plugins querying things like sysfs at the

same time, which can have a measurable effect on the system.

collection_jitter = “0s”

Default flushing interval for all outputs. Maximum flush_interval will be

flush_interval + flush_jitter

flush_interval = “10s”

Jitter the flush interval by a random amount. This is primarily to avoid

large write spikes for users running a large number of telegraf instances.

ie, a jitter of 5s and interval 10s means flushes will happen every 10-15s

flush_jitter = “0s”

By default or when set to “0s”, precision will be set to the same

timestamp order as the collection interval, with the maximum being 1s.

ie, when interval = “10s”, precision will be “1s”

when interval = “250ms”, precision will be “1ms”

Precision will NOT be used for service inputs. It is up to each individual

service input to set the timestamp at the appropriate precision.

Valid time units are “ns”, “us” (or “µs”), “ms”, “s”.

precision = “”

Logging configuration:

Run telegraf with debug log messages.

debug = false

Run telegraf in quiet mode (error log messages only).

quiet = false

Specify the log file name. The empty string means to log to stderr.

logfile = “/var/lib/RockwellWork/telegraf/telegraf.log”

Override default hostname, if empty use os.Hostname()

hostname = “”

If set to true, do no set the “host” tag in the telegraf agent.

omit_hostname = false

###############################################################################

OUTPUTS

###############################################################################

Configuration for sending metrics to InfluxDB

[[outputs.influxdb]]

The full HTTP or UDP URL for your InfluxDB instance.

urls = [“http://nvussjc-ftam5:8086”] ##Later we will change as MONITORING_SERVER

The target database for metrics; will be created as needed.

database = “server_logs” # default naming convention

If true, no CREATE DATABASE queries will be sent. Set to true when using

Telegraf with a user without permissions to create databases or when the

database already exists.

skip_database_creation = false

Name of existing retention policy to write to. Empty string writes to

the default retention policy. Only takes effect when using HTTP.

retention_policy = “autogen”

Write consistency (clusters only), can be: “any”, “one”, “quorum”, “all”.

Only takes effect when using HTTP.

write_consistency = “any”

Timeout for HTTP messages.

timeout = “5s”

HTTP Basic Auth

username = “telegraf”

password = “metricsmetricsmetricsmetrics”

HTTP User-Agent

user_agent = “telegraf”

UDP payload size is the maximum packet size to send.

udp_payload = “512B”

Optional TLS Config for use on HTTP connections.

tls_ca = “/etc/telegraf/ca.pem”

tls_cert = “/etc/telegraf/cert.pem”

tls_key = “/etc/telegraf/key.pem”

Use TLS but skip chain & host verification

insecure_skip_verify = false

HTTP Proxy override, if unset values the standard proxy environment

variables are consulted to determine which proxy, if any, should be used.

http_proxy = “http://corporate.proxy:3128

Additional HTTP headers

http_headers = {“X-Special-Header” = “Special-Value”}

HTTP Content-Encoding for write request body, can be set to “gzip” to

compress body or “identity” to apply no encoding.

content_encoding = “identity”

When true, Telegraf will output unsigned integers as unsigned values,

i.e.: “42u”. You will need a version of InfluxDB supporting unsigned

integer values. Enabling this option will result in field type errors if

existing data has been written.

influx_uint_support = false

###############################################################################

INPUT

###############################################################################

Oracle Log File Plugin

[[inputs.exec]]
commands = [“sh /etc/telegraf/scripts/oracle.sh”]
data_format = “influx”

interval = “1m”
name_suffix = “oracle_logs”

Can anyone suggest me I did mistake.
I am struggling this issue from past 2 week.