보고서 생성
SUSE Multi-Linux Manager를 사용하면 사용자가 다양한 보고서를 생성할 수 있습니다. 이 보고서는 가입한 시스템, 사용자 및 조직의 인벤토리를 작성할 때 유용하게 사용할 수 있습니다. 특히, 관리 중인 시스템이 많은 경우 보고서를 사용하는 방식이 SUSE Multi-Linux Manager Web UI에서 정보를 수동으로 수집하는 방식보다 더 간단합니다.
While the command line tool spacewalk-report can be used to generate pre-configured reports, with the introduction of the Reporting Database it is also possible to generate fully customized reports. This can be achieved by connecting any reporting tool that supports the SQL language to the reporting database and extract the data directly. For more information about the data availability and structure, see the reporting database schema documentation.
1. Using spacewalk-report
|
Use |
To generate reports, you must have the spacewalk-reports package installed. The spacewalk-report command allows you to organize and display reports about content, systems, and user resources across SUSE Multi-Linux Manager.
|
Due to the introduction of the Reporting Database, |
다음에 대한 보고서 생성 가능:
- 시스템 인벤토리
-
SUSE Multi-Linux Manager에 등록된 모든 시스템을 나열합니다.
- 패치
-
등록된 시스템과 관련된 모든 패치를 나열합니다. 패치를 심각도별로 정렬할 수 있을 뿐만 아니라 특정 패치에 적용되는 시스템도 정렬할 수 있습니다.
- 사용자
-
등록된 모든 사용자 및 특정 사용자와 관련된 모든 시스템을 나열합니다.
보고서를 CSV 형식으로 가져오려면 서버의 명령 프롬프트에서 다음 명령을 실행합니다.
spacewalk-report <report_name>
2. spacewalk-report and the reporting database
spacewalk-report uses by default the new reporting database to extract the data. This means that the new generated reports will have some differences in the structure and the format of the data. The differences common to all reports are:
-
보고서 데이터는 실시간으로 변경되지 않고 예약된 작업을 실행하는 방식으로만 업데이트됩니다.
-
data duplication has been removed and columns that were previously considered "multival" contain now multiple values separated by
;. This also means that the command line options--multival-on-rowsand--multival-separatorare no longer applicable to the new reports, as their behavior is now the default; -
in all reports the new columns
mgm_idandsynced_datehave been introduced to identify the management server in the hub scenario and the last time the information was updated from the application database; -
all boolean values are now represented by the
True/Falseand not by a1/0values; -
the column
org_idhas been replaced byorganization, which contains the organization name and not the numerical identifier; -
The term "server" has been replaced by "system." So, for example, the column
server_idis now calledsystem_id.
구체적인 보고서 변경사항은 사용할 수 있는 보고서 목록을 참조하십시오.
|
If this changed behavior causes trouble, the new option |
For more information about the reporting database, see Reporting Database. For hub-specific aggregation of data from multiple servers, see Hub Reporting.
3. 사용할 수 있는 보고서 목록
이 테이블은 사용할 수 있는 보고서를 보여줍니다.
| Report | Invoked as | Description | Uses reporting database | Specific differences |
|---|---|---|---|---|
Actions |
|
All actions. |
Yes |
The column |
Activation Keys |
|
All activation keys, and the entitlements, channels, configuration channels, system groups, and packages associated with them. |
No |
|
Activation Keys: Channels |
|
All activation keys and the entities associated with each key. |
No |
|
Activation Keys: Configuration |
|
All activation keys and the configuration channels associated with each key. |
No |
|
Activation Keys: Server Groups |
|
All activation keys and the system groups associated with each key. |
No |
|
Activation Keys: Packages |
|
All activation keys and the packages each key can deploy. |
No |
|
Channel Packages |
|
All packages in a channel. |
Yes |
|
Channel Report |
|
Detailed report of a given channel. |
Yes |
|
Cloned Channel Report |
|
Detailed report of cloned channels. |
Yes |
|
Configuration Files |
|
All configuration file revisions for all organizations, including file contents and file information. |
No |
|
Latest Configuration Files |
|
The most recent configuration file revisions for all organizations, including file contents and file information. |
No |
|
Custom Channels |
|
Channel metadata for all channels owned by specific organizations. |
Yes |
The column |
Custom Info |
|
Client custom information. |
Yes |
|
Patches in Channels |
|
All patches in channels. |
Yes |
|
Patches Details |
|
All patches that affect registered clients. |
Yes |
|
All patches |
|
All patches. |
No |
|
Patches for Clients |
|
Applicable patches and any registered clients that are affected. |
Yes |
|
Host Guests |
|
Host and guests mapping. |
Yes |
|
Inactive Clients |
|
Inactive clients. |
Yes |
The mandatory parameter is now called |
System Inventory |
|
Clients registered to the server, together with hardware and software information. |
Yes |
The column |
Kickstart Scripts |
|
All kickstart scripts, with details. |
No |
|
Kickstart Trees |
|
Kickstartable trees. |
No |
" |
All Upgradable Versions |
|
All newer package versions that can be upgraded. |
Yes |
|
Newest Upgradable Version |
|
Newest package versions that can be upgraded. |
Yes |
|
Proxy Overview |
|
All proxies and the clients registered to each. |
Yes |
|
Repositories |
|
All repositories, with their associated SSL details, and any filters. |
No |
|
Result of SCAP |
|
Result of OpenSCAP |
Yes |
|
Result of SCAP |
|
Result of OpenSCAP |
Yes |
|
System Data |
|
Client data needed for splice integration. |
No |
|
System Currency |
|
Number of available patches for each registered client. |
No |
|
System Extra Packages |
|
All packages installed on all clients that are not available from channels the client is subscribed to. |
Yes |
|
System Groups |
|
System groups. |
Yes |
|
System Hardware |
|
System hardware information. |
No |
|
Activation Keys for System Groups |
|
Activation keys for system groups. |
No |
|
Systems in System Groups |
|
Clients in system groups. |
Yes |
|
System Groups Users |
|
System groups and users that have permissions on them. |
No |
|
History: System |
|
Event history for each client. |
Yes |
|
History: Channels |
|
Channel event history. |
Yes |
|
History: Configuration |
|
Configuration event history. |
Yes |
The column |
History: Entitlements |
|
System entitlement event history. |
Yes |
|
History: Errata |
|
Errata event history. |
Yes |
The column |
History: Kickstart |
|
Kickstart event history. |
Yes |
The column |
History: Packages |
|
Package event history. |
Yes |
The column |
History: SCAP |
|
OpenSCAP event history. |
Yes |
The column |
MD5 Certificates |
|
All registered clients using certificates with an MD5 checksum. |
No |
|
Installed Packages |
|
Packages installed on clients. |
Yes |
|
System Profiles |
|
All clients registered to the server, with software and system group information. |
No |
|
Users |
|
All users registered to SUSE Multi-Linux Manager. |
Yes |
The column |
MD5 Users |
|
All users for all organizations using MD5 encrypted passwords, with their details and roles. |
Yes |
The column |
Systems administered |
|
Clients that individual users can administer. |
Yes |
The column |
For more information about an individual report, run spacewalk-report with the option --info or --list-fields-info and the report name. This shows the description and list of possible fields in the report.
For further information on program invocation and options, see the spacewalk-report(8) man page as well as the --help parameter of the spacewalk-report command.