Skip to content

Commit aa4af52

Browse files
authored
Merge pull request #4382 from camilosm/add-topic-instrumentation
create topic: instrumentation
2 parents fe9d0ed + c66115d commit aa4af52

File tree

2 files changed

+10
-1
lines changed

2 files changed

+10
-1
lines changed

docs/API.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ referring to the same subject matter as the topic. You should not list another t
99
if the alias is a superset of your topic.
1010

1111
For example, `api` makes sense in the `related` field for the `graphql` topic, but because many
12-
repositories tagged with `api` are _not_ be associated with `graphql`, `api` does not make sense
12+
repositories tagged with `api` are _not_ to be associated with `graphql`, `api` does not make sense
1313
in the `aliases` field for `graphql`.
1414

1515
Each alias must be formatted like that topic's `topic` field (same as the URL slug). Acceptable formatting:

topics/instrumentation/index.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
display_name: Instrumentation
3+
short_description: Instrumentation is the act of inserting instructions into software to analyze it without changing its overall behavior.
4+
topic: instrumentation
5+
wikipedia_url: https://en.wikipedia.org/wiki/Instrumentation_(computer_programming)
6+
related: code-instrumentation, binary-instrumentation
7+
---
8+
In computer science, **instrumentation** is a technique that consists of inserting specific instructions into a program to monitor and/or analyze its performance, functionality, or behavior, but without changing how it behaves.
9+
It can be done statically, changing the program before executing it, or dynamically, inserting instructions while it's being executed.

0 commit comments

Comments
 (0)