@sean Are you providing a JWT key in the request ?

Hey @MattFox ill try get some help from the dev team on this.

Hi Ruan. I have replied to your support ticket

@sean
Please can you explain what your goal is? Are you trying to change historic values?
Also provide the mango version

Hi @tungthanh500
Im not exactly sure what you are trying to do. Are you trying to restore an H2 back to a MySQL cause that will not work? You will need to convert the database first.

@tungthanh500
Yes, shut down mango and move those 2 files. When you start up mango it will create a new DB. Once mango has started you can then restore with an backup

@tungthanh500
Looks like a corrupt db. You will need to start mango with a fresh DB. You do this by moving the current mah2 db to another folderr. Then start mango, it will detect there is no DB then create a new one. You will need to then restore with an old backup.

@Turbo
ok, the scripts of fairly long but I've tried to see what's going on. The install script creates a user and sets its home to /opt/mango-data. it always adds path.data=/opt/mango-data to the mango.properties file. These scripts work entirely as expected if executed as the mango user because they can fall back on the $HOME directory and find the mango. properties.

When you execute them as another user they cannot find the mango.properties file to search for the path.data properties so the fall back on /opt/mango (this is sourced from the directory they are executed in)

So the environmental variables are required when other users execute the scripts which would be the case with certbot executing the cert-deploy script.

The paths are mentioned in the help doc altho it is not quite clear that the scripts will fail without them... I actually had some frustration myself with the scripts about 2 months ago and got them modified to echo more information so you can know what's going on but that will only be in the next release.

I will also open a ticket for the help docs to include the importance of the environmental variables. Ie without them only the mango user can execute them succesfully.

@cbyrne
Ye, I hear what you saying but the component was designed to enable highly accurate filters and we can't lose that. it's needed in the bulk editor and other pages. Maybe adding 2 different filter modes would be helpful to use in general dashboards.

@Turbo

It looks to me the source of all your problems is that you don't have mango_paths_data and mango_paths_home set as environment variables. The scripts are very tightly dependent on those variables. The install script does not set those.

and each site has a conf file that includes the renew_hook, so it's going to expect to be able to run that certbot-deploysh script. How can I make sure make the certbot stuff works now that that config file is moved to /opt/mango-data

When you do the first request for a cert you provide the path of the renew_hook, Which is the certbot deploy script. Certbot executes this script straight after a successful renew. This script does 2 things, its creates a P12 from the bundle the letsencrypt provided. it moves the bundle to "ssl.keystore.location" defined in the mango.properties. if "ssl.keystore.location" is absolute(starting with a "/") it will place it in that location. if it is relative(not starting with a "/") it will put it in $mango_paths_data/ssl.keystore.location

if you are saying that it is landing in /opt/mango/ssl.keystore.location I suspect that you are using a relative path and that $mango_paths_data is not set and it is defaulting to mango directory

@cbyrne

The Data Sources > Data Points just use angularJs $filter directive. You will not be able to override the ma-data-point-selector to behave the same as it already has its own filter in it. It just works differently. You need to be more precise with wild cards:
if you have a point name : foobarfoo and you want to filter by "bar" you would need to use

*bar*

This was built to be able to produce "high resolution" filters to be able to bulk edit points or add to publishers.

For your custom dashboards I would suggest using the

<ma-filtering-point-list  ng-model="maFilteringPointListModel" get-by-xid="true" ></ma-filtering-point-list>

I think it would be more suitable for dashboards as it has a more general filter and works the same as the data source -> datapoint details page. you can add custom queries, client side filtering on those quries, label ect and it has API docs and examples:
/ui/examples/basics/point-list
/ui/docs/ng-mango/ma-filtering-point-list

The <ma-datapoint-selector> does not have documentation yet but you can view its on https://github.com/MangoAutomation/ma-dashboards/tree/main/UI/web-src/ngMango/components/dataPointSelector

@Xof1986

im not able to replicate this. My only suggestion would be to change the interval logging type to instant and see if that fixes the problem.
you'll need to select interval logg on the dropdown to change that setting but you can save it as OCI

@Xof1986 What data sources are these points from and data type?
Actually could you export the whole point and paste it here

@Xof1986 ok seems like more than enough resources for 500 points. I have not ever seen that behavior before. I will see if I can replicate it on 3.7.4. But if it's not happening on every point I doubt I can replicate it. I would recommend upgrading the server if you going to tinker with the threads. There was a bug fix in 3.7.8 regarding the threads:
Version 3.7.8
Upgrade Jetty webserver to 9.4.43.v20210629 to fix performance issues
Remove ssl.alpn.debug env property, this is now enabled by configuring log4j logger for the org.eclipse.jetty.alpn.server package
Fix bug where setting the high priority core thread pool greater than 100 would cause Mango to fail to start
Update store.url env property to new location of store.mango-os.com

@Xof1986

There is a mango internal point tracking the points to be written, is that stable or does it keep climbing?
Sounds like you might be running out of threads or your system cant keep up. what is the size of the mango system and how powerful is our host machine?

@tomatopi This is a good solution, definitely worth investigating. You could also reach out to a weather API and get sun rise and set times for your area and use those times in your statistics query.

@tomatopi this is possible out of the box but it wont be as simple as using the datebar in the top corner. You will need to create a statistics query for each individual time span , one for day time, one for night time of each day.

Thanks for the feedback, everyone. I have been out of the office for two weeks but will try get on back on track with some guides soon.

Hello Mango community, I am seeking your valuable insights on potential topics for How-to guides. Whether it's related to creating dashboards, configuring systems, or designing systems, I'm open to all suggestions. Your input would be greatly appreciated, and I look forward to hearing your ideas.

@kyle-Hughes its kind of hard for me to follow your configuration and identify what the actual problem is. Maybe you could do a diagram on how each Mango assets links together ?