@@ -326,12 +326,12 @@ However, ``DELTA`` is not supported for custom metrics.
326326specified::
327327
328328 >>> client.write_point(metric=metric, resource=resource,
329- ... value=3.14, end_time=end_time) # API call
329+ ... value=3.14, end_time=end_time) # API call
330330
331331By default, ``end_time `` defaults to :meth: `~datetime.datetime.utcnow() `, so metrics can be written
332332to the current time as follows::
333333
334- >>> client.write_point(metric, resource, 3.14) # API call
334+ >>> client.write_point(metric, resource, 3.14) # API call
335335
336336``CUMULATIVE `` metrics enable the monitoring system to compute rates of increase on metrics that
337337sometimes reset, such as after a process restart. Without cumulative metrics, this
@@ -341,15 +341,15 @@ time should be re-used repeatedly as more points are written to the time series.
341341In the examples below, the ``end_time `` again defaults to the current time::
342342
343343 >>> RESET = datetime.utcnow()
344- >>> client.write_point(metric, resource, 3, start_time=RESET) # API call
345- >>> client.write_point(metric, resource, 6, start_time=RESET) # API call
344+ >>> client.write_point(metric, resource, 3, start_time=RESET) # API call
345+ >>> client.write_point(metric, resource, 6, start_time=RESET) # API call
346346
347347To write multiple ``TimeSeries `` in a single batch, you can use
348348:meth: `~google.cloud.monitoring.client.write_time_series `::
349349
350350 >>> ts1 = client.time_series(metric1, resource, 3.14, end_time=end_time)
351351 >>> ts2 = client.time_series(metric2, resource, 42, end_time=end_time)
352- >>> client.write_time_series([ts1, ts2]) # API call
352+ >>> client.write_time_series([ts1, ts2]) # API call
353353
354354While multiple time series can be written in a single batch, each ``TimeSeries `` object sent to
355355the API must only include a single point.
0 commit comments