Skip to content

[Profiling] Update name of filter fields #3046

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 3, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/en/observability/profiling-tag-data-query.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The only config setting you may want to change is `project-id` (default value is

The `-project-id` flag, or the `project-id` key in the host-agent configuration file, splits profiling data into logical groups that you control.

You can assign any non-zero, unsigned integer <= 4095 to a host-agent deployment you control. In Kibana, the KQL field `service.name` is mapped to `project-id` and you can use it to split or filter data.
You can assign any non-zero, unsigned integer <= 4095 to a host-agent deployment you control. In Kibana, the KQL field `profiling.project.id` is mapped to `project-id` and you can use it to split or filter data.

You may want to set a per-environment project ID (for example, dev=3, staging=2, production=1), a per-datacenter project ID (for example,
DC1=1, DC2=2), or even a per-k8s-cluster project ID (for example, us-west2-production=100, eu-west1-production=101).
Expand Down
4 changes: 2 additions & 2 deletions docs/en/observability/universal-profiling.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -167,11 +167,11 @@ Language (https://www.elastic.co/guide/en/kibana/current/kuery-query.html[KQL]).

Most notably, you may want to filter on:

* `service.name`: the corresponding value of `project-id` host-agent flag, logical group of deployed host-agents
* `profiling.project.id`: the corresponding value of `project-id` host-agent flag, logical group of deployed host-agents
* `process.thread.name`: the process' thread name, e.g. `python`, `java`, or `kauditd`
* `orchestrator.resource.name`: the name of the group of the containerized deployment as set by the orchestrator
* `container.name`: the name of the single container instance, as set by the container engine
* `host.name` or `host.ipstring`: the machine's hostname or IP address (useful for debugging issues on a single Virtual Machine)
* `host.name` or `host.ip`: the machine's hostname or IP address (useful for debugging issues on a single Virtual Machine)

[discrete]
[[profiling-differential-views-intro]]
Expand Down