@@ -158,62 +158,41 @@ You can turn off logging by setting the log level:
158
158
Other Loggers
159
159
-------------
160
160
161
- .. tabs-drivers::
162
-
163
- .. tab::
164
- :tabid: cpp-sdk
165
-
166
- The C++ SDK uses a sync logger that behaves differently than the rest of
167
- the examples on this page. You can set or change your sync client's log
168
- level to develop or debug your application. You might want to change the
169
- log level to log different amounts of data depending on the app's
170
- environment.
171
-
172
- You can set the level of detail reported by the sync client logger to
173
- specify the level of output you want from the sync client. Get
174
- :cpp-sdk:`an instance of an App's sync manager
175
- <structrealm_1_1internal_1_1bridge_1_1sync__manager.html>`,
176
- and pass a :cpp-sdk:`realm::logger::level <structrealm_1_1logger.html>`
177
- to the ``set_log_level()`` member function:
178
-
179
- .. literalinclude:: /examples/generated/cpp/quick-start.snippet.set-sync-log-level.cpp
180
- :language: cpp
181
-
182
- .. tab::
183
- :tabid: csharp
184
-
185
- .. tab::
186
- :tabid: dart
161
+ The C++ and Java SDKs have additional Loggers that behave differently.
187
162
188
- .. tab::
189
- :tabid: kotlin
163
+ C++ SDK
164
+ ~~~~~~~
190
165
191
- .. tab::
192
- :tabid: csharp
166
+ The C++ SDK uses a sync logger that behaves differently than the rest of
167
+ the examples on this page. You can set or change your sync client's log
168
+ level to develop or debug your application. You might want to change the
169
+ log level to log different amounts of data depending on the app's
170
+ environment.
193
171
194
- The Java SDK uses an older Logger that may not behave like the other SDKs.
195
- The SDK logs events to the Android system log automatically. You can
196
- view these events using :android:`Logcat </studio/debug/am-logcat>`.
172
+ You can set the level of detail reported by the sync client logger to
173
+ specify the level of output you want from the sync client. Get
174
+ :cpp-sdk:`an instance of an App's sync manager
175
+ <structrealm_1_1internal_1_1bridge_1_1sync__manager.html>`,
176
+ and pass a :cpp-sdk:`realm::logger::level <structrealm_1_1logger.html>`
177
+ to the ``set_log_level()`` member function:
197
178
198
- To access newer logging features, use the Kotlin SDK.
179
+ .. literalinclude:: /examples/generated/cpp/quick-start.snippet.set-sync-log-level.cpp
180
+ :language: cpp
199
181
200
- The Java SDK uses the log levels defined by `Log4J
201
- <https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html>`_.
202
- To configure the log level for database logs in your application, pass a
203
- :java-sdk:`LogLevel <io/realm/log/LogLevel.html>` to
204
- :java-sdk:`RealmLog.setLevel() <io/realm/log/RealmLog.html#setLevel-int->`:
182
+ Java SDK
183
+ ~~~~~~~~
205
184
206
- .. literalinclude:: /examples/generated/java/sync/SyncDataTest.snippet.set-client-log-level.java
207
- :language: java
185
+ The Java SDK uses an older Logger that may not behave like the other SDKs.
186
+ The SDK logs events to the Android system log automatically. You can
187
+ view these events using :android:`Logcat </studio/debug/am-logcat>`.
208
188
209
- .. tab::
210
- :tabid: javascript
189
+ To access newer logging features, use the Kotlin SDK.
211
190
212
- .. tab::
213
- :tabid: kotlin
214
-
215
- .. tab::
216
- :tabid: swift
191
+ The Java SDK uses the log levels defined by `Log4J
192
+ <https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html>`_.
193
+ To configure the log level for database logs in your application, pass a
194
+ :java-sdk:`LogLevel <io/realm/log/LogLevel.html>` to
195
+ :java-sdk:`RealmLog.setLevel() <io/realm/log/RealmLog.html#setLevel-int->`:
217
196
218
- .. tab::
219
- :tabid: typescript
197
+ .. literalinclude:: /examples/generated/java/sync/SyncDataTest.snippet.set-client-log-level.java
198
+ :language: java
0 commit comments