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: CHANGELOG.md
-1
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,6 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).
23
23
-[#7176](https://github.com/apache/trafficcontrol/pull/7176)*ATC Build system* Support building ATC for the `aarch64` CPU architecture
24
24
25
25
### Changed
26
-
-[#2564](https://github.com/apache/trafficcontrol/issues/2564)*Traffic Ops, Traffic Monitor* Renamed RASCAL references to TRAFFIC_MONITOR
27
26
-[#7063](https://github.com/apache/trafficcontrol/pull/7063)*Traffic Ops* Python client now uses Traffic Ops API 4.1 by default.
28
27
-[#6981](https://github.com/apache/trafficcontrol/pull/6981)*Traffic Portal* Obscures sensitive text in Delivery Service "Raw Remap" fields, private SSL keys, "Header Rewrite" rules, and ILO interface passwords by default.
29
28
-[#7037](https://github.com/apache/trafficcontrol/pull/7037)*Traffic Router* Uses Traffic Ops API 4.0 by default
Copy file name to clipboardexpand all lines: docs/source/admin/traffic_monitor.rst
+3
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,9 @@ These are the recommended hardware specifications for a production deployment of
34
34
* It is also recommended that you know the geographic coordinates and/or mailing address of the site where the Traffic Monitor machine lives for optimal performance
35
35
36
36
#. Enter the Traffic Monitor server into Traffic Portal
37
+
38
+
.. note:: For legacy compatibility reasons, the 'Type' field of a new Traffic Monitor server must be 'RASCAL'.
39
+
37
40
#. Make sure the :abbr:`FQDN(Fully Qualified Domain Name)` of the Traffic Monitor is resolvable in DNS.
38
41
#. Install Traffic Monitor, either from source or by installing a :file:`traffic_monitor-{version string}.rpm` package generated by the instructions in :ref:`dev-building` with :manpage:`yum(8)` or :manpage:`rpm(8)`
39
42
#. Configure Traffic Monitor according to `Configuring Traffic Monitor`_
Copy file name to clipboardexpand all lines: docs/source/overview/profiles_and_parameters.rst
+4-2
Original file line number
Diff line number
Diff line change
@@ -112,6 +112,8 @@ SPLUNK_PROFILE
112
112
TM_PROFILE
113
113
A Traffic Monitor Profile.
114
114
115
+
.. warning:: For legacy reasons, the names of Profiles of this type *must* begin with ``RASCAL_``. This is **not** enforced by the :ref:`to-api` or Traffic Portal, but certain Traffic Control operations/components expect this and will fail to work otherwise!
116
+
115
117
TP_PROFILE
116
118
A Traffic Portal Profile. This has no known special meaning to any Traffic Control component(s) (not even Traffic Portal itself), but its use is suggested for the profiles used by any and all Traffic Portal servers anyway.
117
119
@@ -495,8 +497,8 @@ For each Parameter with this Config File value on the same :ref:`Profile <profil
495
497
496
498
.. _tm-related-cache-server-params:
497
499
498
-
traffic_monitor.properties
499
-
''''''''''''''''''''''''''
500
+
rascal.properties
501
+
'''''''''''''''''
500
502
This Config File is meant to be on Parameters assigned to either Traffic Monitor Profiles_ or :term:`cache server` Profiles_. Its allowed :ref:`Parameter Names <parameter-name>` are all configuration options for Traffic Monitor. The :ref:`Names <parameter-name>` with meaning are as follows.
0 commit comments