Employees – Employees List

Ini adalah paparan Employees List yang terdapat dalam module Employees di System Urusniaga. Fungsi senarai pekerja ini memaparkan butiran setiap pekerja daripada semua syarikat di dalam sistem. Butiran seperti nama syarikat, status pekerja, nombor pekerja, nama pekerja, telefon dan e-mel akan ditunjukkan dan boleh disunting serta dipadam.

Anda juga dibenarkan untuk menambah pekerja baru dengan memasukkan maklumat seperti nama syarikat, pengguna sistem, nombor pekerja, tarikh kemasukan, gaji pokok, status dan penerangan. — sila cuba dengan gembira https://urusniaga.my

Read more at: https://urusniagasme.wordpress.com/

Maintenance – Backup / Restore

Ini adalah paparan Backup/Restore yang terdapat dalam module Maintenance di System Urusniaga. Fungsi backup/restore ini membolahkan Anda mencipta fail backup untuk menyimpan data sistem ke dalam fail dengan memasukkan nama fail dan penerangan.

Fail backup akan dicipta dengan format yang telah ditetapkan secara automatik. Selain itu, Anda juga boleh memuat naik fail backup untuk restore ke dalam sistem dengan memuat naik fail dan memasukkan penerangan jika perlu. Sistem hanya menyimpan maksimum 5 fail backup sahaja. — sila cuba dengan gembira https://urusniaga.my

Read more at: https://urusniagasme.wordpress.com/

Expenses Type

Ini adalah paparan Expenses Type yang terdapat dalam module Purchases di System Urusniaga. Fungsi jenis perbelanjaan membenarkan Anda untuk menambah rekod perbelanjaan dan memasukkan jenis perbelanjaan yang telah dikeluarkan. Jenis perbelanjaan boleh ditambah dengan melengkapkan maklumat seperti nama jenis perbelanjaan dan penerangan. Selain itu, jenis perbelanjaan juga boleh disunting dan dipadam. — sila cuba dengan gembira https://urusniaga.my

Read more at: https://urusniagasme.wordpress.com/

Template – Document Note

Ini adalah paparan Document Note yang terdapat dalam module Template di System Urusniaga. Dengan Document Note ini Anda boleh menyediakan nota di setiap dokumen seperti jualan, pembelian, pembelajaan dan lain-lain lagi. Nota yang ditetapkan akan terus dijana bersama dokumen yang dipilih. Sebagai contoh, nota berkenaan memberitahu info akaun bank syarikat anda bagi pembayaran yang akan dijana di dokumen jualan invoice dengan ada nota ini akan memudahkan pelanggan tahu info pembayaran dan menjimatkan masa setiap kali anda menjana sebarang dokumen. — sila cuba dengan gembira https://urusniaga.my

system-urusniaga-document-note

 

Read more at: https://urusniagasme.wordpress.com/

System Urusniaga – My Calender

Ini adalah paparan My Calender yang terdapat dalam module Calender di System Urusniaga. Di My Calender ini anda boleh memasukkan catatan atau nota sebagai peringatan ke dalam kalendar. Kalendar peribadi ini hanya boleh diakses oleh individu yang log masuk ke akaun tersebut. Untuk menambah acara ke dalam kalendar, Anda perlu memasukkan tarikh, jenis kalendar sama ada peribadi atau kongsian dan penerangan. — sila cuba dengan gembira https://urusniaga.my

system-urusniaga-calender

Read more at: https://urusniagasme.wordpress.com/

System Urusniaga – User list

Ini adalah paparan User list yang terdapat dalam module Users di System Urusniaga. Di user list ini anda boleh menguruskan dan menambah pengguna sistem dengan mudah, setiap pengguna yang di tambah anda boleh memberikan pelbagai syarikat untuk di akses. Data penting yang boleh disimpan seperti nama pengguna, e-mel, katalaluan, nama penuh, peranan, muat-naik gambar profile, alamat dan lain-lain lagi. — sila cuba dengan gembira https://urusniaga.my

Read more at: https://urusniagasme.wordpress.com/

System Urusniaga – Sales Update button Action

System Urusniaga di module Sales telah dikemaskini mempunyai fungsi membolehkan anda menukar semua dokumen jualan yang berstatus overdue kepada cancel, anda boleh mencubanya di Sales order, Quotation dan Invoice dengan klik pada butang ‘More’>pilih Action dan panel action akan dipaparkan disebelah kiri. — sila cuba dengan gembira https://urusniaga.my

system-urusniaga-sales-updates-actions

Read more at: https://urusniagasme.wordpress.com/

Does Percona Monitoring and Management (PMM) Support External Monitoring Services? Yes It Does!

External Monitoring Services

Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL and MongoDB performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL and MongoDB servers to ensure that your data works as efficiently as possible.

Starting with version 1.4.0 and improved in 1.7.0, PMM supports external monitoring services. This means you can plug in Prometheus exporters for technologies not directly provided by Percona. For example, you can start monitoring the metrics of your PostgreSQL database host, Memcached or Redis.

Exporters Overview

Applications store their metrics in arbitrary formats, and Prometheus exporters collect them and produce (or export to) a consistent format of key-value pairs. The keys refer to metric types and values are numbers in the float 64 format. Due to the diversity of formats that applications may use, you should program a specific exporter for each format. However, if you decide to make the metrics of your application available via PMM you may consider using one of existing Prometheus exporters.

Currently, PMM offers exporters for MySQL (mysqld_exporter) and MongoDB (mongodb_exporter) database management systems. Built-in exporters also exist for Percona XtraDBCluster, MariaDB, RDS and Aurora via mysqld_exporter and for ProxySQL (via proxysql_exporter). These exporters are made available as monitoring services that you can add or remove as necessary. In addition, PMM includes the node_exporter to capture the host level Linux metrics such as CPU, Load, and disk resources.

Using Exporters

On the computer where the PMM client is installed and connected to a PMM server, make use of the pmm-admin utility to add any built-in monitoring service directly. There is no extra effort in this case: the added monitoring service will run its exporter and all required configuration updates are made automatically to make the metrics available in the web interface for further analysis in Query analytics and Metrics monitor.

In case of external monitoring services, you need to locate, download, set up and run the specific Prometheus exporter to collect metrics. When it is ready, you can add it as a monitoring service:

pmm-admin add external:service job_name [instance] --service-port=PORT_NUMBER

This command adds an external monitoring service bound to the Prometheus job that you specify as the job_name parameter. You should also provide the port associated with this Prometheus job as the value of the service-port parameter. The instance parameter is optional. By default, it is assigned the name of the host where you run pmm-admin.

Example 1: Adding a PostgreSQL Monitoring Service

In order to add an external monitoring service for a PostgreSQL database server, make sure to install and configure your PostgreSQL server. Then, select a PostgreSQL Prometheus exporter from the list available from the  Prometheus site, such as PostgreSQL metric exporter for Prometheus. Refer to the documentation for this exporter for details about how to install and set it up.

As soon as your Prometheus exporter can collect metrics from your PostgreSQL database server,  you are ready to add this exporter as a monitoring service. Make sure that you have access to a configured PMM server and your PMM client has been set up to use it. Use the pmm-admin utility, which is part of PMM client, to add the PostgreSQL monitoring service. Assuming postgresql is the name of this monitoring service, your command should look like this:

pmm-admin add external:service --service-port=PORT_NUMBER postgresql

It is time now to display the metrics on the PMM Server. Open Metrics Monitor and check the Advanced Data Exploration dashboard. This can dashboard visualize a lot of metrics including those exposed by external monitoring services. In the Host field select your host. Use the Metric field to select a metric.

External Monitoring Services
Viewing a metric exposed by a PostgreSQL exporter.

Setting up an external monitoring service requires extra work compared to adding built-in monitoring services. However, by using external monitoring services you can considerably extend the capabilities of your PMM installation.

Note that running the pmm-admin list command lists the added external monitoring services. They also appear in the JSON output, too. To remove an external service use the remove (or its short form rm) command:

pmm-admin rm external:service --service-port=PORT_NUMBER NAME_OF_EXTERNAL_MONITORING_SERVICE

