#ASAr2 -- Harvest-main-cDOT > ONTAP SVM Dashboard
1 messages · Page 1 of 1 (latest)
@verbal quest FCP metrics are only supported by the ZapiPerf and RestPerf collectors currently, so these panels will be empty for ASAr2. You can refer to the metrics documentation here:
https://netapp.github.io/harvest/26.02/ontap-metrics/#fcp_lif_avg_read_latency
ASAr2 supports a limited set of performance metrics, as noted here: https://netapp.github.io/harvest/26.02/asar2/
However, with StatPerf we can enable additional metrics. Let us know if you’d like to enable fcp_lif metrics via the StatPerf collectors.
yea, that's what I was looking for... the individual FCP lif metrics
hi @verbal quest the documentation at https://netapp.github.io/harvest/26.02/asar2/ mentions enabling StatPerf
Can you follow the instructions there to install StatPerf and then enable the FcpLif template. How did you install Harvest?
basically the "quick start" processes ... I did the StatPert steps as part of it since I assumed I would need it at some point, if not at the start
Did you also do these steps for your ASAr2 cluster? https://netapp.github.io/harvest/26.02/prepare-cdot-clusters/#statperf-least-privilege-role
The quickstart process uses the Harvest native binary (not Nabox, containers, or Deb/RPM). Is that how you installed?
Great! To enable the FcpLif StatPerf template create a custom.yaml file here conf/statperf/custom.yaml The contents of that file should be
objects:
FcpLif: fcp_lif.yaml
After making those changes, restart your poller(s) and check your log files for a line like this
time=2026-03-05T10:46:15.891-05:00 level=INFO source=helpers.go:113 msg="best-fit template" Poller=sar collector=StatPerf:FcpLif path=conf/statperf/9.8.0/fcp_lif.yaml v=9.16.1 jitter=none
cool .. will take a look at that shortly (doing a code upgrade this ASA box at the moment)
weird... my logging stopped working, but I'm still getting data... but no change to the FC data
harvest.yaml:
collectors:
- StatPerf
- Rest
- RestPerf
- Ems
use_insecure_tls: true
exporters:
- prometheus1
Pollers:
CLUSTER1:
datacenter: DC1
addr: CLUSTER1.foo.com
auth_style: basic_auth
username: <creds>
password: <creds>```
Then the custom.yaml file:
```# cat conf/statperf/custom.yaml
objects:
FcpLif: fcp_lif.yaml```
Are you getting data now?
no
Could you share harvest logs @ ng-harvest-files@netapp.com ?
like I said, since I restart the poller, my logging stopped... I'm still getting data at the SVM layer, but no changes for the FCP piece
binary files / tar.gz via the "quick start" processes
Could you try running below command. Pass a POLLERNAME for ASAr2 as you configured in harvest config
You need to run this through your installed directory of harvest
bin/poller --poller POLLERNAME --collectors StatPerf
and share logs. They should print in console only for this command
```time=2026-03-06T14:14:23.673Z level=ERROR source=collector.go:435 msg="Entering standby mode" Poller=CLUSTER collector=StatPerf:NvmMirror error="error in POST request: StatusCode: 403, Error: Permission denied, Message: not authorized for that command, API: /api/private/cli" task=counter````
hrm... looks like I have a permissions issue, but I was just checking that and thought that entry was there
Ok try applying these permissions again
https://netapp.github.io/harvest/nightly/prepare-cdot-clusters/#statperf-least-privilege-role
that took care of it...
this was the problem:
security login rest-role create -role harvest-rest-role -access read_create -api /api/private/cli
that was throwing a "duplicate entry" since the "readonly" rule had existed from other processes
i just missed it 🤷
cool. Yeah StatPerf requires read_create
I still don't get why my log isn't updating 🤔
You are usually getting it /var/log/harvest right?
yep .. it just stopped logging there after I added that custom.yaml and restarted
Are you getting metric data now?
yea, I am getting the FCP data in the dashboards now
for logs, Let me check what can we do
was just vadliting permissions... the 'harvest' user runs and owns everything, best I can tell
are you running it via systemd?
yea
Any disk space issue?
nope, that was the first thing I checked... been bit by that before 😄
Yeah.. It seems like permission issue only to me. But you have checked it already
try running below command
journalctl -u harvest -n 50
or try tunning permissions again
sudo chown -R harvest:harvest /var/log/harvest/
sudo chmod 755 /var/log/harvest/
# Restart harvest
sudo systemctl restart harvest