Skip to content

Commit

Permalink
Merge pull request #4382 from camilosm/add-topic-instrumentation
Browse files Browse the repository at this point in the history
create topic: instrumentation
  • Loading branch information
ahpook authored Jun 27, 2024
2 parents fe9d0ed + c66115d commit aa4af52
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 1 deletion.
2 changes: 1 addition & 1 deletion docs/API.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ referring to the same subject matter as the topic. You should not list another t
if the alias is a superset of your topic.

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

Each alias must be formatted like that topic's `topic` field (same as the URL slug). Acceptable formatting:
Expand Down
9 changes: 9 additions & 0 deletions topics/instrumentation/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
display_name: Instrumentation
short_description: Instrumentation is the act of inserting instructions into software to analyze it without changing its overall behavior.
topic: instrumentation
wikipedia_url: https://en.wikipedia.org/wiki/Instrumentation_(computer_programming)
related: code-instrumentation, binary-instrumentation
---
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.
It can be done statically, changing the program before executing it, or dynamically, inserting instructions while it's being executed.

0 comments on commit aa4af52

Please sign in to comment.