THE GITOPS GUIDE TO BUILDING & MANAGING INTERNAL PLATFORMS
THE GITOPS GUIDE TO BUILDING & MANAGING INTERNAL PLATFORMS weave.works 2 THE GITOPS GUIDE TO BUILDING & MANAGING INTERNAL PLATFORMS Internal platforms are a great way to enable an outstanding code. The way to foster an outstanding developer experience is to leverage the internal platform approach. An internal platform helps to get resources to developers on-demand and in a secure way. FAANG In this paper, we look at how an internal platform serves to deliver an outstanding developer experience. Further, we look at how GitOps is the way to build internal platforms at scale. With these key0 码力 | 15 页 | 623.52 KB | 1 年前3SQLite Development with Zumero
ACL .................................................................................... 22 7.3. Internal Auth .......................................................................................... ..................... 33 10.1.3. zumero_internal_auth_create() ................................................................... 34 10.1.4. zumero_internal_auth_add_user() ........................ ...................... 35 10.1.5. zumero_internal_auth_add_alias() ............................................................... 35 10.1.6. zumero_internal_auth_set_password() .....................0 码力 | 57 页 | 199.89 KB | 1 年前3Flashcat 让监控分析变简单,Flashcat产品技术交流
北京快猫星云科技有限公司 Flashcat 产品技术交流 让监控分析变简单 INTERNAL OR RESTRICTED, ALL RIGHTS RESERVED © 北京快猫星云科技有限公司 由知名开源项⽬“夜莺”的核⼼开发团队组成: 夜莺是⼀款开源云原⽣监控⼯具,是中国计算机学会接受捐赠并托管的 第⼀个开源项⽬,在GitHub上有超过8500颗星,上百位社区贡献者, 上万家企业⽤户,是国内领先的开源可观测性解决⽅案。 由国内顶级投资机构连续投资。 INTERNAL OR RESTRICTED, ALL RIGHTS RESERVED © 北京快猫星云科技有限公司 快猫星云是国内开源监控领域最具专业性的团队之⼀ INTERNAL OR RESTRICTED, ALL RIGHTS RESERVED © 北京快猫星云科技有限公司 Flashcat 是什么 INTERNAL OR RESTRICTED, ALL ALL RIGHTS RESERVED © 北京快猫星云科技有限公司 Flashcat 构建了⼀个数据、平台、场景打通的⼀体化⽅案 INTERNAL OR RESTRICTED, ALL RIGHTS RESERVED © 北京快猫星云科技有限公司 Flashcat 的特点 统⼀采集 采⽤插件化思路,内置集成上百种采集插件,服务器、⽹络设备、中间件、数据库、应⽤、业务,云上 云下,均可监控,开箱即⽤。0 码力 | 43 页 | 6.54 MB | 1 年前3Apache OFBiz User Manual
Overview The main page on OFBiz Setup application including 2 sections, following this: 7 Available Internal Organizations Section This section shows list of organizations which store in the system. You be enter the 'Product Id' field it will be used the default as 'Organization Party Id') 3. Enter the 'Internal Name' field 4. Enter the 'Product Name' field 11 5. Enter a description describing what the category will be displayed in the box 3. Amend the details in the line item that needs to be updated (eg Internal Name, Product Name, Short Description, Default Price, Average Cost) 4. Press the 'Update' button0 码力 | 307 页 | 5.64 MB | 1 年前3Apache OFBiz User Manual
Overview The main page on OFBiz Setup application including 2 sections, following this: 7 Available Internal Organizations Section This section shows list of organizations which store in the system. You be enter the 'Product Id' field it will be used the default as 'Organization Party Id') 3. Enter the 'Internal Name' field 4. Enter the 'Product Name' field 11 5. Enter a description describing what the category will be displayed in the box 3. Amend the details in the line item that needs to be updated (eg Internal Name, Product Name, Short Description, Default Price, Average Cost) 4. Press the 'Update' button0 码力 | 304 页 | 5.21 MB | 1 年前3Zabbix 4.0 Manual
preprocessing : ok, master, err, slave. • zabbix[rcache,, ] and zabbix[wcache, , ] internal items now support a pused mode, returning the use percentage of the respective buffer. JMX monitoring downtime. Configurable session cookie name The session cookie name that Zabbix frontend uses for internal authentication is now configurable in ZBX_SESSION_NAME of the frontend definitions. Host column historical problem names. However, the size of problem/events tables is now larger. Note that for internal events the name contains an error message why an object changed its state; upon recovery no name 0 码力 | 1365 页 | 16.69 MB | 1 年前3QCon北京2017/企业软件互联网应用实践/基于 kubernetes 的企业级容器云
2 2016 Lenovo Internal. All rights reserved. 3 2017 Lenovo Internal. All rights reserved. 大纲 • 背景和挑战 • 企业级容器云设计与思考 • 让一切自动化 • 监控与日志 • Showcase • 那些坑,那些事 4 2017 Lenovo Internal. All rights reserved 缺少标准和规范 5 2017 Lenovo Internal. All rights reserved. 背景和挑战 • 内部系统演进 每个项目自维护 难以规范和升级 01 脚本化 多个工具集成 最佳搭配 合力作战 03 平台化 抽象成工具 模板化 一键化 零散,不成体系 02 工具化 6 2017 Lenovo Internal. All rights reserved. 规范落地困难 系统分散,难以统一 自服务平台 高效协作,加速迭代 7 2017 Lenovo Internal. All rights reserved. 背景和挑战 • 容器之道 加速 交付 统一 规范 构建 平台 节约 资源 8 2017 Lenovo Internal. All rights reserved. 企业级容器云设计与思考 • 设计思路 从需求出发 需求驱动,勿求大而全,没有银弹0 码力 | 30 页 | 1.80 MB | 1 年前3Zabbix 3.0 Manual
host states by default: *0 not available *1 available *2 unknown and matches the value of internal check item zabbix[host,,available]. 5.19.10 Miscellaneous improvements • Value mappings per day. The current operational mode can be checked with zabbix[vcache,cache,mode] key. See the internal check documentation. 5.20.5 Zabbix agent crash log on Windows platforms Zabbix agent will now been removed together with internal items used to monitor it. History index cache has been added to keep index of the history cache. A new zabbix[wcache,index, ] internal check was added to monitor 0 码力 | 1074 页 | 12.04 MB | 1 年前3Zabbix 3.4 Manual
older) proxies, keeping partial backwards compatibility. • The default data storage period for internal, discovery and agent auto-registration events has been decreased from 365 days to 1 day. • Maximum time during configuration synchronization has been reduced. • To allow internal checks to be processed prior to other items, internal check items are now enqueued at the beginning of the preprocessing queue been added to Zabbix server and proxy configurations. This parameter points to the directory where internal Zabbix socket files are stored (/tmp by default). Server and proxy uses different socket file names0 码力 | 1136 页 | 15.03 MB | 1 年前3Zabbix 3.2 Manual
this development: • ”Trigger value” conditions for trigger events • ”Event type” conditions for internal events - Item in “normal” state, Low-level discovery rule in “normal” state, Trigger in “normal” automatically are: • Recovery messages are moved to recovery operations; 67 • All trigger-based and internal actions having ’Or’ or ’Custom expression’ calculation type are disabled; • Trigger-based actions handle OK events only, but have a recovery message or more than one escalation step are disabled; • Internal actions that could handle any other event except those corresponding a single Item in “not supported”0 码力 | 1012 页 | 12.11 MB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100