You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Ensure that timeStamp.txt exists with a timeStamp.
46
+
Note: Ensure that timeStamp.txt exists with a timeStamp. The exact time and date should be in the past, but the value does not matter as long as it is in the past because the extension will update it to the current execution time the first time the extension is run.
50
47
51
48
3. Configure queries in config.yml with commands and displayPrefix to determine metric path in AppD metric browser.
52
49
53
-
54
50
Requirement - no duplicate data. You can ignore this section if you choose not to use the freqInSec variable in your queries.
55
51
Set the below argument name for "machineAgent-relativePath" to the relative path of the MachineAgent folder location. For example:
@@ -62,12 +58,8 @@ they run. If duplicate data is detected, this date/time in the file and the cur
62
58
63
59
Go to monitor.xml to the 'task-arguments' tag and find this tag within it:
64
60
argument name="execution_freq_in_secs"
65
-
*You must set this field equal to whatever value is configured for the 'execution-frequency-in-seconds' field within the same file.
66
-
Next set
67
-
argument name="timeper_in_sec"
68
-
This is the value, in seconds, that will replace the variable
69
-
freqInSec
70
-
within the SQL queries in config.yml.
61
+
*You must set this field equal to whatever value is configured for the 'execution-frequency-in-seconds' field within the same file. Next set argument name="timeper_in_sec" This is the value, in seconds, that will replace the variable
62
+
freqInSec within the SQL queries in config.yml.
71
63
72
64
*Note: ALWAYS set "timeper_in_sec" LESS THAN "execution_freq_in_secs"
73
65
This ensures no duplicate data.
@@ -104,15 +96,13 @@ the query data farther back than the execution frequency will create duplicate d
104
96
105
97
Dots below are execution frequency.
106
98
<------| represents the length of time we are looking back when the query is executed, for instance, with the DateAdd() function:
107
-
[REST_OF_QUERY] > DATEADD(ss, -120, GETDATE())
99
+
[REST_OF_QUERY] > DATEADD(ss, -59, GETDATE())
108
100
109
-
This query is pulling data for the last 120 seconds from the present time. Say that the execution frequency specified in
110
-
monitor.xml is 150 seconds. Then each time the extension executes, which is every 150 seconds, we get a data set covering the
111
-
last 120 seconds. That leaves a 30 second gap in data. To ensure that these gaps are very small, set the execution frequency
101
+
This query is pulling data for the last 59 seconds from the present time. Say that the execution frequency specified in
102
+
monitor.xml is 60 seconds. Then each time the extension executes, which is every 60 seconds, we get a data set covering the
103
+
last 59 seconds. That leaves a 1 second gap in data. To ensure that these gaps are very small, set the execution frequency
112
104
10 seconds or more than timeper_in_sec, which is the variable that allows values passed into the queries. So, for example, if
113
-
you set the execution frequency to 240 seconds, set the timeper_in_sec variable in the range of 230 - 240. If there is overlap
114
-
in data, the extension will detect this and pass in a time that is the difference between the current time and the time the
115
-
extension was last successfully executed(taken from timeStamp.txt) to the queries with the freqInSec variable.
105
+
you set the execution frequency to 240 seconds, set the timeper_in_sec variable in the range of 230 - 240. If there is overlap in data, the extension will detect this and pass in a time that is the difference between the current time and the time the extension was last successfully executed(taken from timeStamp.txt) to the queries with the freqInSec variable.
116
106
117
107
No duplicate data, exec freq > timeper_in_sec
118
108
. . .
@@ -129,17 +119,15 @@ Note-Please make sure to not use tab (\t) while editing yaml files. You may want
129
119
yaml validator http://yamllint.com/
130
120
131
121
JDBC Driver
132
-
To use this extension, you will need to provide the JDBC driver, class name, and connection URL. We've provided examples for some
133
-
of the common databases. You'll need to replace the placeholders (HOST, PORT, DB, etc.) in the URL with your own values.
122
+
To use this extension, you will need to provide the JDBC driver, class name, and connection URL. We've provided examples for some of the common databases. You'll need to replace the placeholders (HOST, PORT, DB, etc.) in the URL with your own values.
134
123
135
124
Metrics Provided
136
125
The metrics created by this extension depend on the query you provide. The column names will be used as the metric names, and the first column of each row will be used as a folder name.
137
126
For example, the query SELECT "A", 3 as "B" would create a new metric folder called A, with a new metric B whose value would be 3.
138
127
139
128
Restrictions
140
-
The first column is assumed to be a string. All other columns are assumed to be long integers.
141
-
129
+
The first column is assumed to be a string. All other columns are assumed to be long integers. If you set an execution frequency longer than 1 minute, then you will get metric data gaps that will skew baselines. The machine agent, by design, places 0 values in the spots where there are gaps in metric data. For example, if you set the execution frequency in monitor.xml to 180 seconds, you will have two data points missing in between each metric.
0 commit comments