Hi! I am working on developing a datepicker plugin, and I have encountered a problem. Everything works correctly in the local environment, but on the server, part of the functionality is not executing. For example, no console.log statements are outputting on the server, even though everything works …

[image] maxymzakharkiv: but on the server, part of the functionality is not executing Grafana doesn’t execute any javascript in the server-side. All the server-side (backend) of Grafana is written in go. Do you maybe mean you can’t see your console.log statements in the browser when you test…

The code is running on the server, meaning the project is deployed on the server. The plugin itself displays in the server environment, and I can use it, but for some reason, this useEffect doesn’t work in the server environment, although it works correctly locally. useEffect(() => { const para…

@maxymzakharkiv We published an article recently from a community member who implemented custom Date Picker using existing community plugin without developing a new one. Check it out: [image] How to create a custom Datepicker to set time range in Grafana 11 | Volkov Labs Thank you oros…

This is a bit different from what I need. I’ve already developed the plugin, and it works locally, but for some reason, part of the functionality isn’t working in the server environment (as I described above). I’m not sure what the issue is here

Curious, Why is there a need to use console log on server after plugin is deployed? Wonder if the plugin build process strips out those kinds of things

I’m deploying this on a test server and I needed to debug the code this way because again, the plugin works correctly locally, but on the test server there is no console.log output and the useEffect from the code I provided above access is not working. I can’t figure out why this is happening.

Is it not just as advised above? That: The default webpack configuration that comes with create-plugin drops console.log statements

Well as @davidharris pointed out you can’t so maybe go the write to log route?

For some reason, the timeRange on the remote server isn’t working for auto-refreshing the date, but it works locally. Why is this happening?

I made it so that console.log messages now appear, but it didn’t solve the problem. Locally, useEffect triggers based on the interval (set to 5 seconds - it works every 5 seconds), but in the server environment, useEffect only fires once. This needs to be fixed.

Issue with custom plugin for Grafana on the server

Grafana Plugin Development

maxymzakharkiv November 7, 2024, 2:58pm 14

The issue has been resolved

Topic		Replies	Views
Make your own custom 'Datepicker' (Use/set your own timerange). Here is how to Dashboards time-selection	14	16893	November 21, 2024
Deploy grafana development environment changes to production environment Grafana Plugin Development	1	470	June 8, 2023
ChatGPT told me there is a REST API call to set the timepicker current time range in a dashboard. True? Dashboards api , time-selection	6	1825	February 21, 2023
Newly installed plugins are not visible & log file is not updating with the passage of time & Date Configuration	15	7114	August 6, 2020
Unix time to UK Date Time Grafana	8	801	March 29, 2022

Issue with custom plugin for Grafana on the server

Related topics