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: packages/mk-oracle/README.md
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1100,6 +1100,40 @@ The alias then forms the entry alone and the dropped restriction is reported:
1100
1100
In both cases, check that the alias resolves to the database the section was meant to
1101
1101
query — the connection now depends on your `tnsnames.ora` alone.
1102
1102
1103
+
##### `SQLS_ITEM_SID`
1104
+
1105
+
The legacy plugin builds the item of the `oracle_sql` output as
1106
+
`[[[<SQLS_ITEM_SID>|<SQLS_ITEM_NAME>]]]`, which lets the displayed SID differ from the
1107
+
internal name of the monitored instance. It is mainly used for remote instances, whose
1108
+
internal name is the `REMOTE_INSTANCE_<ID>` variable:
1109
+
1110
+
```bash
1111
+
foo_views_chk1 () {
1112
+
SQLS_SIDS="REMOTE_INSTANCE_PRODPDB1"
1113
+
SQLS_SQL=foo_view_check1.sql
1114
+
SQLS_ITEM_NAME="foo_views_kim1"
1115
+
SQLS_ITEM_SID="PRODPDB1"
1116
+
}
1117
+
```
1118
+
1119
+
**`mk-oracle` has no equivalent field**: the item is always built from the name of the
1120
+
instance the section runs on (`sid:`, or the discovered SID). `SQLS_ITEM_SID` is
1121
+
therefore not migrated, and the migration warns about every section where the item
1122
+
would change:
1123
+
1124
+
```
1125
+
# WARNING: foo_views_chk1: SQLS_ITEM_SID 'PRODPDB1' is not supported and is not migrated; the item of the oracle_sql section is built from the name of the instance the section runs on, so the name of the service changes and it is rediscovered
1126
+
```
1127
+
1128
+
The item is part of the Checkmk service name, so an affected service disappears and is
1129
+
rediscovered under the new name — together with the rules, downtimes and history bound
1130
+
to the old one. Compare the old and the new item before rediscovering, and rename the
1131
+
instance (`sid:`) if you need to keep the previous service name.
1132
+
1133
+
No warning is emitted when the value cannot change anything: the section runs on that
1134
+
one SID anyway, or it uses a custom `SQLS_SECTION_NAME`, for which the legacy plugin
1135
+
emits no item at all.
1136
+
1103
1137
### What Is Not Migrated
1104
1138
1105
1139
The following variables are recognized but only preserved as comments in the output;
@@ -1109,6 +1143,7 @@ port them manually if you still need them:
0 commit comments