Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 49b966a

Browse files
rename programmatic to focused
1 parent 48535f2 commit 49b966a

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

‎README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,14 +79,14 @@ All initialization options:
7979
* `app_version` (Optional) Sets application version, which can be used to associate profiling information with the source code release.
8080
* `app_environment` (Optional) Used to differentiate applications in different environments.
8181
* `host_name` (Optional) By default, host name will be the OS hostname.
82-
* `auto_profiling` (Optional) If set to `False`, disables automatic profiling and reporting. Programmatic or manual profiling should be used instead. Useful for environments without support for timers or background tasks.
82+
* `auto_profiling` (Optional) If set to `False`, disables automatic profiling and reporting. Focused or manual profiling should be used instead. Useful for environments without support for timers or background tasks.
8383
* `debug` (Optional) Enables debug logging.
8484
* `cpu_profiler_disabled`, `allocation_profiler_disabled`, `block_profiler_disabled`, `error_profiler_disabled` (Optional) Disables respective profiler when `True`.
8585
* `include_agent_frames` (Optional) Set to `True` to not exclude agent stack frames from profile call graphs.
8686
* `auto_destroy` (Optional) Set to `False` to disable agent's exit handlers. If necessary, call `destroy()` to gracefully shutdown the agent.
8787

8888

89-
#### Programmatic profiling
89+
#### Focused profiling
9090

9191
Use `agent.profile(name)` to instruct the agent when to start and stop profiling. The agent decides if and which profiler is activated. Normally, this method should be used in repeating code, such as request or event handlers. In addition to more precise profiling, timing information will also be reported for the profiled spans. Usage example:
9292

‎README.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -114,8 +114,8 @@ All initialization options:
114114
- ``host_name`` (Optional) By default, host name will be the OS
115115
hostname.
116116
- ``auto_profiling`` (Optional) If set to ``False``, disables automatic
117-
profiling and reporting. Programmatic or manual profiling should be
118-
used instead. Useful for environments without support for timers or
117+
profiling and reporting. Focused or manual profiling should be used
118+
instead. Useful for environments without support for timers or
119119
background tasks.
120120
- ``debug`` (Optional) Enables debug logging.
121121
- ``cpu_profiler_disabled``, ``allocation_profiler_disabled``,
@@ -127,8 +127,8 @@ All initialization options:
127127
handlers. If necessary, call ``destroy()`` to gracefully shutdown the
128128
agent.
129129

130-
Programmatic profiling
131-
^^^^^^^^^^^^^^^^^^^^^^
130+
Focused profiling
131+
^^^^^^^^^^^^^^^^^
132132

133133
Use ``agent.profile(name)`` to instruct the agent when to start and stop
134134
profiling. The agent decides if and which profiler is activated.
File renamed without changes.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /