Artifacts (Dashboards/Alerts) catalog (service)
- Abhishek Chaturvedi (Unlicensed)
- Swapnil Kulkarni
- Ayan Shah
- Pankaj Thakkar
- 1 Overview
- 1.1 Explore/Install through the Kloudfuse artifacts catalog
- 1.2 Migrating artifacts from other platforms
- 1.2.1 Migrating from grafana
- 1.2.1.1 Download from existing
- 1.2.1.2 Upload to Kloudfuse
- 1.2.2 Manually uploading artifacts (dashboards/alerts) to Kloudfuse
- 1.2.2.1 Download from existing
- 1.2.2.2 Upload to Kloudfuse
- 1.2.1 Migrating from grafana
- 2 Caveats
Overview
The Kloudfuse platform comes with catalog service which aims to provide following functionalities for ease of use/onboarding.
It presents ready-to-use artifacts (dashboards or alerts) for several commonly used software components (Postgres, Redis, Mongo, Kafka, K8s, Apache Pinot, etc. etc.) towards the “works out of the box” experience. These artifacts can be deployed directly into your environment through the catalog service. Learn more here.
The catalog service is also aimed at providing simpler migration of artifacts from other source platforms to kloudfuse platform. Learn more here.
Explore/Install through the Kloudfuse artifacts catalog
The UI for consuming (listing/exploring/installing) these artifacts is coming in an upcoming version. However, the users can use these easy-to-follow instructions to do the same by using a CLI. The CLI is available as part of the catalog-service which runs as a service within the kloudfuse installed stack. The steps are as follows:
Logging into the catalog service
# make sure you are connected to the kfuse k8s cluster and in the kfuse namespace
kubectx <your-kfuse-cluster>
kubens kfuse
kubectl exec -it catalog-service-<...> -- bashUsage
# Make sure to understand the usage.
# cd /catalog_service
python3 catalog.py -h
usage: catalog.py [-h] [--artifact_type {dashboards,alerts,contactpoints}] [--explore] [--list [LIST]] [--detailed] [--install] [--download_installed] [--grafana_address GRAFANA_ADDRESS] [--grafana_username GRAFANA_USERNAME]
[--grafana_password GRAFANA_PASSWORD] [-c CONFIG] [--no_upload]
catalog service
options:
-h, --help show this help message and exit
--artifact_type {dashboards,alerts,contactpoints}
which artifact type you want to work with
--explore explore the catalog, making selections, and finally installing chosen artifacts to grafana
--list [LIST] list all the components for which artifacts are available. if list of comma separated components are provided, then those are used
--detailed show detailed list (only honored with --list option)
--install directly installs artifacts of specified type as per --list option without exploring/prompting
--download_installed download already installed artifacts from provided grafana instance or from the grafana in the cluster context
--grafana_address GRAFANA_ADDRESS
grafana server address. optional, default is http://kfuse-grafana:80)
--grafana_username GRAFANA_USERNAME
grafana username. optional, if not provided, it is taken from environment
--grafana_password GRAFANA_PASSWORD
grafana user password. taken from the environment
-c CONFIG, --config CONFIG
Config file containing settings for install if selectivity is needed
--no_upload just process artifacts but do not upload List artifacts (optionally, of a given type)
# To list all artifacts in the catalog
python3 catalog.py
{'kafka': {'dashboards': {'count': 1}},
'kubernetes': {'alerts': {'count': 1}, 'dashboards': {'count': 5}},
'sock-shop': {'dashboards': {'count': 1}}}
# To list only alerts in the catalog
python3 catalog.py --artifact_type=alerts
{'kafka': {}, 'kubernetes': {'alerts': {'count': 1}}, 'sock-shop': {}}Explore artifacts (optionally, of a given type)
Install kubernetes artifacts
Install all artifacts
Install out of the box Kloudfuse artifacts
Migrating artifacts from other platforms
Migrating from grafana
Download from existing
connect to kfuse cluster and log into the catalog service pod
Download existing artifacts (alerts in the following example) from source grafana instance using the catalog script (check usage with
-hfor more options), appropriately specifying arguments (be sure that the catalog service pod can reach the source grafana address):
Upload to Kloudfuse
The above step will download the artifacts to
/tmp/<artifact_type>_downloadsdirectory. Use following command to explore and install these artifacts into the kfuse embedded grafana.
Note/Limitation: If uploading directory, make sure the your alerts are in directory structure like /tmp/alerts_downloads/assests/<any_folder_name>/alerts/ and then use the below command, other you may not see any alerts to select from.
Note: If these commands can’t be executed from pod due to <target-cluster-addr> reachability, you can use following instructions to extract the catalog tool used above to a location where <target-cluster-addr> can be reached:
Manually uploading artifacts (dashboards/alerts) to Kloudfuse
Download from existing
Ensure you’ve downloaded the alerts/dashboards in json format to be uploaded to Kloudfuse and are available in the catalog-service pod. You can connect to catalog service pod with above instructions
Upload to Kloudfuse
Create a directory structure as follows in your <<download_directory>>
For alerts mkdir -p <<download_directory>>/assets/upload/alertsFor dashboards mkdir -p <<download_directory>>/assets/upload/dashboards
Copy the alerts and/or dashboards to respective directories. Use following command to explore and install these artifacts into the kfuse embedded grafana.
Caveats
the artifacts that are installed using the catalog are considered to be “staged” for the user to tweak as needed. This, ideally, shouldn’t be considered as the final destination of how users should manage their artifacts and their life-cycle (as code) as each organization has their own way of managing these. The user should ideally move these to other folders as desired and then use their life-cycle management workflows from there.
if artifacts with same name in the same folder are already installed (found), the catalog will NOT overwrite them and will skip them by default. If users need to update their installed artifacts, then they should first delete the existing artifacts. Also, a sample config.yaml file is provided which can be used to control how artifacts are merged (applies to alerts only for now).