File: Known-Issues.md

package info (click to toggle)
cacti 1.2.30%2Bds1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 67,176 kB
  • sloc: php: 123,193; javascript: 29,825; sql: 2,595; xml: 1,823; sh: 1,228; perl: 194; makefile: 65; python: 51; ruby: 9
file content (25 lines) | stat: -rw-r--r-- 1,397 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
# Known Issues

Cacti has been under development and evolution for almost 20 years.  So,
with all that evolution there are going to be bugs from time to time and
sometimes these bugs can be severe.  So, its important that people who
use Cacti stay up to date on various bugs and limitations.

The best place to go for discovering what Bugs or Issue exist in Cacti is
to goto [GitHub](https://www.github.com/Cacti/cacti).  From there, you can
view not only the Cacti repo, but a collection of Cacti Group mainteined
**Plugins**.  For the Core Cacti and for every Plugin, there is an issue
tracker site the corresponds to it.  Issues are generally broken into
[Enhancements](https://github.com/Cacti/cacti/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement)
and [Bugs](https://github.com/Cacti/cacti/issues?q=is%3Aopen+is%3Aissue+label%3Abug).

If you find that you are having experiencing and issue, and you are fairly
experienced Cacti user, go directly to the Cacti issue tracker and submit your
issue.  If you are new to Cacti, it's best to go to the Cacti [Forums](https://forums.cacti.net)
first as you will likely find answers to your questions there.  Generally
using either [Google](https://www.google.com), [DuckDuckGo](https://duckduckgo.com)
and other popular search engines regularly scan the Cacti Forums, so using
those services will help.

---
Copyright (c) 2004-2024 The Cacti Group