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
Copy file name to clipboardExpand all lines: docs/class1/module2/lab2.rst
+84-8
Original file line number
Diff line number
Diff line change
@@ -149,6 +149,7 @@ F5 Application Study Tool Installation and Setup
149
149
# The data_types that should be enabled or disabled. Default-disabled module users can enable those modules
150
150
# by setting the below to true. These will apply to all devices and may be better specified on the
151
151
# per-reciever settings file.
152
+
# The full list of available data types is [here](https://f5devcentral.github.io/application-study-tool/components/otel_collector/receiver_readme.html#available-data_types).
152
153
data_types:
153
154
f5.apm:
154
155
enabled: false
@@ -162,6 +163,18 @@ F5 Application Study Tool Installation and Setup
162
163
enabled: false
163
164
f5.gtm:
164
165
enabled: false
166
+
f5.policy.api_protection:
167
+
enabled: false
168
+
f5.policy.asm:
169
+
enabled: false
170
+
f5.policy.firewall:
171
+
enabled: false
172
+
f5.policy.ip_intelligence:
173
+
enabled: false
174
+
f5.policy.nat:
175
+
enabled: false
176
+
f5.profile.dos:
177
+
enabled: false
165
178
# The TLS settings to use. Either a CA file must be specified or insecure_skip_verify
166
179
# set to true (not recommended)
167
180
tls:
@@ -223,12 +236,21 @@ F5 Application Study Tool Installation and Setup
223
236
# Each entry must have a unique name, starting with bigip/
224
237
# (e.g. bigip/1, bigip/2)
225
238
bigip/1:
239
+
# Endpoint must be specified for each device
240
+
# Set this to the management IP for the device. This must be
241
+
# reachable from the Application Study Tool host (port 443).
226
242
endpoint: https://10.1.1.5
243
+
## Uncommenting any of the following lines will override the defaults in
Notice how the configuration for this BIG-IP consists of the *endpoint* (management) IP address and the *data_types* (modules) enabled/disabled for collection. Its authentication settings are inherited from the ``ast_defaults.yaml`` file.
This particular output reveals ``v0.8.1`` of the OTel Custom Collector. If that version is lower than what's listed on the `f5devcentral / application-study-tool Releases board <https://github.com/f5devcentral/application-study-tool/releases/>`_, perform the following steps. Otherwise, you're ready and free to roll on to :ref:`Accessing F5 AST`.
257
+
This particular output reveals ``v0.9.1`` of the OTel Custom Collector. If that version is lower than what's listed on the `f5devcentral / application-study-tool Releases board <https://github.com/f5devcentral/application-study-tool/releases/>`_, perform the following steps. Otherwise, you're ready and free to roll on to :ref:`Accessing F5 AST`.
210
258
211
259
#. Since local changes have been made to files which are actively tracked for changes in the repo, such as ``.env.device-secrets`` and ``config/bigip_receivers.yaml``, we must stash away those changes prior to performing a ``git pull``. Stashing simply sets them aside temporarily. We'll reincorporate them after pulling the latest code from GitHub.
212
260
@@ -230,7 +278,7 @@ Let's check the AST OTel collector version by examining the ``docker-compose.yam
230
278
231
279
.. code-block:: console
232
280
233
-
sudo git checkout tags/v0.8.1
281
+
sudo git checkout tags/v0.9.1
234
282
235
283
#. Undo the ``git stash`` action, bringing our local changes back where they need to be:
0 commit comments