Go to file
openharmony_ci 675a8764b8
!2485 适配setuid
Merge pull request !2485 from 曹小刚/OpenHarmony-5.0.1-Release
2024-11-21 02:47:13 +00:00
adapter fix 2024-10-28 15:47:59 +08:00
base fix UT 2024-11-07 17:45:31 +08:00
build dft plugins to so 2024-05-05 16:16:18 +08:00
core !2358 提升用例分支覆盖率 2024-10-17 08:08:07 +00:00
figures hiview_zh.md 2022-01-20 14:55:13 +08:00
framework/native/unified_collection bug: fix the problem that traces are repeatedly compressed and copied 2024-10-30 09:28:07 +08:00
hisysevent cherry pick 3a21850 from https://gitee.com/lyj_love_code/hiviewdfx_hiview/pulls/2073 2024-10-17 03:02:32 +00:00
interfaces bug: sync code from master 2024-10-24 15:37:12 +08:00
plugins Description:fix asan logpath is wrong in ide 2024-11-12 12:47:22 +00:00
service 增加setuid配置 2024-11-20 10:06:43 +08:00
test Merge branch 'OpenHarmony-5.0-Release' of gitee.com:openharmony/hiviewdfx_hiview into OpenHarmony-5.0-Release 2024-09-07 02:01:18 +00:00
utility code sync 2024-10-28 20:03:26 +08:00
.gitattributes update OpenHarmony 2.0 Canary 2021-06-02 02:18:59 +08:00
.gitignore bug: sync code 2024-09-03 12:03:26 +08:00
BUILD.gn rename xperf 2024-08-01 15:30:48 +08:00
bundle.json delete 2024-09-06 14:32:53 +08:00
CODEOWNERS adapt the ipc code of HivewService and SysEventService 2023-07-01 11:48:14 +08:00
hisysevent.yaml hiview match crash event 2024-03-17 14:16:05 +08:00
hiview_zh.md CodeClear 2024-01-17 11:23:12 +08:00
hiview.gni Synchronize code 2024-10-12 19:36:25 +08:00
kernel_vendor.yaml add hisysevent xpower kernel tag 2023-05-31 11:54:40 +08:00
LICENSE update OpenHarmony 2.0 Canary 2021-06-02 02:18:59 +08:00
main.cpp 重命名logger.h 2024-04-18 15:47:55 +08:00
OAT.xml !1960 同步差异 2024-07-11 11:01:51 +00:00
README_zh.md add innerkit for hiviewbase 2023-06-30 17:10:13 +08:00
README.md add innerkit for hiviewbase 2023-06-30 17:10:13 +08:00

Hiview

Introduction

Hiview is the module of OpenHarmony that provides toolkits for device maintenance across different platforms.

Currently, Hiview opens only the plug-in management platform and system event source capabilities.

Figure 1 Architecture of Hiview

Hiview consists of the following components:

adapter: operating system adaptation layer, which adapts APIs of the system services in use

hiview base: Hiview base definition, which provides the plug-in definition, detector definition, and utility class

hiview core: Hiview core module, which provides the plug-in configuration, plug-in management, and event source functions

hiview services: Hiview services. Currently, only the Hiview run information exporting function is provided.

plugins: Independent service modules.

Hiview works in event-driven mode. The core of Hiview is a collection of HiSysEvent stubs distributed in the system.

Formatted events are reported to Hiview through the HiSysEvent API for processing. Figure 2 shows the data interaction process.

Figure 2 Data interaction between Hiview modules

  1. The application framework and system services report system events using the HiSysEvent API.

  2. HiSysEventSource reads events and prints the events to logs.

Directory Structure

The code directory structure of Hiview is as follows:

/base/hiviewdfx/hiview
├── adapter             # Platform adaptation code
│   └── service        # Service adaptation code
├── base                # Module definition and utility class
│   └── utility
├── build               # Compilation scripts
├── include             # Common definitions
├── core                # Plug-in management
└── service             # Platform services

Constraints

Use of C++14 features requires libc of C++14 or later.

Contribution

If you are interested in Hiview and want to become a contributor, refer to the Code Contribution Guide.

Usage

Hiview automatically starts with the device and loads plug-ins based on the configuration file.

Repositories Involved

DFX subsystem

hiviewdfx_hiview

hiviewdfx_hilog

hiviewdfx_hiappevent

hiviewdfx_hisysevent

hiviewdfx_faultloggerd

hiviewdfx_hilog_lite

hiviewdfx_hievent_lite

hiviewdfx_hiview_lite