TypeScript

A Svelte component library for Obsidian development.

A series of tutorials where I walk through different aspects of plugin development for Obsidian.

An Obsidian plugins that lets you manage and visualize notes for project management.

In Data frame design: Basics, I stressed the importance to document the data response that your panel plugin expects from the data source. While you can document it in your README, that would mean the user needs to switch to another tab to understand how to use your panel. In this post, I’ll share a different approach, that lets the user configure the query without leaving Grafana.

Template variables enable users to create dashboards that change dynamically based on user input. Since variables have been around in Grafana for a long time, many users expect them to be supported for any data sources they install. In this post, I’ll share some tips on how you can use template variables in your data source plugin.

An unofficial Grafana data source for You Need A Budget.

If your data source retrieves data from an official, well-defined API, you can simplify your data source configuration by only asking for the relevant data, such as the API token. However, if the user should be able to access data from any given HTTP endpoint, you probably want to let them configure things like authentication headers and query parameters to fit their needs. In this post, I’ll explain how you can build a configurable HTTP-based backend data source.

In this post, I want to share a pattern that I’m using for almost all my panel plugins. I call it panel dimensions.

If you’re building a data source plugin, chances are you want to make HTTP requests from your TypeScript code to a HTTP API somewhere. In the past, the preferred way to make an HTTP request from your plugin was to use the BackendSrv.datasourceRequest(), which has been deprecated in favor of BackendSrv.fetch().

If you’re building a panel plugin, Grafana already provides the data you need to configure and render your panel. If not, you can retrieve the information you need from any of the runtime services, like BackendSrv and TemplateSrv. In some cases though, you want your plugin to react to changes outside of your plugin. For example, when the user hovers their cursor over data in another panel. In this post, you’ll learn how to make your plugin react to events in Grafana.

An Obsidian plugin that adds pipe tricks to the Wikilink format used by Obsidian

Generate Markdown from a .d.ts file.

A Vale client for Obsidian.

This repository contains various helper functions that I’ve found myself reimplementing for my plugins.

Display your query results as calendar events.

A panel plugin for Grafana to visualize Gantt charts.

A Grafana panel plugin for hexagonal tiling of data.

Load CSV files into Grafana.

A data source plugin for loading JSON APIs into Grafana using JSONPath or JSONata.

Define text templates using the data from your data source query.

Plugins amplify what you can do with Grafana. By creating your own custom visualizations and data source integrations you can bring in your own data and present it in a way that makes sense for you. In this webinar, Solutions Engineer Christine Wang and Developer Advocate Marcus Olsson will show you how you can build a panel plugin to create custom visualizations for Grafana. During this webinar, you will learn about:

Create static query results for prototyping dashboards and testing panels.

There are a lot of great things about Grafana 7.0, but one of my favorite features is the new React-based plugin platform, which has a set of new APIs and design system to help you build your own plugin. The process is easier and faster than ever. In this blog post, I’ll show how you can create a panel plugin for visualizing scatter plots.

Compare data by area and colors.

Aggregate time series by hour to analyze activity or traffic during the day.