Pick graph with Slack Slash Command from Grafana Image Renderer and post graph image to Slack.
Please read docker-compose.yml
You need register an Slack Application for Slash Command and files:write permission token.
Slash command can be configured as follows:
Command: /graph Request URL: https://your_server_host/slash Short Description: Get Grafana Panel by alias Usage Hint: [cpu|memory|disk] \d+[m|h|d|M]
Configuration file be specified as follows:
slack: token: xoxb-test # Slack Token (needs files:write permission) secret: 6e50 # Slack Verification Token addr: ":8080" # Slash Command Server Listen Address grafana: endpoint: "http://localhost:3000/" # Grafana Endpoint use_client_auth: true # Enable Client Authentication for Auth Proxy client_auth_p12: "/ssl/key.p12" # Certificate file (P12) dashboards: - name: disk # Graph Alias (string) dashboardId: "000000012" # Graph Dashboard ID dashboardName: alerts-linux-nodes # Graph Dashboard Name orgId: 1 # Graph Org ID panelId: 1 # Graph Panel ID - name: cpu dashboardId: "000000012" dashboardName: alerts-linux-nodes orgId: 1 panelId: 4 - name: memory dashboardId: "000000012" dashboardName: alerts-linux-nodes orgId: 1 panelId: 5
dashboards specify a graph panel to be upload with Slack slash command. You can get the parameters of the graph panel by selecting the panel in Grafana and clicking on the share button.
name specifies the alias of a graph. So you can get a graph in Slack like
This application needs PKCS12 File (.p12) and password, and you need to enable
use_client_auth and specify p12 file path on
Run with environment:
Run with environment:
/graph <alias> (<from_time_range>) (No
<from_time_range> with default time range)
We found that github.com/ak1ra24/slack-grafana-image-renderer-picker demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket installs a GitHub app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.