$ sudo pmm-admin list
pmm-admin 1.7.0
PMM Server      | 192.0.2.2 (password-protected)
Client Name     | postgres01
Client Address  | 192.0.2.3
Service Manager | unix-systemv
Job name    Scrape interval  Scrape timeout  Metrics path  Scheme  Target         Labels                   Health
postgresql  1s               1s              /metrics      http    192.0.2.3:9187 instance="postgres01"      UP

Example 2: Adding a Redis Monitoring Service

To start with, you must install a Prometheus exporter for Redis (this exporter is listed on the Prometheus Exporters and Integrations page) on the machine where your PMM client runs. The following command adds this exporter as an external monitoring service (run it as a superuser or use sudo). This time the command has an extra parameter:

$ sudo pmm-admin add external:service redis --service-port 9121 redis01
External service added.

Notice that we use Redis Server as the last parameter passed to pmm-admin add external:service command. The last positional parameter is a label that you assign to this particular instance.

pmm-admin add external:service --service-port=PORT_NUMBER NAME_OF_EXTERNAL_MONITORING_SERVICE [INSTANCE_LABEL]

You may choose any name for this purpose. Make sure to use quotes if you decide to use a label made of two or more words.

$ sudo pmm-admin list
pmm-admin 1.7.0
PMM Server | 127.0.0.1
Client Name | percona
Client Address | 172.17.0.1
Service Manager | linux-systemd
No services under monitoring.
Job name Scrape interval Scrape timeout Metrics path Scheme Target          Labels                  Health
redis    1m0s            10s            /metrics     http   172.17.0.1:9121 instance="redis01"      UP

To view Redis related metrics you need to open the Advanced Data Exploration dashboard on your PMM Server. The redis01 label automatically appears in the Host field in the Advanced Data Exploration dashboard. In the Host field, select the redis01 option and choose a metric to view from the Metric field, such as redis_exporter_scrapes_total.

Other Ways to Add External Services

The pmm-admin add external:service command is the recommended way to add an external monitoring service. There exist other, more specific, methods. The pmm-admin add external:metrics adds external Prometheus exporters job to metrics monitoring.

Read more at: //www.mysqlperformanceblog.com/

Webinar Thursday, February 15, 2018: Basic Internal Troubleshooting Tools for MySQL Server

Troubleshooting Tools for MySQL

Troubleshooting Tools for MySQLPlease join Percona’s Principal Support Engineer, Sveta Smirnova, as she presents “Basic Internal Troubleshooting Tools for MySQL Server” on Thursday, February 15, 2018, at 10:00 am PST (UTC-8) / 1:00 pm EST (UTC-5).

 

MySQL Server has many built-in troubleshooting tools. They are always available and can provide many insights on what is happening internally. Many graphical tools, such as Percona Monitoring and Management (PMM), use built-ins to get data for their nice graphs.

Even if you are only going to use graphical tools, it is always good to know what data they can collect. This way, you can see their limitations and won’t have incorrect expectations in the heat of battle. Built-in troubleshooting tools are accessible via SQL commands. Most of them are standard across the server, but details are component-specific.

In this webinar, I will discuss how to use them, how to troubleshoot component-specific issues and how to find additional information. I will cover SHOW commands, Information Schema, status variables and few component-specific syntaxes. I will NOT cover Performance Schema (there will be a separate webinar on that), and I will use PMM graphs to illustrate the topics whenever possible.

Register for the Basic Internal Troubleshooting Tools for MySQL Server webinar now.

Internal Troubleshooting for MySQLSveta Smirnova, Principal Technical Services Engineer

Sveta joined Percona in 2015. Her main professional interests are problem-solving, working with tricky issues, bugs, finding patterns that can solve typical issues quicker. She likes teaching others how to deal with MySQL issues, bugs and gotchas effectively. Before joining Percona Sveta worked as Support Engineer in MySQL Bugs Analysis Support Group in MySQL AB-Sun-Oracle. She is the author of book “MySQL Troubleshooting” and JSON UDF functions for MySQL.

Read more at: //www.mysqlperformanceblog.com/