-
Notifications
You must be signed in to change notification settings - Fork 15
/
Copy pathperformance-copilot-metrics.asm.xml
257 lines (247 loc) · 8.78 KB
/
performance-copilot-metrics.asm.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- This file originates from the project https://github.com/openSUSE/doc-kit -->
<!-- This file can be edited downstream. -->
<!DOCTYPE assembly
[
<!ENTITY % entities SYSTEM "../common/generic-entities.ent">
%entities;
]>
<!-- refers to legacy doc: <add github link to legacy doc piece, if applicable> -->
<!-- point back to this document with a similar comment added to your legacy doc piece -->
<!-- refer to README.md for file and id naming conventions -->
<assembly version="5.2" xml:lang="en"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:trans="http://docbook.org/ns/transclusion"
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://docbook.org/ns/docbook">
<!-- resources section references all topic chunks used in the final article
-->
<!-- R E S O U R C E S -->
<!-- Glue files -->
<!-- Concept files -->
<resources>
<resource xml:id="_pcp-overview" href="../concepts/pcp-overview.xml">
<description>Overview of PCP</description>
</resource>
</resources>
<!-- Tasks -->
<resources>
<resource xml:id="_pcp-getting-container" href="../tasks/pcp-getting-container.xml">
<description>Getting the PCP container</description>
</resource>
<resource xml:id="_pcp-start-onboot" href="../tasks/pcp-start-onboot.xml">
<description>Starting the PCP container on each boot</description>
</resource>
<resource xml:id="_pcp-listing-metrics" href="../tasks/pcp-listing-metrics.xml">
<description>Listing the PCP metrics</description>
</resource>
<resource xml:id="_pcp-checking-metrics" href="../tasks/pcp-checking-metrics.xml">
<description>Checking the PCP metrics</description>
</resource>
<resource xml:id="_pcp-recording-metrics" href="../tasks/pcp-recording-metrics.xml">
<description>Recording the PCP metrics</description>
</resource>
</resources>
<!-- References -->
<resources>
<resource xml:id="_pcp-service-configuration" href="../references/pcp-service-configuration.xml">
<description>PCP service configuration</description>
</resource>
<resource xml:id="_pcp-starting-container" href="../references/pcp-starting-container.xml">
<description>Starting the PCP container</description>
</resource>
</resources>
<!-- Legal -->
<resources>
<resource href="../common/legal.xml" xml:id="_legal">
<description>Legal Notice</description>
</resource>
<resource href="../common/license_gfdl1.2.xml" xml:id="_gfdl">
<description>GNU Free Documentation License</description>
</resource>
</resources>
<!-- S T R U C T U R E -->
<structure renderas="article" xml:id="pcp-container" xml:lang="en">
<merge>
<title>Analyzing Performance Metrics Using the Performance Co-Pilot Analysis Toolkit</title>
<revhistory xml:id="rh-pcp-container">
<revision><date>2024-11-02</date>
<revdescription>
<para>Initial version</para>
</revdescription>
</revision>
</revhistory>
<!-- TODO: provide a listing of possible and validatable meta entry values. Maybe in our geekodoc repo? -->
<!-- add author's e-mail -->
<meta name="maintainer" content="[email protected]" its:translate="no"/>
<!-- ISO date of last update as YYYY-MM-DD -->
<meta name="updated" content="2024-11-02" its:translate="no"/>
<!-- this does not work yet. Use the dm tags listed below for now
<meta name="bugtracker" its:translate="no">
<phrase role="url">https://bugzilla.suse.com/enter_bug.cgi</phrase>
<phrase role="component">Non-product-specific documentation</phrase>
<phrase role="product">Smart Docs</phrase>
<phrase role="assignee">[email protected]</phrase>
</meta>
-->
<!-- not supported, yet. Use dm: tag for now
<meta name="translation" its:translate="no">
<phrase role="trans">yes</phrase>
<phrase role="language">de-de,cs-cz</phrase>
</meta>
-->
<!-- enter the platform identifier or a list of
identifiers, separated by ; -->
<!-- For a full list of meta tags and their values,
see https://confluence.suse.com/x/aQDWNg
-->
<meta name="architecture">
<phrase>&x86-64;</phrase>
</meta>
<!-- enter one or more product names and version -->
<meta name="productname" its:translate="no">
<productname version="6.1">&slm;</productname>
</meta>
<meta name="title" its:translate="yes">Performance Co-Pilot analysis toolkit</meta>
<meta name="description" its:translate="yes">The toolkit that collects performance metrics from
the system</meta>
<meta name="social-descr" its:translate="yes">Performance Co-Pilot analysis toolkit</meta>
<!-- Determines "filter by task" filter value -->
<meta name="task">
<phrase>Monitoring</phrase>
<phrase>Admministration</phrase>
</meta>
<meta name="series">Products & Solutions</meta>
<dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
<dm:bugtracker>
<dm:url>https://bugzilla.suse.com/enter_bug.cgi</dm:url>
<dm:component>Documentation</dm:component>
<dm:product>SUSE Linux Micro 6.1</dm:product>
<!-- provide your BUGZILLA e-mail address, otherwise this does not work correctly-->
<dm:assignee>[email protected]</dm:assignee>
</dm:bugtracker>
<dm:translation>yes</dm:translation>
</dm:docmanager>
<abstract>
<variablelist>
<varlistentry>
<term>WHAT?</term>
<listitem>
<para>
For performance monitoring purposes, &productname; provides a container image
that enables you to run the Performance Co-Pilot (PCP) analysis toolkit
in a container.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>WHY?</term>
<listitem>
<para>
You want to monitor performance on your system, and this article provides information
on how to configure and use the toolkit.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>EFFORT</term>
<listitem>
<para>
It takes approximately 40 minutes of reading time.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>GOAL</term>
<listitem>
<para>
You will be able to start the PCP container with a configuration that suits your needs.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>REQUIREMENTS</term>
<listitem>
<itemizedlist>
<listitem>
<para>
A running instance of &productnameshort;.
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
</abstract>
</merge>
<module resourceref="_pcp-overview" renderas="section">
<merge>
<abstract>
<para/>
</abstract>
</merge>
<module resourceref="_pcp-getting-container" renderas="section">
<merge>
<abstract>
<para/>
</abstract>
</merge>
</module>
</module>
<module resourceref="_pcp-starting-container" renderas="section">
<merge>
<abstract>
<para/>
</abstract>
</merge>
<module resourceref="_pcp-start-onboot" renderas="section">
<merge>
<abstract>
<para/>
</abstract>
</merge>
</module>
</module>
<module resourceref="_pcp-service-configuration" renderas="section">
<merge>
<abstract>
<para/>
</abstract>
</merge>
</module>
<module renderas="section">
<merge>
<title>Managing PCP metrics</title>
<abstract>
<para/>
</abstract>
</merge>
<module resourceref="_pcp-listing-metrics" renderas="section">
<merge>
<abstract>
<para/>
</abstract>
</merge>
</module>
<module resourceref="_pcp-checking-metrics" renderas="section">
<merge>
<abstract>
<para/>
</abstract>
</merge>
</module>
<module resourceref="_pcp-recording-metrics" renderas="section">
<merge>
<abstract>
<para/>
</abstract>
</merge>
</module>
</module>
<module resourceref="_legal"/>
<module resourceref="_gfdl">
<output renderas="appendix"/>
</module>
</structure>
</assembly>